ACDT #89 · Blob pool Engine API Included in Devnet 8
AllCoreDevs - Testing #089 · 2026-07-27
The sparse blob pool Engine API goes into Devnet 8
It was agreed to include only the Engine API part of the sparse blob pool (EIP-8070) in Glamsterdam Devnet 8, and actual cell-level data availability sampling (cell-level DAS) was postponed. The final repricing numbers are not out yet, so the Devnet 8 launch date was pushed to the next call.
Why it matters
If the sparse blob pool Engine API is adopted as standard, clients can choose between GetBlobsV3 and V4 as appropriate and reduce blob processing latency. However, disagreement remains over how to fit custody_columns into FCU, so further coordination will be needed during implementation.
Decisions
- EIP-8070 Engine API: It was agreed to include the Engine API changes of EIP-8070 (GetBlobsV4, and FCU carrying custody columns) in Devnet 8. Cell-level DAS is postponed until bandwidth allows.
- EIP-2780 Log costs: EIP-2780, which simplifies log costs, was included in Devnet 8 without objection. Most prices stay the same and only the values for contract creation (create) transactions change.
- EIP-8037 Gas naming: EIP-8037, which renames 'regular gas' to 'execution gas', was included in Devnet 8 without objection. It is a pure rename with no behavior change.
- EIP-7997 Boundary handling: Both PRs related to EIP-7997 were closed. The spec wording is already correct, and clients must not check for contract existence at the fork boundary.
- Devnet 8 launch date: The Devnet 8 launch date was postponed. It will be set again at the next ACDT, when the final repricing numbers are available.
Discussion
Devnet 8 launch schedule
The discussion covered when and how to launch the testnet after Devnet 7, and whether the changes could simply be layered onto Devnet 7.
Outcome: Schedule on hold, to be discussed again at the next ACDT
EIP-8070 sparse blob pool Engine API
The points of contention were the proposal to make only the Engine API part of the sparse blob pool mandatory for Devnet 8, and whether fitting custody_columns into FCU is the right approach.
Outcome: SFI decision 00:34:26
EIP-8037 gas renaming
A pure rename of 'regular gas' to 'execution gas' was briefly discussed, specifically whether this is the right name now.
Outcome: SFI decision 00:49:22
EIP-7997 factory contract at the fork boundary
The issue was whether, on chains where the factory contract has not yet been deployed at Glamsterdam activation, its address should be included in the block access list (BAL).
Outcome: Confirmed 01:00:12
Glossary
- ACDT: Ethereum core developer testing call (AllCoreDevs - Testing)
- SFI: Scheduled for Inclusion in the fork (Scheduled For Inclusion)
- CFI: Considered for Inclusion in the fork (Considered For Inclusion)
- PFI: Proposed for Inclusion in the fork, accepted and kept as a candidate (Proposed For Inclusion)
- DFI: Declined for Inclusion, removed from fork candidacy (Declined For Inclusion)
- Sparse blob pool: A blob management approach in which a node does not hold every blob but stores only the columns it needs
- BAL (block access list): A list of accessed accounts that lets block state be applied without re-executing transactions
- FCU (fork choice update): An Engine API call by which the consensus layer notifies the execution layer of the head block