Leo's Builder Journey

[Tchips46]

Hello everyone,

I'm Leo, a third-year EPITECH Paris student, thrilled to begin my journey with gno.land through the Student Contributors Program.

I’m passionate about cybersecurity and low-level programming. While blockchain is new to me, I’m excited to explore it alongside Lou, Eva, Mounia, Paul, and Nicolas! Over the next four months, we’ll be sharing our progress!

[Tchips46]

Hi everyone!

This week, I spent two days diving into Gno, Go, and how to interact with the blockchain through gno.web. As part of that, I developed my homepage and implemented a lightweight Pokémon fight simulator that's fully playable on GnoWeb.

I also gained a deeper understanding of the existing technical stack during a training day in Paris with @leohhhn , @gfanton , and the Parisian student cohort team.

Our goal for the upcoming month is to showcase what GnoWeb is capable of through small or larger projects (PR).
@paulogarithm and I also shared our interest in working on the Gno VM. To contribute effectively and propose useful issues that align with the current state and needs of the project, but before all, we have to understand how it really works and what its current limitations are.

This week was all about getting comfortable with the environment and exploring ideas for future development. Excited to keep making progress!

[Tchips46]

This week i focused on finishing my pokemon game, adding new features for a more complete experience, also ehancing my go/gno experience. (PR).

[Tchips46]

This week i started the gno evm implementation with @paulogarithm and @moonia, Ethereum VM PR

I also fixed my pokemon game issue after Leon reviews pr.

And i documented myself about what features could offer gno.web (like svg), and about how is working the evm

[Tchips46]

This week, I continued working on the Gno EVM implementation alongside @paulogarithm and @moonia. We made significant progress on the Ethereum VM PR.

We’ve completed all the "easy" parts of the code and are now focused on mocking EVM-specific chain codes.

[Tchips46]

This week, I continued working on the Gno EVM implementation alongside @paulogarithm and @moonia. We made significant progress on the Ethereum VM PR.

Our EVM is now Turing complete and capable of executing almost every opcode. The final step is to focus on EVM-dependent opcodes and determine how to mock them in order to alter the behavior of real contracts as little as possible.

[Tchips46]

This week, I continued working on the Gno EVM implementation alongside @paulogarithm and @moonia. We made significant progress on the Ethereum VM PR.

Our EVM can now execute Ethereum contracts, handle all types of storage, and is integrated into /r/demo/evm to visualize transactions. We're now focusing on the most complex opcodes that depend on the Ethereum blockchain.

I'm currently refactoring some of the account logic due to our initial misunderstood that smart contracts are also accounts, just like Externally Owned Accounts. This change is necessary to properly support opcodes that depend on interactions with other contracts.

[Tchips46]

This week, I continued working on the Gno EVM implementation alongside @paulogarithm and @moonia. We made significant progress on the Ethereum VM PR.

We are now implementing the defaults contracts.

I also foud a bug in a the gnoevm issue related to map state in crossing public fonction

[Tchips46]

This week, I continued working on the Gno EVM implementation alongside @paulogarithm and @moonia. We made significant progress on the Ethereum VM PR, struggling with the CALLCODE opcode, before finding out if it was that badly documented, it's because that's a deprecated opcode.

I also investigates in the map issue with the help of @paulogarithm

And fixed my review for the Pokémon realm.

[Tchips46]

This week, we mostly worked on the demonstration of the Ethereum VM that was due to the wednersday 28th, so we fixed the missing bugs, tried some stuff that we were going to show, and improve the frontend so it looks cleaner.

Friday, we saw each other with @paulogarithm and @moonia, and we mostly worked on our internship report. Something about this internship report, is that it can really have an impact on the gno community, because we plan to use it to contribute to Gno.

I also fixed my review for the Pokémon realm, cleaning lot of old code, now that I am better with gno.

[Tchips46]

This week, I again worked on the gno evm implementation with @paulogarithm and @moonia, Ethereum VM PR, focusing on contract creation, transaction tracking, and finished the CREATE opcode.

I also began drafting my internship report.

[Tchips46]

This week, once again, I worked on the Ethereum VM PR, grappling with some misunderstood Ethereum concepts. These misconceptions led to a need for refactoring for example, realizing that "global" storage is actually scoped to a single contract, which makes much more sense. Another case was contract creation, which involves not just the CREATE opcode, but a combination of several others.

I also continued my internship report.

[Tchips46]

This week, I finished all opcodes and logic for the Ethereum VM PR. The only remaining task is implementing the precompiled contracts, which are challenging due to their complex algorithms, such as hashing and advanced mathematical operations.

I also made progress on my internship report.

[Tchips46]

Over the past two weeks, a lot has happened, but the highlight was definitely ETHCC in Cannes with @moonia, @paulogarithm, and @louonezime!

First of all, we learned so much from the conferences we attended. We also had the chance to meet many members of the Gno team, it was great to get to know them better and finally put faces to names.
A huge thank you to the Gno.Land team for this amazing experience!

In addition, I reworked my Pokémon Realm to introduce new crossing methods and am currently waiting for feedback.

I also made a few adjustments to the EVM, following suggestions from Manfred, it's now ready for review.

And now, I'm working on the Change.Org Realm with @paulogarithm.