This previous week, simply over 100 Ethereum core contributors gathered above the Arctic Circle — in Longyearbyen, Svalbard — for the Soldøgn Interop: per week of intense work on the Glamsterdam community improve.
Soldøgn adopted final 12 months’s Berlinterop, however returned to the format utilized by Amphora 🏺, Edelweiss 🏔️, and Nyota ✨: a single-track week of targeted, multi-client progress towards a particular improve — on this case, hardening Glamsterdam.
By Friday, the group had delivered on its three core targets: alignment on a post-Glamsterdam fuel restrict ground of 200M, steady ePBS implementations operating with exterior builders, and remaining EIP-8037 repricing numbers locked in. Significant progress was additionally made on Hegotá options like FOCIL and native account abstraction, in addition to a slew of different matters.
Why Svalbard?
Svalbard is likely one of the few locations on Earth the place anybody, no matter nationality, can stay and work with out a visa. It is also residence to the International Seed Vault and the Arctic World Archive, two cold-storage services tunneled into the permafrost outdoors Longyearbyen. Between them they maintain backups of crops, books, movies, manuscripts, and supply code that humanity may want a thousand years from now, together with a snapshot of Ethereum’s supply code. Final however not least, from late April by way of August, the solar would not set in Svalbard. It has 24/7 uptime, identical to Ethereum, which core devs made essentially the most of through the week!
Harden Glamsterdam, Scale Ethereum
The week’s aim was to harden Glamsterdam implementations and derive a goal for a post-upgrade fuel restrict ground. Elevating the fuel restrict safely is a multi-dimensional drawback and Glamsterdam tackles a number of of them: how blocks are constructed and proposed, how a lot headroom consumer implementations have underneath load, and the way state-creation prices scale alongside throughput.
In observe that meant ending the week with a steady multi-client Glamsterdam devnet operating the most recent ePBS, repricing and block entry record specs, together with benchmarking information to anchor a reputable fuel restrict proposal.
More often than not was spent heads down writing code, typically till the early hours of the morning, punctuated by breakout periods to align on design selections and talk about longer-term roadmap objects.
Three EF groups supplied infrastructure for the week: EthPandaOps shipped ethIQ and a panda MCP server to help groups’ agentic workflows; Protocol Help arrange soldogn.xyz as the one supply of fact for interop targets, schedule, and notes; and the EF Digital Studio crew captured the week on movie. Anticipate the very first interop documentary 🔜!
ePBS
Past cleansing up the proposer/builder relationship, ePBS restructures slots by including deadlines for block building, payload reveal, and attestations. This makes express how a lot time could be allotted for execution, growing the pinnacle room we have now to boost the fuel restrict.
Groups kicked off the week aiming for a 4 EL × 4 CL Glamsterdam devnet by Monday night. The primary makes an attempt surfaced sufficient points to push the goal to Tuesday, when a 4×3 configuration ran stably sufficient for stress testing to start.
From there, the remainder of the week was an ePBS hardening cycle: stress take a look at, expose edge circumstances, repair, repeat. A Tuesday-morning Builder API breakout considerably simplified the spec round validator registration, the bid/header/commitments stream, the belief mannequin for builder funds, and circuit-breaker habits. Mid-week debugging zeroed in on cross-client edge circumstances — notably round execution-request invalidation of beacon requests, the place a brand new take a look at suite revealed a niche throughout each consumer implementation. By Thursday morning, CL groups have been reporting steady ePBS whereas EL-side bid pathways have been nonetheless being debugged; these resolved by way of Thursday into Friday. Two questions stay genuinely contentious for ACD: whether or not a request signature ought to decide to the receiving builder, and the right way to preserve a 1 ETH-staked-builder design resilient towards P2P Sybil-based liveness assaults.
By Friday, practically all purchasers have been operating collectively on glamsterdam-devnet-2 with the exterior builders pipeline examined end-to-end!
BAL Optimizations
If ePBS is the consensus-layer aspect of the Glamsterdam scaling story, the execution layer counterpart has two dominant items: fuel repricings and Block-Stage Entry Lists. By giving purchasers sufficient details about a block’s learn/write arrange entrance, BALs allow parallel execution, batched I/O, and parallel state-root computation, all of which decide how massive a block purchasers can comfortably deal with.
The Soldøgn BAL observe ran by itself devnets, separate from the Glamsterdam ePBS chains, so optimization benchmarks weren’t entangled with consensus-layer stabilization work. Every optimization sat behind its personal function flag so the week’s measurement work may examine them in isolation reasonably than as a single bundle. The BAL benchmark dashboard and leaderboard surfaced every consumer’s worst-case eventualities throughout the take a look at suite — by specializing in elevating the slowest paths first, groups may raise the fuel restrict ground throughout the board, not only for the quickest implementation.
Fuel Repricings
Glamsterdam consists of numerous EL fuel repricings, calibrating prices to higher match useful resource utilization at increased throughput. EIP-8037, the state-creation fuel value improve, sits on the core: it raises the value of writing new state so {that a} increased fuel restrict would not translate into unbounded state development.
Heading into Soldøgn, the 8037 spec carried dynamic per-state-byte pricing tied to the block fuel restrict, which made testing combinatorially painful (one fuzz matrix per fuel restrict band) and benchmarking practically intractable. Groups agreed early within the week to drop dynamic pricing in favor of a set cost_per_state_byte, with future repricing dealt with at fork boundaries reasonably than inside a fork.
The accounting mannequin itself took a extra iterative path. The Monday breakout moved state-gas accounting from mid-execution to end-of-call-frame; a Tuesday follow-up closed out account creation prices, code deposit prices, and CREATE-transaction reverts; Wednesday surfaced reservoir refund/refill edge circumstances that compelled a rethink. The Thursday breakout reverted accounting to opcode stage, having concluded that the actual complexity sat within the reservoir mannequin, not within the accounting computation. By Friday the spec had stabilized on bal-devnet-6, with the BAL observe delivering the ultimate repricing numbers.
This entire arc highlights one of the vital necessary elements of interop: the flexibility to resolve complicated spec, implementation, testing, debugging, and design points in hours as a substitute of weeks. At their finest, interop weeks can compress a month of asynchronous progress into every day!
By Friday, the three threads converged on the headline quantity for the week: a reputable 200M post-Glamsterdam fuel restrict ground. This important improve is feasible as a result of ePBS buildings the slot to provide execution extra time, BAL optimizations give purchasers the throughput headroom underneath that construction, and 8037 ensures the upper fuel restrict would not translate into runaway state development.
Different Glamsterdam Threads
Past ePBS, BALs and repricings, many of the remaining Glamsterdam scope was hashed out throughout breakout periods.
CL groups finalized selections on smaller Glamsterdam EIPs: EIP-8061 (exit/consolidation churn improve) was included in glamsterdam-devnet-1; EIP-8080 (exits through the consolidation queue) was declined for inclusion; EIP-8045 (slashed-validator obligation elimination) was scoped right down to proposer duties inside the look-ahead window solely; and EIP-7688 (SSZ steady containers) stays in Glamsterdam scope however is held out of glamsterdam-devnet-1 whereas the crew works by way of bounded gossip-message dimension for attestations underneath progressive lists.
A Wednesday-morning EL/CL sync structure breakout deferred EIP-8237 out of Glamsterdam in favor of preserving optionality for a longer-term “top-up sync” structure in a future fork. As an alternative, the room agreed to draft an EIP that normalizes forkchoiceUpdated / newPayload / getPayload sequencing, specifies a snap-sync initiation handshake, and tightens legitimate/invalid consistency between the engine API surfaces.
Hardening was a continuing theme of the week. A Thursday session lined fork-choice compliance testing frameworks, the Diamond repo of reproducible CL edge-case eventualities, and buildoor, PandaOps’s external-builder testing device, demoed mid-session to an extended stream of assault eventualities attendees recommended on the spot.
Past Glamsterdam
A number of breakouts appeared towards Hegotá and the forks that observe.
A intentionally proposal-agnostic session on native Account Abstraction kicked issues off, working by way of the necessities and constraints any future design should fulfill. Characteristic-set targets like different signature schemes, aggregation, batching, restoration, fuel sponsorship, versatile nonces, and keystore wallets sat alongside onerous constraints round public-mempool compatibility, statelessness, and L2 DoS resistance.
A Thursday FOCIL breakout targeted on implementation updates: early prototypes have been already practical, with multi-client interop and a devoted FOCIL devnet because the quick subsequent steps. Two notable design selections have been additionally made: disabling FOCIL throughout 2-epoch non-finality (mirroring proposer-boost circuit-breaker habits), and adopting an index-based bookmark strategy for compatibility with body transactions / EIP-7702.
Additional out, a long-running ETH P2P observe sketched a QUIC-based substitute for libp2p with privacy-by-default and slot-aware integration, alongside an erasure-coded broadcast prototype that simulated ~6× sooner propagation than GossipSub on 2.4 MB payloads. The CL observe additionally surfaced sturdy sentiment towards finally deprecating consolidations solely — declaring a remaining fork that helps them, then forcing exit-then-redeposit afterwards — because the cleaner long-term reply to validator-set state development.
ACD Course of
On Wednesday afternoon, Nixo and Ansgar, the 2 ACDE co-leads, ran a session to gather enter from core contributors concerning the ACD course of. The session revisited the headliner assemble, debated the professionals and cons of getting a strawmap, and formalized EIP SFI standards. The room broadly needed to maintain headliners however loosen the EIP-vs-theme rigidity, accepting “theme + candidate EIP” as a viable sample. The straw map’s per-fork 12 months assignments previous 2026 have been flagged as overcanonicalized and more likely to be softened. A brand new four-point SFI definition was put ahead, with ACDT signaling readiness and ACDE/ACDC retaining the ultimate name. A brand new prioritization-ordering course of — produced after CFI selections and mirrored within the meta-EIP — will exchange SFI’s previous position of driving devnet inclusion, beginning with Hegotá.
On the call-coordination aspect, Alex Stokes introduced he shall be taking a three-month sabbatical beginning subsequent week, with Pari protecting ACDC moderation within the interim and Barnabas filling in for ACDT. All advised: Nixo and Ansgar chair ACDE, Pari is interim on ACDC, and Mario, Barnabas, and Danceratopz rotate ACDT moderation.
Every part Else
Along with all the above, groups used the in-person time to make progress on the whole lot from higher take a look at harnesses (compressing Hive suggestions loops from hours to minutes), to engine-API plumbing enhancements (gossip dedup, batched calls, and light-client-driven head discovery), to onerous tradeoffs round consumer range, and plenty of different matters. The complete record of session notes is obtainable at soldogn.xyz.
Subsequent Steps
From right here, groups head residence to take what was prototyped through the week and make it production-ready. Anticipate the subsequent a number of weeks to be heads-down on hardening consumer implementations towards the brand new specs, finalizing take a look at protection, and turning Soldøgn’s draft PRs into merged code.
As all the time, the ultimate selections for values such because the 200M fuel restrict goal and remaining repricing numbers shall be made and shared publicly on AllCoreDevs calls. Anticipate these to be the foremost matters of the subsequent week!
Thanks very a lot to everybody who got here all the best way as much as 78°N and made this week a hit! Particular shout out to EthPandaOps for whipping the group into form every single day, and to everybody who labored underneath the midnight solar to verify we hit our every day targets — together with the Ethrex crew, becoming a member of us for his or her first interop. It was an extremely productive week, and by chance we’ll have a full brief movie to recollect it by ☀️
