Sacha's Builder Journey

[dujardin09]

Hey everyone 👋🏼

I'm Sacha, a French student ! I'm entering my third year at Epitech Paris. I love working with Go, C/C++, TypeScript and more recently, Solidity.

Through Poc-Innovation projects and hackathons, I've developed solid experience in software development and blockchain eco-system.

Right now, I’m participating in the Epitech student program!

In this issue, I'll be sharing my progress and experiences over the next two month 🔥

[dujardin09]

This week I discovered the gno.land ecosystem. I read the documentation and followed several tutorials to learn the gno language and tools. Then I quickly started building my home realm and a realm for betting on the coin toss game. I opened a PR for it.

These two realms allowed me to learn how to write realms and, above all, to apply important concepts such as interrealm, testing, the banker module, gnodev, and gnokey.

PR: gnolang/gno#4551

[dujardin09]

This week I started resolving issues, starting with two good first issues on tooling (gnokey & gnodev).

• feat(gnodev): -txs-file= detect dependencies gno#4589
• feat(gnokey): add gnokey version subcommand gno#4598

I also fixed my review for my coinflip realm and added my home realm to the home of realm.

[dujardin09]

Last week, I suggested a feature that would allow users to connect their wallet to a realm, but it wasn't really interesting. Then I keep correcting my PR after reviews on gnolang/gno/pull/4598 and gnolang/gno/pull/4551.
Finally, I began to discover the ecosystem of gnoverse/volos.

[leohhhn]

Hey @dujardin09, it would be great if you can provide an update on your progress here.

[dujardin09]

Since last time one of my good first issue on gnodev has been merged: gnolang/gno#4589. The other one on gnokey (gnolang/gno/pull/4598) is ready to be merged.

In the meantime I've enhanced the doc on gnodev (gnolang/gno#4634) because the genesis transaction file format was very tricky to find.

Since three weeks I've started contributing on https://github.com/gnoverse/volos. I've created a Docker environment composed of Dockerfiles and one Docker compose. -> gnoverse/volos/pull/37. It simulate a whole gno + gnoswap + tx-indexer environment.

Then I'm dedicated to the rendering of Volos realms. (gnoverse/volos#51). More precisely the governance part of the project. This represents 5 different pages.

Next to this journey I've opened two little PR:
gnolang/gno/pull/4700
gnolang/gno/pull/4639

[dujardin09]

This week, I submitted a PR for the rendering realm side of the Volos project: #51, and I'm nearly done addressing the review comments.

I also opened two additional PRs focused on refactoring and improving the structure of the Volos codebase:
gnoverse/volos/pull/88
gnoverse/volos/pull/89

Excited to keep pushing forward and improving the project!

[dujardin09]

Unfortunately, the Volos project has been put on hold.

So I've pivoted to a new project called “gnit,” that Guilhem came up with. Gnit is a composable Git protocol implementation as a Gno package (gno.land/p/demo/gnit) that enables any realm to become a Git repository.

This week, I started developing a proof of concept for the project that is capable of pushing and pulling Markdown format files.

Here's the repository: https://github.com/dujardin09/gnit

[dujardin09]

Significant progress on gnit! The project has evolved from a basic proof of concept into a functional Git-like workflow system for Gno.land.

The CLI now supports a complete development workflow:

• gnit clone - Clone repositories from any Gno realm, automatically creating a local directory
• gnit add - Stage files for commit (supports individual files and directories)
• gnit commit "" - Commit only staged changes to the blockchain
• gnit pull [file] - Fetch all files or specific files from the realm

Implemented a .gnit JSON file that tracks both the realm path and staged files, enabling proper staging/commit workflows

The realm implementation (gno.land/p/demo/gnit) now includes ListFiles() functionality, enabling the CLI to discover and pull all files in a repository.

Next steps include handling larger files (currently limited by gnokey's output truncation) and potentially implementing chunked file transfers for better scalability.