EOF Implementers Call #68

EOF Implementers Call #68

Agenda

Other comments and resources

GitHub Issue

1 Like

Agenda for tomorrows call:

2 Likes

Meeting Notes

Client and compilers - no updates

Testing - there is a “final” devnet 0 test suite - pleas test and report back

Devnet 1 - ’

  • hash : 0xff || sender || salt

    • 0xff guarantees no rlp collisions, that was EIP-1014 motivation. Retain it for consistency.
    • creator contract - add optional sender to salt
      • without it, the contracts can be front runnable, wherever it matters (such as using tx.origin in initcode).
      • Could we use two selectors? One that is sender safe and one that is sender unsafe?
      • Start with simplest version. Initcode hash, plus a called salt, plus arguments for initcode. don’t include sender.
      • ERCs can deploy the safer ones and tooling can ensure deployment.
      • We need to communicate with dev tool to see how it would impact their use case. (Foundary, hardhat, etc.)
      • Frangio is still nervous. We need to have a flag for the caller.
  • Pay Opcode

    • slides presented by wjelemts.
    • No consensus one way or another
  • Metadata section

    • Can metadata section be excluded from initcode hash as a part of TXCREATE initcode? Uniswap drops metadata because it impacts addresses.
    • Metadata has been solved on etherscan for a while (frangio). There are concerns about frontrunnig that may have been solved.
1 Like