Agenda
-
Payload Post-State Availability in the EVM (EIP-4788 Implications Post-ePBS): Discuss EVM access to beacon state roots post-ePBS, which introduces separate consensus and execution state transitions. EIP-4788 exposes the parent beacon block root (containing a state_root, pre-payload), enabling proofs of pre-payload states (e.g., validator not slashed) but not post-payload states (e.g., consolidation requests processed in payload). Evaluate options:
- a. Leave as-is, using state.state_roots for post-payload access (grandparent payload, sufficient for most cases).
- b. New EIP exposing execution payload envelope root (like EIP-4788, for post-payload proofs).
- c. Add pre_state_root to beacon block (similar functionality to a).
-
Handling Beacon Block Body Fields Moved to Execution
- Description: Decide on fields shifted from CL to EL (e.g.,
blob_kzg_commitments
,execution_requests
) Options:- (a) Remove entirely (changes generalized indices; backward compatibility concerns, but no known breakage;
- (b) Stub as empty, assert in STF (preserves indices, adds tech debt).
- If removing, consider dropping unused deposits and
eth1data
(post-Pectra).
- Description: Decide on fields shifted from CL to EL (e.g.,
-
PR Reviews and Spec Updates
-
Discuss Potential Impact on Builder API: ePBS MEV Relays Design - HackMD
-
Discuss Process and Timing for Advancing Spec: epbs-devnet-0 spec
Meeting Time: Friday, August 29, 2025 at 14:00 UTC (60 minutes)