EOF Implementers Call #56

[poojaranjan]

Meeting Info

Aug 21st, 2024 , 15:00 UTC

Duration: 60 minutes

Zoom: https://us02web.zoom.us/j/88940506383?pwd=aTdsbHVyMTNDSUFHYmhTWlI2ZEVldz09

📅 Subscribe to the Ethereum Protocol Call calendar for calendar invites

Resources

• Current specs
  • EIP-7692: EVM Object Format (EOFv1) Meta
  • EIPs Included
    
    EIP-3540: EOF - EVM Object Format v1
    EIP-3670: EOF - Code Validation
    EIP-4200: EOF - Static relative jumps
    EIP-4750: EOF - Functions
    EIP-5450: EOF - Stack Validation
    EIP-6206: EOF - JUMPF and non-returning functions
    EIP-7480: EOF - Data section access instructions
    EIP-663: SWAPN, DUPN and EXCHANGE instructions
    EIP-7069: Revamped CALL instructions
    EIP-7620: EOF Contract Creation
    EIP-7698: EOF - Creation transaction
• EOF Meeting Playlist
• EVM (EOF) Taxonomy
• EOF explainers on PEEPanEIP
  
  EVM Object Format (EOF) with Danno Ferrin
  EVM Object Format (EIP-3540 & EIP-3670) with Andrei Maiboroda, Axic & Pawel
• EOF Testing Coverage Tracker
• Solidity + EOF POC summary
• Matrix on evmobjectformat.org
• Prev meeting notes

Agenda

• Client updates
• Compiler updates
• Spec updates
• Testing updates
• Other items
  • Prague / Devnet-4 readiness (~3 weeks)
  • EOF Container Fuzzing
  • EOFTests need to be at 100%
  • EOF Execution Fuzzing
  • State/Block Tests need to be at 100%

Please add other agenda items or links to discuss.

Next call on Sep 4th, 2024

[shemnon]

Items that we need to make sure we discuss:

• Prague / Devnet-4 readiness (~3 weeks)
• EOF Container Fuzzing
  • EOFTests need to be at 100%
• EOF Execution Fuzzing
  • State/Block Tests need to be at 100%

[shemnon]

• Client and fuzzing updates

  • evmone found a bug that fuzzers couldn't find
  • besu had subcontainer container bugs found via evmon's tests a few weeks ago
  • Nethermind is re-writing their subcontainer validation to not be recursive
  • Reth and Geth were not present.

• Spec updates

  • community strongly wants a EXTCODESIZE/ISCONTRACT solution, Libs may not be happy with legacy "escape hatch" contracts rather than using EIP-165 introspections
    • If AA is the reason not to proceed, a clear plan needs to be stated as to how the AA transition is expected to play out.
  • Delegate call into legacy call rule
    • This may break proxies. (EOF proxies, proxying to a legacy contract)
    • A detection of EOF vs legacy contract would be useful. EXTCODEHASH would identify EOF
    • No opinion about 7702 proxy detection detection, can go with legacy treatment.

• Testing Readiness

  • With devnet-4 we need to activate on prague alone
    • EEST will migrate to just "Prague" for tests,
    • EEST will sunset "CancunEIP7692" and "Prague7692" forks
    • Will change once 7702 tests are fully merged into tests
    • Suddenly 7702 tests will work with EOF
  • New fixtures release 1.0.8 - Contains Both pragueEIP-7692 and Cancun7692
  • EOF Container Fuzzing
    • EVMONE and Besu
  • EOF Execution fuzzing
    • possibly goevmlab, guido vranken's fuzzer.

• Testing matrix

  • Devs, please update
  • Any automation interest?
    • Maybe hive/consume?
      • Still needs final consume setup in CI
      • Consume does not run EOF Validation tests (because engine API is the test interface)

[poojaranjan]

Closing in favor of #1138