Written by the Besu Maintainers.

To streamline Prague planning from the Besu client team, our maintainers propose the following scope...

Prague Meta-Thread

In-Favor

EOF

Besu advocates for adding EOF to the Prague hard fork. 

The EVM Object Format is a collection of smaller changes aiming at paying down a significant amount of technical debt that the EVM has accrued over nearly a decade, and prepare the EVM so that "calcification" can occur on a robust foundation. EOF does not fundamentally change the execution of the EVM, instead it introduces a container format and migrates key instructions to new formats that resolve long standing problems such as eliminating dynamic jumps and the associated JUMPDEST analysis. Generally speaking there are four major themes addressed

  1. Making EVM code O(n) to JIT and AOT compile
  2. Eliminating Code Introspection 
  3. Eliminating Gas Introspection 
  4. Make “Quality of Life” improvements easier

The last bullet point enables features in future forks and L2 usages of the evm. L2s can more safely perform wholesale changes to their gas schedule. Experimental and non-conforming EVM features (such as new opcodes) can be signaled with extra header fields. And because JUMPDEST analysis has been replace with deploy time code validation the contract size limit could be safely increased or even uncapped. Team Ipsolon has launched https://evmobjectformat.org/ for a more comprehensive list of features. 

Besu's implementation of EOF is nearly complete, awaiting the finalization of a few final details.

EOAs, AA, & Next Steps

Besu supports adoption of EIP-3074

This EIP was considered and rejected for the London hard fork, almost three years ago, citing security issues. There was a call for a security audit at the time, which has not been done. The EIP would benefit from such an assessment. A major recent update to the nonce handling rules allows for a user to revoke authorizations with a single action. This recent specification change has removed the major safety concerns team members have had.

The Besu team views the need for 3074 as an opportunity cost. If we do not ship something in Prague, we run the risk of not supporting AA for the next 2-3 years. While this necessarily creates complexity in censorship resistance workstreams, the learnings from implementing AA sooner will allow us to have a better, more informed design where AA transaction validation logic is baked-in. This is a feature, not a bug. Keeping UX on Ethereum stunted for 2-3 years in order to solve some niche MEV challenges via ePBS seems like a poor trade-off. 


Supported Grab-Bag EIPs 

Neutral/No Opinion

  • EIP-7664: Access-Key opcode
    • Could be significant EVM work. Do we have an alternative? 
    • Not sure of necessity 
    • Might provide better security UX 

  • EIP-7557: Block-level Warming

    • Need to better understand the code complexity 
    • Might add complexity to the state DB that may add more data, memory, etc. Need to understand the impact to our code. 
  • EIP-7377: Migration Transaction
    • Good migration path for AA, but not instead of an encompassing AA solution like 3074 


Opposed

SSZ

Aesthetics and consistency with the CL is not necessarily a reason to engage on a large bucket of work on the EL. 

Opposed Grab Bag EIPs 

  • EIP-6913: SETCODE instruction
    • Code immutability is questionable. 
  • EIP-5806 Delegate Transaction
  • Weakly Opposed - EIP-5920: PAY opcode 1
    • Might break some assumptions of existing smart contracts 
    • Ether can get stuck in a smart contract that cannot send it 
    • Users may create issues with stuck Ether and 



  • No labels