ACDT #97 · Hegotá devnets Split, then merged
AllCoreDevs - Testing #097 · 2026-09-21
Agreed to start Focil and Frames separately and merge them later
No major new decisions came out of this call. It agreed to start Hegotá devnets separately, one for FOCIL only and one for Frames only, and merge them later, while the CL block serving window and BAL retention period issues were passed to asynchronous discussion with no conclusion.
Why it matters
Testing complex EIPs separately early on lets teams find the cause of problems quickly and shorten the Hegotá development cycle. Aligning the serving window and the BAL retention period would reduce node storage requirements once decided, which affects both EL and CL operators.
Decisions
- Serving window unresolved: The call did not settle the Glamsterdam CL block serving window and BAL retention period, and passed them to asynchronous discussion and ACDE. Three options were raised: keep 33,024 epochs, reduce to about 14,299, or reduce to 8,192 (EIP-8383, a Hegotá candidate and so out of scope). None of them blocks the testnet launch.
- Hegotá devnet plan: Agreed to start Hegotá devnets separately, one for FOCIL only and one for Frames only, and merge them into a combined Hegotá devnet once they are stable. The aim is to separate complex interactions early so causes are easier to identify.
- EIP-8142 withdrawn: The announcement was that the champion withdrew EIP-8142 (BiB) and proposed EIP-8411 (Fast Execution Payload Broadcast) as its replacement, and no decision was made on this call. CL teams were asked to add their ratings before the next ACDC.
Discussion
CL serving window and BAL retention period
EIP-8061 shortened the Weak Subjectivity Period (WSP), but the CL block serving window remains at 33,024 epochs, so the group discussed whether to shorten it and whether to align it with the BAL retention period.
Hegotá devnet composition order
Drawing on the experience of underestimating complex EIPs in Glamsterdam, the group discussed in what order to compose the Hegotá devnets.
Outcome: Scheduled 00:44:22
Benchmarking hardware target
It was raised that benchmarking targets only the minimum full node spec, and whether the stricter attester node spec should also be tested.
Glossary
- SFI: Scheduled for Inclusion. Confirmed for inclusion in the fork
- CFI: Considered for Inclusion. Under consideration for inclusion
- PFI: Proposed for Inclusion. Accepted and kept as a candidate
- DFI: Declined for Inclusion. Removed from candidacy or withdrawn
- BAL: Block Access List (EIP-7928). The list of state a block accessed
- WSP: Weak Subjectivity Period. The period during which a node can catch up after being offline without a trusted checkpoint
- FOCIL: Fork-choice enforced Inclusion Lists (EIP-7805). Inclusion lists for censorship resistance
- Frames: Frames (EIP-8141). A new transaction format
EIPs covered
- EIP-7805 Inclusion lists enforced by fork choice
- EIP-7870 Recommended node hardware and bandwidth specifications
- EIP-7928 Block-level access lists
- EIP-8061 Higher exit and consolidation processing limit
- EIP-8141 Frame transactions
- EIP-8142 Block-in-Blobs
- EIP-8383 Shorter consensus layer block retention period
- EIP-8411 Fast propagation of execution payloads