EOF implementers call #62, November 27 2024

Protocol Calls & happenings
1

Agenda

EOF Implementers Call #62 · Issue #1192 · ethereum/pm · GitHub

Notes

Notes by @shemnon (Copied from ethereum/pm)

Testing Update
  • How to handle State tests with invalid EOF?
    • state tests - reject test if any EOF is invalid
    • Block tests - only an issue in genesis? Abort if EOF in genesis is invalid.
    • Imported blocks - presume valid as create TXes are how they are added, so invalid EOF should result in an failed transactions.
    • Extends to 7702 - 0xEF01 validation?
  • EOFWrap Tests
Client and Compiler Updates
Spec Updates
  • Compiler Metadata Section
    • Kaan from Sourcify Team
    • Current practice is to just append
    • would want a separate metadata section in EOF.
      • Unreachable by code (a good thing)
      • contains the CBOR data solidity produces
    • Current status of appended to data and behind constructor fields makes it hard to find
    • Experimental Solidity EOF handling is to put CBOR metadata at the beginning of the data section.
    • Would insulate code/data indexes from variable CBOR sizes, such as if experimental flags are logged.
    • Next step is an EIP

Brief discussion on header section numbers

EOFCREATE hash - ipsilon/eof#162 (comment)
  • danno wants a “0xef01” hash added
  • Solidity has concerns about the genericness, would prefer container index
  • Bad salt management could prohibit multiple deployments
  • Should hash include auxdata, not just code data?
  • possible issues with cross-chain deployment. The more mandatory data makes same address contracts difficult.
  • note: some people don’t like metadata has in CREATE2, would compiler metadata be excluded from address derivation?
  • Are there security implications? Would the “code hash” guarantees be forgotten about? Could compilers compensate?
  • Please add comments to the thread.

Recording

2 Likes