JJOptimist's Builder Journey

[JJOptimist]

Gm! I am a web3 dev from Serbia looking to create something useful for the Gno community. I am currently diving into Gno space and exploring solutions made by previous contributors.

[JJOptimist]

Here's an update on the stuff I did for the first week:

• Explored Gno.land’s GitHub repositories, focusing on issues, PRs, and previous contributors' journeys to gain a better understanding of the ecosystem and its active development.
• Experimented with GRC20 to get a better understanding of how it works underneath

My plans for the next week are:

• Experiment with GRC721
• Do the final touches and finish my homerealm
• Start building a decentralized event ticketing system leveraging GRC721 for ticket creation and management, integrated with a Telegram Mini App for mobile accessibility and ease of use.

[JJOptimist]

I explored Gno.land’s GitHub repositories, focusing on issues, pull requests, and previous contributors' work to gain a better understanding. I worked on my homerealm and after pushing it for review I have a good feedback on what to improve.

What will I focus on this week?
I will continue working on my homerealm, resolving existing issues and adding new, interesting features. I plan to experiment with GRC721 to strengthen my understanding of it. I’ll also revisit the awesome-gno repository to improve my fundamentals. Once I feel more confident, I’ll return to my event ticketing project, refining its foundation and focusing on using GRC721 for ticket creation and management. Additionally, I aim to contribute by trying to resolve an issue in gnoweb.

[JJOptimist]

My initial contribution began with creating a home realm, where I received valuable feedback. This feedback has helped me understand better practices for code quality, and I'm actively working on implementing these improvements.

Building on this experience, I've developed an NFT-based event ticketing system (PR #3509). This system leverages the GRC721 standard to create a decentralized solution for event management. Users can create events with customizable parameters such as name, description, date, and ticket capacity. The system handles GNOT payments for ticket purchases, automatically minting NFT tickets to buyers' addresses. A web interface provides easy access to view available events and their details.

Through this development process, I've gained significant insights into:

• Implementing GRC721 standards in Gno
• Writing comprehensive test suites
• Handling blockchain transactions and payments
• Working with Gno's CI/CD pipeline

Currently, I'm focusing on improving the test coverage and resolving CI issues in the eventix and my home realm. I am also looking to explore issue #3482 .

[JJOptimist]

I've finally finished the home realm, if something is worth the HoF it's the time it took for this PR to get merged. I did have a few setbacks and had to revert some things but I am now back on the track. I started working on the POAP system . last week and it is in progress now. I am currently writing ownership management and working on UI for it. The plan is for this to be later integrated with my previous event managing tool (Eventix) so users can get proof of attendance in a form of GRC721.

[JJOptimist]

Last few weeks I've been working between the event managing tool Eventix and the POAP system. I've added some improvements to both. Eventix now supports multiple GRC20 tokens instead of just GNOT and uses some packages such as pager for better UX. On the other hand POAPs first version is finished. Users can create events easily by specifying its name, description, date (or date as an RFC3339 string), and maximum allowed mint count. When created, each event is assigned a unique identifier and stored using an efficient AVL tree structure. Use GetPOAP to fetch a specific event by its ID, or ListPOAPs to retrieve all available events. When a user (or caller) initiates a mint, the system verifies that the event exists and that the minting limit has not been exceeded. If the conditions are met, it mints an NFT token using the GRC721 interface. The token ID is generated in the format eventID-mintCount, ensuring a unique identifier for every minted token. Users can also retrieve all events for which they own a token, as well as fetch the specific NFT tokens minted for any event using GetPOAPsByOwner and GetPOAPTokens. There are also tests for each of the functionalities, successful minting process, and proper NFT ownership, including managing state transitions when the mint limit is reached. If I missed some edge case feel free to open an issue on this and I'll get it covered.

Aside from that, I started experimenting with AI Agents such as ElizaOS with a goal in mind to make an Agent that can for example manage Adena wallet or use some of the existing tools/packages within Gno such as this POAP system. I will continue working on the remaining improvements for Eventix, wait for suggestions for the POAPs, and hopefully manage to work out something with an AI Agents.

[JJOptimist]

This last period, I focused on creating an AI Agent that possesses the knowledge about Gno to assist new contributors or anyone interested in Gno.land. I've combined ElizaOS (The Operating System for AI Agents) with Telegram client and my Telegram Bot since most of web3/blockchain users are also TG users. Now you can directly chat with Agent through Telegram.

ElizaOS allows you to give a certain type of personality to your Agent depending on how many parameters you give it. I won't say what I set up, you can figure it out through conversation with him :). You can find him on TG under the '@gnomeland_bot' tag.

Currently ElizaOS has an issue with TG client and they are working on it, so now its only available through a direct web client.
Here are some examples of how Gnome Agent responds:

It still requires some fine tuning but works as intended. My initial idea was to make him also manage Adena wallet, but turns out its a much harder challenge than I thought. It would require making a special plugin with specific 'actions' that Agent can understand