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

EOF-Solidity feature requests:

1) Native support for Code Section types: Defined as a struct of 4 fields: bytecode, num of inputs, num of outputs and max stack height. This is to be defined at the contract level and must be known at compile time so that it can be validated and compiled together with the solidity code.

Then within any function, the code section can be called via solidity or inline assembly and outputs are to be consumed. 

This feature enables using custom bytecode e.g hyper optimized hand written bytecode or from another compiler be used within solidity.

Example with unchecked add 3 bytecode in comments:

Okay, issue raised. Maybe native bytecode linking (like huffidity) will be possible with EOF Solidity... any feedback is appreciated and welcome

Okay, issue raised. Maybe native bytecode linking (like huffidity) will be possible with EOF Solidity... any feedback is appreciated and welcome

https://github.com/ethereum/solidity/issues/15211

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

This would be such a nice feature for solidity! Would love to see it adopted!

Interested in ZK, FHE, PUFs, hardware, system design, ai safety, and smart contact security.