All Core Devs - Execution (ACDE) #219, August 28, 2025

ACDE TL;DW

Fusaka

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 :robot:

Action Items

  1. Fusaka
  1. Holesky
  • Agreement to retire Holesky a few weeks after Fusaka activates there. A blog post with timelines/migration notes is planned for next week.
  1. Gas limit (toward 60M)
  1. Glamsterdam (PFI pipeline)

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.

1 Like