ACDE TL;DW
Fusaka
devnet-3
expected to finalize today, CL teams working on fixes for sync issues- Next week, once CL fixes are out, we’ll do another non-finality test. If things go well, we’ll launch
devnet-5
. Optimistic ETA EONW. - Barnabas will merge the following PRs if no objections in the next day:
- feat: update osaka style blob schedule eth-clients/holesky#129
- feat: update osaka style blob schedule eth-clients/sepolia#110
- feat: update osaka style blob schedule eth-clients/hoodi#19
- feat: update osaka style blob schedule eth-clients/mainnet#10
- For the fork rollout, we’ll propose both a timeline that matches the process doc we went with post-Pectra and reach out to the major stakeholders affected by the rollout to gauge their preferences
Holesky: agreed to shut it down a few weeks after Fusaka activates on it. Blog post coming next week to formally announce this.
Gas Limit: teams are working on addressing bottlenecks, hoping to get to 60M before Fusaka. Here is the list of blockers: eth-perf-research/README.md at main · NethermindEth/eth-perf-research · GitHub, Nethermind and PandaOps are working on better docs for the various dashboards and benchmarking test suites.
Glamsterdam PFI discussions: we’ll prioritize EIPs that client teams want to see discussed on the call. Besu shared some today which I’ll try and line up for the next call.
We also discussed a handful of EIPs that people had put on the agenda. The goal isn’t to make decisions about inclusion, but to share context and answer questions raised by client teams.
LLM Summary 
Action Items
- Fusaka
- Devnet-3: aim to finalize today; CL teams (e.g., Lighthouse, Prysm, Teku, Nimbus) continue syncing fixes.
- Non-finality testing: once the CL fixes are out next week, we’ll run another non-finality test; if recovery looks good, we’ll bring up Devnet-5 (fix-only scope).
- Blob-schedule PRs (merge after ~24h if no objections):
- Holesky: feat: update osaka style blob schedule by barnabasbusa · Pull Request #129 · eth-clients/holesky · GitHub
- Sepolia: feat: update osaka style blob schedule by barnabasbusa · Pull Request #110 · eth-clients/sepolia · GitHub
- Hoodi: feat: update osaka style blob schedule by barnabasbusa · Pull Request #19 · eth-clients/hoodi · GitHub
- Mainnet: feat: update osaka style blob schedule by barnabasbusa · Pull Request #10 · eth-clients/mainnet · GitHub
- Fork-rollout planning (two-track approach):
- Prepare a “default” schedule that follows the post-Pectra process doc for testnets (ordering, spacing, and comms milestones).
- In parallel, proactively poll major stakeholders (L2s, infra/app providers, staking operators) on preferred activation sequencing and lead-time. Items to clarify: (i) which testnet should carry the “app-staging” role and remain last; (ii) how much time to reserve between devnet validation and each testnet; (iii) change-freeze/holiday windows; (iv) gating criteria (e.g., non-finality recovery, sync health) before scheduling each step.
- Holesky
- Agreement to retire Holesky a few weeks after Fusaka activates there. A blog post with timelines/migration notes is planned for next week.
- Gas limit (toward 60M)
- Teams continue removing bottlenecks with a shared measurement plan; goal is to raise to 60M (ideally before Fusaka).
- Tracking list: eth-perf-research/README.md at main · NethermindEth/eth-perf-research · GitHub
- Nethermind and PandaOps will publish clearer docs for dashboards and benchmarking suites; client teams are encouraged to add measurements.
- Glamsterdam (PFI pipeline)
- We’ll prioritize EIPs that client teams request for the call. Besu shared the first batch; aim to review those next time:
All Core Devs - Execution (ACDE) #219, August 28, 2025 · Issue #1687 · ethereum/pm · GitHub - Repricings Meta EIP (discussion; no decisions): Add EIP: Glamstardam Gas Repricings by misilva73 · Pull Request #10206 · ethereum/EIPs · GitHub
- Purpose: group repricing work (opcodes/precompiles) under a single framing, define shared rationale and measurement methodology, and avoid one-off repricings without coordinated evidence.
- Client feedback requested: worst-case justifications, reference implementations or test vectors, and rollout cadence aligned with 60M-gas goals and devnet capacity.
- Today’s outcome: keep iterating in the PR; bring concrete perf data and test plans back to ACDE.
- PFI EIPs reviewed (context-setting only): EIP-2926, EIP-7793, EIP-7843, EIP-8012, EIP-8014.
Summary
Fusaka
Devnet-3 is targeted to finalize today while CL teams finish sync fixes. After those land next week, we’ll rerun non-finality; if recovery looks solid, we’ll spin up Devnet-5 (fix-only, to validate stability before talking dates). Blob-schedule alignment moves forward via the Osaka-style PR set (Holesky/Sepolia/Hoodi/Mainnet), which will be merged after ~24h if there’s no pushback. For the rollout, we’ll produce a default timeline that mirrors the process doc, and, in parallel, survey major stakeholders on preferred testnet order, lead-time, and change-freeze windows—so we can reconcile “process-clean” vs. “operationally-ideal” plans before scheduling.
Holesky
Consensus to deprecate Holesky a few weeks after Fusaka activates there; a public post will outline timing and migration guidance.
Gas limit
Work continues toward a 60M target. Teams will document deltas using shared dashboards/suites; Nethermind and PandaOps will improve the public docs so client teams can contribute comparable perf data.
Glamsterdam
PFI time on future calls goes first to client-requested items. The Repricings Meta EIP is the proposed umbrella for cost-model updates (opcodes/precompiles), with alignment on evidence, test vectors, and rollout planning. Author-queued PFIs (EIP-2926/7793/7843/8012/8014) were reviewed for context; no inclusion decisions today.