-
Notifications
You must be signed in to change notification settings - Fork 335
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
Execution Layer Meeting 162 #781
Comments
I would like to discuss OpCode allocations for Cancun and EOF. https://hackmd.io/@shemnon/CancunOpcodeAllocation In summary I propose we move all EOF only opcodes to the 0xE? opcode block, move transient storage and memory copy into 0x5? and reserve some space in 0xF?. blobhash and beacon root are unchanged in the 0x4? block. Since Transient storage is in Cancun and memory copy is very likely in Cancun this should be decided sooner rather than later. Pay and EOF are mentioned for completeness. |
I'd like to cover the update to 4788 to move to a "stateful precompile" over an opcode-based mechanism as done in this PR: ethereum/EIPs#7065. Moreover, there are some questions around how to organize the root data in the EIP I'd like to discuss. A summary of the concerns can be seen here in an initial implementation of this EIP: https://github.com/ethereum/go-ethereum/pull/27289/files#r1204840057 |
Added @shemnon @ralexstokes! Also added some updates re: SELFDESTRUCT removal / EIP-6780, and posted relevant links that were shared in the R&D discord. |
if time we shall discuss this update to 4844: |
and this pls ethereum/EIPs#7062 |
Done @ralexstokes @lightclient! |
If there's some time left, I'd be interested to talk 2 mins about ethereum/EIPs#7069 at the very end. |
would also be nice to discuss the still open PRs from devnet-6 (https://notes.ethereum.org/@bbusa/dencun-devnet-6) PR-7038 - Cleanup transaction network payload references |
Closed in favor of #786 |
Meeting Info
#allcoredevs
Discord channel shortly before the callAgenda
data_gas_used
to header EIPs#7062The text was updated successfully, but these errors were encountered: