Consensus-layer Call 138

[ralexstokes]

Consensus-layer Call 138

prev: call 137

Meeting Date/Time: Thursday 2024/7/25 at 14:00 UTC
Meeting Duration: 1.5 hours
stream

1. Electra
   • devnet-1
   • Refactor requests from execution payload
   • Engine API update: Consensus-layer Call 138 #1100 (comment)
   • Stable container EIPs 7688, 7495 in Pectra
2. PeerDAS
   • devnet updates?
   • Pectra roadmap -- drop sampling?
3. Research, spec, etc
4. Open discussion/Closing remarks

[lightclient]

Engine api proposal for devnet-2 ethereum/execution-apis#565

[etan-status]

SSZ StableContainer in devnet2?

• EIPs: https://eips.ethereum.org/EIPS/eip-7688, https://eips.ethereum.org/EIPS/eip-7495
• Specs: etan-status/consensus-specs@ef-eip7688
• Tests: Adopt EIP-7688: Forward compatible consensus data structures consensus-specs#3844 (comment)
• Kurtosis: https://stabilitynow.box (bottom left config)

This is about the minimum scope we can do to address the issues with GeneralizedIndex breaking on consensus forks.
Electra already breaks GeneralizedIndex in BeaconState for other reasons, so EIP-4788 based smart contracts are required to go through migration. Meaning, that if the fix is applied with Electra, it won't result in additional work for smart contract devs beyond Electra.

[potuz]

I'd like to discuss the possibility of replacing the ExecutionPayload that is broadcast in the CL by an envelope in which the requests that are needed for the beacon state transition are put outside and the remaining of the payload (transactions, gas limits, etc) are kept inside a payload object within the envelope. This way the CL can store more easily the data it needs to process state transition without requesting the data from the EL, it's future SSZ compatible and makes blinding the payload a trivial proceduce.

[dapplion]

If possible as late addition I would like to bring up

• Add BeaconBlocksByRange v3 consensus-specs#3845

[ralexstokes]

closing in lieu of #1116