EIP-7917 has been SFI’d for Fusaka with target of fusaka-devnet-1
Prepare readiness for fusaka-devnet-1, recognizing PeerDAS bugfixes from fusaka-devnet-0 and EIP-7917
Summary
Fusaka
fusaka-devnet-0 is live!
Some minor issues client teams are working through, but things are progressing well
Includes the BPO feature to scale blob count, which is working as intended so far
Fusaka CL EIPs to SFI
only EIP to consider was EIP-7917 for proposer lookahead
began with input from EIP champions and community members (preconf builders/users) who are impacted by this EIP
consensus amongst client teams was that implementation complexity was low, and the EIP is supported by spec testing that builds confidence in correctness
taken together, we decided to SFI 7917 and target fusaka-devnet-1 inclusion, with the understanding that it could be pulled in the event there are further complications from testing/integration
PeerDAS
Resolved some open questions around the BPO EIP
Decided to move forward with BPO-change aware fork digests that would be reflected in a node’s ENR, update to EIP forthcoming.
Touched on open questions around validatory custody, but the relevant contributors were not present so we decided to handle on Monday’s ACDT.
Glamsterdam
Opened the Glamsterdam conversation with a general discussion on high-level fork framing and some headliner previews
We had rough consensus that the fork focus should be around scalability and a potential subfocus of UX
With that in mind, we had two headliner presentations
EIP-7732 (ePBS)
check the call for a short presentation from @potuz
the discussion around this EIP was interesting, as many participants underscored the importance of FOCIL for CR properties but pointed out it didn’t directly contribute to the scalability focus; some discussion around presenting this EIP as enhancing UX
regardless, there was general support for this EIP and participants decided to keep reviewing in the context of other headliners as we progress in the fork scoping conversation
We wrapped the call by exploring which parts of the community ACD should seek to provide perspectives on Glamsterdam EIPs
for 7732, we identified the MEV ecosystem as desireable to weigh in on the builder mechanics of this EIP, and the solo staker community as desireable to speak to the improvements to node load from the EIP’s proposed pipelining structure
FOCIL was a bit trickier as it applies to the entire Ethereum community although that is signal in itself
We did not make any explicit decisions around Glamsterdam scope today, and instead opened the conversation to begin headliner selection alongside forthcoming EL EIPs.