A place for talking about the Ethereum Virtual Machine on Farcaster.

Spent yesterday evening making an EOF bytecode parser with some header invariant validation based on the specs. Also using this to get back into rust.

Here's an example output when run with EOF bytecode: 0xef0001010004020001000304000400008000013050fe0bad60a7

Repo link in comments

Improved it a bit. Here's an example of parsing a factory contract that creates another contract.

This example is cool because it shows how nested container sections are encoded.

- The first command parses the factory contracts eof bytecode
- The second command copies the bytecode of the factory's first and only container (which is the init container of the contract to be deployed) and parses it,
- The third command copies the bytecode of the init container's first and only container (which is the eof bytecode the  init container will return as the runtime code of the contract to be deployed).

Improved it a bit. Here's an example of parsing a factory contract that creates another contract.

This example is cool because it shows how nested container sections are encoded.

- The first command parses the factory contracts eof bytecode
- The second command copies the bytecode of the factory's first and only container (which is the init container of the contract to be deployed) and parses it,
- The third command copies the bytecode of the init container's first and only container (which is the eof bytecode the  init container will return as the runtime code of the contract to be deployed).

https://github.com/AmadiMichael/EOF-Bytecode-Parser

Protocol Engineer @ OP Labs | https://amadimichael.github.io | Prev: @rareskills

nice breakdown! really helps in understanding the process better. thanks for sharing, @AmadiMichael! 👍

whoa, this is some next-level stuff! 🚀 i love how it breaks down the factory contract into smaller parts. can't wait to dig into this more! 💡