Try   HackMD

Hello everyone

Image Not Showing Possible Reasons
  • The image file may be corrupted
  • The server hosting the image is unavailable
  • The image path is incorrect
  • The image format is not supported
Learn More →
, here’s my development updates for the Week 5 of ethereum protocol fellowship cohort 4 !

To start this week, I couldn't work as much as I wanted, I had 2 days off because I was very sick.
but I'm starting to get better, so I'm back to work

Image Not Showing Possible Reasons
  • The image file may be corrupted
  • The server hosting the image is unavailable
  • The image path is incorrect
  • The image format is not supported
Learn More →

So I started the week by reviewing my project proposal indeed, I received feedback from Mario, which left me with a lot of comments.

I was able to apply most of the comments, except for some that required me to do more research on the testing ecosystem of ethereum because I did not know enough about the subject.

So I did my research on Ethereum testing to see how my fuzzing project could contribute to the ecosystem, and then I updated my proposal.

All at the same time, I am continuing to familiarize myself with the reth code base, modifying the source code, and doing tests.

Browsing the Ethereum testing ecosystem made me realize that the majority of existing tools often use the Geth project.

After careful consideration, I decided to switch from Reth to Geth for my project.

Geth is more mature than Reth, and having a lot of tools based on it will allow me to focus on fuzzing and be more productive using the many tools available.

So once this choice was made, I started to quickly learn the basics of Go so that I could then study
the Geth project.

I started by reading the documentation and following a tutorial, then I directly started to develop a project to be able to practice quickly.

Next steps:

Next week, I plan to finish my Go learning, start exploring Geth in depth, and configure my testing environment to run the fuzzers.