EOF Implementers Call #59

[poojaranjan]

Meeting Info

Oct 02, 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
  • Osaka Migration
  • EXTCALL return values
  • HASCONTRACT

Please add other agenda items or links to discuss.

Next call on Oct 16, 2024

[shemnon]

Stuff to discuss

• Testing Update
• Osaka Migration
• EXTCALL return values
• HASCONTRACT

[shemnon]

• Current release tests (EOF on top of prague) are broken

  • Besu had a 7702 bug, all non-7702 tests are fine.
  • Next release will be released after devnet 4 is released
  • PR reviews are mostly caught up
  • Testing focus is on devnet 4 for the next week

• Compiler

  • Vyper create from blueprint needs a re-work for EOF.
    • Create form EXT Contract would have helped.
    • Cannot blueprint off of any contract in EOF like you could in legacy
    • A factory deployer would be good, delegate call into a contract that EOF creates. As opposed to an initcode only contract

• Osaka Migration

  • Clients need to target Osaka for EOF activation
  • Tests need to target Osaka, including moving tests in source tree
  • We have 6 more months to reifine the spec
    • We can look into HASCODE
    • We can reconsider EXT*CALL return code numbers
    • cleanup: EOFCREATE stack order
    • cleanup: Remove hashing of container in EOFCREATE
    • cleanup: Rename RETURNCONTRACT to RETURNCODE

• Open questions

  • Implications of gas introspection: regarding a gas to eth EIP.

Next Meeting:

• Rename RETURNCONTRACT -> RETURNCODE
• HASCODE / ERC-721 solution
• EXT*CALL return code, keep or revise?
• EOFCRAE stack order
• remove container hashing in EOFCREATE

[poojaranjan]

Closing in favor of #1167