This previous week, simply over 100 Ethereum core contributors gathered above the Arctic Circle — in Longyearbyen, Svalbard — for the Soldøgn Interop: every 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 flooring of 200M, steady ePBS implementations working with exterior builders, and last 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 subjects.
Why Svalbard?
Svalbard is likely one of the few locations on Earth the place anybody, no matter nationality, can reside and work and not using a visa. It is also dwelling 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 would possibly 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 does not set in Svalbard. It has 24/7 uptime, similar to Ethereum, which core devs made probably the most of through the week!
Harden Glamsterdam, Scale Ethereum
The week’s objective was to harden Glamsterdam implementations and derive a goal for a post-upgrade fuel restrict flooring. Elevating the fuel restrict safely is a multi-dimensional downside and Glamsterdam tackles a number of of them: how blocks are constructed and proposed, how a lot headroom shopper implementations have beneath load, and the way state-creation prices scale alongside throughput.
In apply that meant ending the week with a steady multi-client Glamsterdam devnet working the newest ePBS, repricing and block entry record specs, together with benchmarking knowledge to anchor a reputable fuel restrict proposal.
More often than not was spent heads down writing code, usually till the early hours of the morning, punctuated by breakout classes to align on design choices and focus on longer-term roadmap gadgets.
Three EF groups offered infrastructure for the week: EthPandaOps shipped ethIQ and a panda MCP server to help groups’ agentic workflows; Protocol Assist arrange soldogn.xyz as the only supply of fact for interop targets, schedule, and notes; and the EF Digital Studio workforce captured the week on movie. Count on 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 specific how a lot time might be allotted for execution, growing the pinnacle room now we have to lift 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 check, expose edge circumstances, repair, repeat. A Tuesday-morning Builder API breakout considerably simplified the spec round validator registration, the bid/header/commitments movement, 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 check suite revealed a spot throughout each shopper implementation. By Thursday morning, CL groups had been reporting steady ePBS whereas EL-side bid pathways had 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 how one can maintain a 1 ETH-staked-builder design resilient in opposition to P2P Sybil-based liveness assaults.
By Friday, practically all purchasers had been working 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 monitor 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 might evaluate them in isolation slightly than as a single bundle. The BAL benchmark dashboard and leaderboard surfaced every shopper’s worst-case eventualities throughout the check suite — by specializing in elevating the slowest paths first, groups might raise the fuel restrict flooring throughout the board, not only for the quickest implementation.
Fuel Repricings
Glamsterdam contains quite a lot of EL fuel repricings, calibrating prices to higher match useful resource utilization at increased throughput. EIP-8037, the state-creation fuel price enhance, sits on the core: it raises the worth of writing new state so {that a} increased fuel restrict does 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 hard and fast cost_per_state_byte, with future repricing dealt with at fork boundaries slightly 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 monitor delivering the ultimate repricing numbers.
This entire arc highlights one of the crucial necessary facets of interop: the power to resolve advanced spec, implementation, testing, debugging, and design points in hours as a substitute of weeks. At their greatest, 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 flooring. This important enhance is feasible as a result of ePBS buildings the slot to provide execution extra time, BAL optimizations give purchasers the throughput headroom beneath that construction, and 8037 ensures the upper fuel restrict does not translate into runaway state development.
Different Glamsterdam Threads
Past ePBS, BALs and repricings, a lot of the remaining Glamsterdam scope was hashed out throughout breakout classes.
CL groups finalized choices on smaller Glamsterdam EIPs: EIP-8061 (exit/consolidation churn enhance) 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 workforce works by way of bounded gossip-message dimension for attestations beneath 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 a substitute, 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 relentless 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 software, demoed mid-session to a protracted stream of assault eventualities attendees advised on the spot.
Past Glamsterdam
A number of breakouts seemed towards Hegotá and the forks that comply with.
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 various signature schemes, aggregation, batching, restoration, fuel sponsorship, versatile nonces, and keystore wallets sat alongside laborious constraints round public-mempool compatibility, statelessness, and L2 DoS resistance.
A Thursday FOCIL breakout targeted on implementation updates: early prototypes had been already useful, with multi-client interop and a devoted FOCIL devnet because the rapid subsequent steps. Two notable design choices had been additionally made: disabling FOCIL throughout 2-epoch non-finality (mirroring proposer-boost circuit-breaker habits), and adopting an index-based bookmark method for compatibility with body transactions / EIP-7702.
Additional out, a long-running ETH P2P monitor sketched a QUIC-based alternative for libp2p with privacy-by-default and slot-aware integration, alongside an erasure-coded broadcast prototype that simulated ~6× quicker propagation than GossipSub on 2.4 MB payloads. The CL monitor additionally surfaced robust sentiment towards finally deprecating consolidations totally — declaring a last 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 wished 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 had 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 choices and mirrored within the meta-EIP — will change SFI’s previous position of driving devnet inclusion, beginning with Hegotá.
On the call-coordination aspect, Alex Stokes introduced he will probably be taking a three-month sabbatical beginning subsequent week, with Pari masking 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.
All the pieces Else
Along with all the above, groups used the in-person time to make progress on the whole lot from higher check 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 laborious tradeoffs round shopper range, and plenty of different subjects. The complete record of session notes is out there at soldogn.xyz.
Subsequent Steps
From right here, groups head dwelling to take what was prototyped through the week and make it production-ready. Count on the subsequent a number of weeks to be heads-down on hardening shopper implementations in opposition to the brand new specs, finalizing check protection, and turning Soldøgn’s draft PRs into merged code.
As at all times, the ultimate choices for values such because the 200M fuel restrict goal and last repricing numbers will probably be made and shared publicly on AllCoreDevs calls. Count on these to be the main subjects 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 successful! Particular shout out to EthPandaOps for whipping the group into form daily, and to everybody who labored beneath the midnight solar to ensure we hit our day by 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 ☀️
