Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

EOF Implementers Call #66 #1260

Closed
poojaranjan opened this issue Jan 22, 2025 · 5 comments
Closed

EOF Implementers Call #66 #1260

poojaranjan opened this issue Jan 22, 2025 · 5 comments
Labels
Breakout Type: Topic-specific breakout calls EOF Series: EVM Object Format Execution Layer: Issues that affect the execution layer

Comments

@poojaranjan
Copy link
Contributor

poojaranjan commented Jan 22, 2025

Meeting Info

  • Date & Time: February 5th, 2025, 15:00 UTC
  • Duration: 60 minutes
  • Zoom: Link

📅 Subscribe to the Ethereum Protocol Call calendar for calendar invites

Resources

Agenda

  • Testing Updates
    • General EEST updaes (mario)
    • Converting legacy tests to EEST (@chfast)
  • Client and Compiler Update
  • Non-specification Issues:
  • Specification Issues
  • Osaka-1 cleanup items
    • Document code section type malleability ipsilon/eof#176
    • Remaining List of items
      • Modify type section to have "additional stack" instead of total stack
      • Change EOFCREATE stack order to match EXTCALL
      • Any other stack arg re-ordering to align with legacy or other EOF ops
      • Rename RETURNCONTRACT to RETURNCODE
      • Change data section index from 0x04 to 0xff
        • Retire the 0x04 header ID.
      • Change CREATE/CREATE2 to an exceptional halt when seeing EOF (was fails and returns 0)
    • TXCREATE EIP-7873
      • Q: Do we need to block DELEGATECALL?
        • Will impact generated address namespace
      • Q: Is address hashing OK with everyone?
      • Q: Is toehold contract OK wih everyone?
      • Q: What other toehold variants for the ERC?
      • Add Metadata Section EIP-7834
      • Add EXTCODETYPE EIP-7761
      • Add CODEADDRESS opcode

Please add other agenda items or links to discuss.

Next call on February 19th, 2025

@abcoathup
Copy link

@chfast
Copy link
Member

chfast commented Jan 29, 2025

If time permits, I'd like to discuss:

  1. Progress on converting EOF validation tests from ethereum/tests to EEST.
  2. Document code section type malleability ipsilon/eof#176

@shemnon
Copy link
Contributor

shemnon commented Feb 4, 2025

  • Testing Updates

    • General EEST updaes (mario)
    • Converting legacy tests to EEST (@chfast)
  • Client and Compiler Update

  • Non-specification Issues:

  • Specification Issues

    • Osaka-1 cleanup items
      • Section Type Malliability ipsolon/eof#176
      • Remaining List of items
        • Modify type section to have "additional stack" instead of total stack
        • Change EOFCREATE stack order to match EXTCALL
        • Any other stack arg re-ordering to align with legacy or other EOF ops
        • Rename RETURNCONTRACT to RETURNCODE
        • Change data section index from 0x04 to 0xff
          • Retire the 0x04 header ID.
        • Change CREATE/CREATE2 to an exceptional halt when seeing EOF (was fails and returns 0)
    • TXCREATE EIP-7873
      • Q: Do we need to block DELEGATECALL?
        • Will impact generated address namespace
      • Q: Is address hashing OK with everyone?
      • Q: Is toehold contract OK wih everyone?
      • Q: What other toehold variants for the ERC?
    • Add Metadata Section EIP-7834
    • Add EXTCODETYPE EIP-7761
    • Add CODEADDRESS opcode

@nixorokish nixorokish added Breakout Type: Topic-specific breakout calls Execution Layer: Issues that affect the execution layer EOF Series: EVM Object Format labels Feb 4, 2025
@poojaranjan
Copy link
Contributor Author

@poojaranjan
Copy link
Contributor Author

Closing in favor of #1277

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Breakout Type: Topic-specific breakout calls EOF Series: EVM Object Format Execution Layer: Issues that affect the execution layer
Projects
None yet
Development

No branches or pull requests

5 participants