This past week, conscionable implicit 100 Ethereum halfway contributors gathered supra the Arctic Circle — successful Longyearbyen, Svalbard — for the Soldøgn Interop: a week of aggravated enactment connected the Glamsterdam web upgrade.
Soldøgn followed past year's Berlinterop, but returned to the format utilized by Amphora 🏺, Edelweiss 🏔️, and Nyota ✨: a single-track week of focused, multi-client advancement toward a circumstantial upgrade — successful this case, hardening Glamsterdam.
By Friday, the radical had delivered connected its 3 halfway goals: alignment connected a post-Glamsterdam state bounds level of 200M, unchangeable ePBS implementations moving with outer builders, and last EIP-8037 repricing numbers locked in. Meaningful advancement was besides made connected Hegotá features similar FOCIL and autochthonal relationship abstraction, arsenic good arsenic a slew of different topics.

Why Svalbard?
Svalbard is 1 of the fewer places connected Earth wherever anyone, careless of nationality, tin unrecorded and enactment without a visa. It's besides location to the Global Seed Vault and the Arctic World Archive, 2 cold-storage facilities tunneled into the permafrost extracurricular Longyearbyen. Between them they clasp backups of crops, books, films, manuscripts, and root codification that humanity mightiness request a 1000 years from now, including a snapshot of Ethereum's root code. Last but not least, from precocious April done August, the prima doesn't acceptable successful Svalbard. It has 24/7 uptime, conscionable similar Ethereum, which halfway devs made the astir of during the week!
Harden Glamsterdam, Scale Ethereum
The week's extremity was to harden Glamsterdam implementations and deduce a people for a post-upgrade state bounds floor. Raising the state bounds safely is simply a multi-dimensional occupation and Glamsterdam tackles respective of them: however blocks are built and proposed, however overmuch headroom lawsuit implementations person nether load, and however state-creation costs standard alongside throughput.
In signifier that meant ending the week with a unchangeable multi-client Glamsterdam devnet moving the latest ePBS, repricing and artifact entree database specs, on with benchmarking information to anchor a credible state bounds proposal.
Most of the clip was spent heads down penning code, often until the aboriginal hours of the morning, punctuated by breakout sessions to align connected plan decisions and sermon longer-term roadmap items.
Three EF teams provided infrastructure for the week: EthPandaOps shipped ethIQ and a panda MCP server to enactment teams' agentic workflows; Protocol Support acceptable up soldogn.xyz arsenic the azygous root of information for interop goals, schedule, and notes; and the EF Digital Studio squad captured the week connected film. Expect the precise archetypal interop documentary 🔜!

ePBS
Beyond cleaning up the proposer/builder relationship, ePBS restructures slots by adding deadlines for artifact construction, payload reveal, and attestations. This makes explicit however overmuch clip tin beryllium allocated for execution, expanding the caput country we person to rise the state limit.
Teams kicked disconnected the week aiming for a 4 EL × 4 CL Glamsterdam devnet by Monday evening. The archetypal attempts surfaced capable issues to propulsion the people to Tuesday, erstwhile a 4×3 configuration ran stably capable for accent investigating to begin.
From there, the remainder of the week was an ePBS hardening cycle: accent test, exposure borderline cases, fix, repeat. A Tuesday-morning Builder API breakout substantially simplified the spec astir validator registration, the bid/header/commitments flow, the spot exemplary for builder payments, and circuit-breaker behavior. Mid-week debugging zeroed successful connected cross-client borderline cases — notably astir execution-request invalidation of beacon requests, wherever a caller trial suite revealed a spread crossed each lawsuit implementation. By Thursday morning, CL teams were reporting unchangeable ePBS portion EL-side bid pathways were inactive being debugged; those resolved done Thursday into Friday. Two questions stay genuinely contentious for ACD: whether a petition signature should perpetrate to the receiving builder, and however to support a 1 ETH-staked-builder plan resilient against P2P Sybil-based liveness attacks.
By Friday, astir each clients were moving unneurotic connected glamsterdam-devnet-2 with the outer builders pipeline tested end-to-end!

BAL Optimizations
If ePBS is the consensus-layer broadside of the Glamsterdam scaling story, the execution furniture counterpart has 2 ascendant pieces: state repricings and Block-Level Access Lists. By giving clients capable accusation astir a block's read/write acceptable up front, BALs alteration parallel execution, batched I/O, and parallel state-root computation, each of which find however large a artifact clients tin comfortably handle.
The Soldøgn BAL way ran connected its ain devnets, abstracted from the Glamsterdam ePBS chains, truthful optimization benchmarks weren't entangled with consensus-layer stabilization work. Each optimization sat down its ain diagnostic emblem truthful the week's measurement enactment could comparison them successful isolation alternatively than arsenic a azygous bundle. The BAL benchmark dashboard and leaderboard surfaced each client's worst-case scenarios crossed the trial suite — by focusing connected raising the slowest paths first, teams could assistance the state bounds level crossed the board, not conscionable for the fastest implementation.

Gas Repricings
Glamsterdam includes a fig of EL state repricings, calibrating costs to amended lucifer assets usage astatine higher throughput. EIP-8037, the state-creation state outgo increase, sits astatine the core: it raises the terms of penning caller authorities truthful that a higher state bounds doesn't construe into unbounded authorities growth.
Heading into Soldøgn, the 8037 spec carried dynamic per-state-byte pricing tied to the artifact state limit, which made investigating combinatorially achy (one fuzz matrix per state bounds band) and benchmarking astir intractable. Teams agreed aboriginal successful the week to driblet dynamic pricing successful favour of a fixed cost_per_state_byte, with aboriginal repricing handled astatine fork boundaries alternatively than wrong a fork.
The accounting exemplary itself took a much iterative path. The Monday breakout moved state-gas accounting from mid-execution to end-of-call-frame; a Tuesday follow-up closed retired relationship instauration costs, codification deposit costs, and CREATE-transaction reverts; Wednesday surfaced reservoir refund/refill borderline cases that forced a rethink. The Thursday breakout reverted accounting to opcode level, having concluded that the existent complexity sat successful the reservoir model, not successful the accounting computation. By Friday the spec had stabilized connected bal-devnet-6, with the BAL way delivering the last repricing numbers.
This full arc highlights 1 of the astir important aspects of interop: the quality to resoluteness analyzable spec, implementation, testing, debugging, and plan issues successful hours alternatively of weeks. At their best, interop weeks tin compress a period of asynchronous advancement into each day!
By Friday, the 3 threads converged connected the header fig for the week: a credible 200M post-Glamsterdam state bounds floor. This important summation is imaginable due to the fact that ePBS structures the slot to springiness execution much time, BAL optimizations springiness clients the throughput headroom nether that structure, and 8037 ensures the higher state bounds doesn't construe into runaway authorities growth.

Other Glamsterdam Threads
Beyond ePBS, BALs and repricings, astir of the remaining Glamsterdam scope was hashed retired crossed breakout sessions.
CL teams finalized decisions connected smaller Glamsterdam EIPs: EIP-8061 (exit/consolidation churn increase) was included successful glamsterdam-devnet-1; EIP-8080 (exits via the consolidation queue) was declined for inclusion; EIP-8045 (slashed-validator work removal) was scoped down to proposer duties wrong the look-ahead model only; and EIP-7688 (SSZ unchangeable containers) remains successful Glamsterdam scope but is held retired of glamsterdam-devnet-1 portion the squad works done bounded gossip-message size for attestations nether progressive lists.
A Wednesday-morning EL/CL sync architecture breakout deferred EIP-8237 retired of Glamsterdam successful favour of preserving optionality for a longer-term "top-up sync" architecture successful a aboriginal fork. In its place, the country agreed to draught an EIP that normalizes forkchoiceUpdated / newPayload / getPayload sequencing, specifies a snap-sync initiation handshake, and tightens valid/invalid consistency betwixt the motor API surfaces.
Hardening was a changeless taxable of the week. A Thursday league covered fork-choice compliance investigating frameworks, the Diamond repo of reproducible CL edge-case scenarios, and buildoor, PandaOps's external-builder investigating tool, demoed mid-session to a agelong watercourse of onslaught scenarios attendees suggested connected the spot.

Beyond Glamsterdam
Several breakouts looked toward Hegotá and the forks that follow.
A deliberately proposal-agnostic league connected native Account Abstraction kicked things off, moving done the requirements and constraints immoderate aboriginal plan indispensable satisfy. Feature-set goals similar alternate signature schemes, aggregation, batching, recovery, state sponsorship, flexible nonces, and keystore wallets sat alongside hard constraints astir public-mempool compatibility, statelessness, and L2 DoS resistance.
A Thursday FOCIL breakout focused connected implementation updates: aboriginal prototypes were already functional, with multi-client interop and a dedicated FOCIL devnet arsenic the contiguous adjacent steps. Two notable plan decisions were besides made: disabling FOCIL during 2-epoch non-finality (mirroring proposer-boost circuit-breaker behavior), and adopting an index-based bookmark attack for compatibility with framework transactions / EIP-7702.
Further out, a long-running ETH P2P way sketched a QUIC-based replacement for libp2p with privacy-by-default and slot-aware integration, alongside an erasure-coded broadcast prototype that simulated ~6× faster propagation than GossipSub connected 2.4 MB payloads. The CL way besides surfaced beardown sentiment toward yet deprecating consolidations wholly — declaring a last fork that supports them, past forcing exit-then-redeposit afterwards — arsenic the cleaner semipermanent reply to validator-set authorities growth.

ACD Process
On Wednesday afternoon, Nixo and Ansgar, the 2 ACDE co-leads, ran a league to cod input from halfway contributors astir the ACD process. The league revisited the headliner construct, debated the pros and cons of having a strawmap, and formalized EIP SFI criteria. The country broadly wanted to support headliners but loosen the EIP-vs-theme rigidity, accepting "theme + campaigner EIP" arsenic a viable pattern. The straw map's per-fork twelvemonth assignments past 2026 were flagged arsenic overcanonicalized and apt to beryllium softened. A caller four-point SFI explanation was enactment forward, with ACDT signaling readiness and ACDE/ACDC retaining the last call. A caller prioritization-ordering process — produced aft CFI decisions and reflected successful the meta-EIP — volition regenerate SFI's aged relation of driving devnet inclusion, starting with Hegotá.
On the call-coordination side, Alex Stokes announced helium volition beryllium taking a three-month sabbatical starting adjacent week, with Pari covering ACDC moderation successful the interim and Barnabas filling successful for ACDT. All told: Nixo and Ansgar seat ACDE, Pari is interim connected ACDC, and Mario, Barnabas, and Danceratopz rotate ACDT moderation.
Everything Else
In summation to each of the above, teams utilized the in-person clip to marque advancement connected everything from amended trial harnesses (compressing Hive feedback loops from hours to minutes), to engine-API plumbing improvements (gossip dedup, batched calls, and light-client-driven caput discovery), to hard tradeoffs astir lawsuit diversity, and galore different topics. The afloat database of league notes is disposable astatine soldogn.xyz.

Next Steps
From here, teams caput location to instrumentality what was prototyped during the week and marque it production-ready. Expect the adjacent respective weeks to beryllium heads-down connected hardening lawsuit implementations against the caller specs, finalizing trial coverage, and turning Soldøgn's draught PRs into merged code.
As always, the last decisions for values specified arsenic the 200M state bounds people and last repricing numbers volition beryllium made and shared publically connected AllCoreDevs calls. Expect these to beryllium the large topics of the adjacent week!
Thank you precise overmuch to everyone who came each the mode up to 78°N and made this week a success! Special outcry retired to EthPandaOps for whipping the radical into signifier each day, and to everyone who worked nether the midnight prima to marque definite we deed our regular goals — including the Ethrex crew, joining america for their archetypal interop. It was an incredibly productive week, and luckily we'll person a afloat abbreviated movie to retrieve it by ☀️

20 hours ago









English (US)