Ethereum Glamsterdam upgrade explained: what it is and why it matters

Ethereum core developers are moving from the recent Fusaka upgrade into a new phase called “Glamsterdam.” It is a paired upgrade to both halves of the network. The execution layer will get “Amsterdam.” The consensus layer will get “Gloas.” Together, they focus on fairness, efficiency, and long-term scaling.

The headline feature is enshrined Proposer-Builder Separation (ePBS), tracked as EIP-7732. This change splits who builds blocks from who proposes them. It reduces the power of any single party to reorder or censor transactions for profit. A second piece, EIP-7928, adds Block-level Access Lists. This lets a block declare which accounts and storage it will touch before execution. Clients can then fetch data once and reuse it, speeding up execution and making gas use steadier.

Glamsterdam is still in scope-setting. More EIPs may join the bundle. Developers point to a 2026 target, but testing and audits will shape the date.

MEV and the promise of ePBS

What is MEV and why it hurts users

MEV stands for maximal extractable value. It is the extra profit gained by reordering, inserting, or censoring transactions in a block. When MEV is unfair, users pay more, trades slip, and some actors gain an edge. This can look like sandwich attacks on swaps or selective inclusion during NFT mints.

Today, Ethereum reduces these issues with off-chain relays. These relays connect builders, who arrange transactions for revenue, with proposers, who choose a block to publish. This setup works, but it adds trust, opacity, and centralization risk. If a few relays dominate, they become choke points.

How ePBS changes the game

Under ePBS, builders still assemble blocks. But they commit to block contents cryptographically before proposers can see them. Proposers pick the best-paying block without access to the raw transactions. The full contents are revealed only after the chain finalizes the choice. This makes frontrunning and targeted manipulation much harder.

For readers looking for Ethereum Glamsterdam upgrade explained in one line: ePBS moves the builder–proposer market on-chain with cryptographic guarantees, and removes trusted relays from the center.

Benefits for users and validators

• Less information leakage before block inclusion, limiting abusive reordering.
• Clearer incentives for validators: pick the highest bid, reveal later.
• Fewer single points of failure, since the protocol, not relays, organizes flow.
• More predictable transaction outcomes for users during busy times.

Inside EIP-7732: the mechanics of fairness

Sealed bids and late reveal

Builders craft a block and seal it with a cryptographic commitment. Proposers receive bids tied to these sealed blocks. They select the top bid without seeing the contents. After selection and finalization, the block opens and the transactions execute. This model narrows the chance to exploit pending order flow.

What happens to relays

Relays do not fully vanish, but their role shrinks. With ePBS enshrined, the protocol provides the core separation and flow. Any remaining middleware must compete on reliability and performance, not on privileged access. This reduces centralization risk.

Trade-offs and open areas

• Builders may consolidate if scale gives them an edge. Monitoring builder diversity will be key.
• There could be new forms of out-of-protocol collusion. Transparency and client safeguards will matter.
• Client teams must coordinate on the cryptographic flow, timeouts, and penalties to keep liveness strong.

EIP-7928: Block-level Access Lists and faster execution

Why predeclaring access helps

Today, clients discover which accounts and storage each transaction touches as they execute. That means repeated lookups, cache misses, and more variance in block processing time. EIP-7928 flips the process. A block states its planned reads and writes up front. Clients fetch this data once and reuse it.

Performance gains you can expect

• Smoother gas costs, since execution is more predictable for clients.
• Lower latency for block execution, which supports tighter timing in consensus.
• Cleaner optimization paths for client teams, since the access footprint is known early.

Rollups and L2s benefit too

Rollups batch thousands of transactions and then post data to Ethereum. With access lists at the block level, rollup sequencers and proof systems can align data fetching with Ethereum’s execution rhythm. This reduces redundant work and makes settlement more efficient.

Another part of Ethereum Glamsterdam upgrade explained is how EIP-7928 complements ePBS. Together, they reduce manipulation surfaces and speed up the part of the system that executes transactions.

Who needs to prepare and how to get ready

Validators and staking providers

• Track client releases that add ePBS logic. Test on devnets and public testnets as they appear.
• Update operational playbooks for new timing, bid acceptance, and penalties.
• Diversify clients where possible to spread implementation risk.

Builders and MEV searchers

• Plan for sealed-bid logic and new commitment flows.
• Invest in latency, reliability, and pricing models in a more competitive builder market.
• Adopt transparency tools to show fair practices and attract order flow.

Wallets, dapps, and infrastructure

• Review any reliance on mempool visibility, private order flow, or relay-specific features.
• Adjust gas and slippage defaults based on more stable execution times.
• Use SDKs and APIs that track access list behavior as clients roll out previews.

Timeline, risks, and how to measure success

When will it ship?

The scope is not final. Developers aim for 2026, but this depends on audits, testnets, and real-world feedback. Expect iterative devnets, shadow forks, and client release candidates before a mainnet date is set.

Key risks to watch

• Builder centralization: if a few firms dominate, fairness gains shrink. Community monitoring and incentives will matter.
• Edge-case liveness: sealed bids and reveals add timing steps. Clients must handle timeouts and penalties robustly.
• Relay transition: as roles shift, gaps could appear. Clear migration guidance will help operators stay stable.

How we will know it worked

• Lower share of harmful MEV strategies that rely on seeing contents pre-inclusion.
• More diverse builder landscape and fewer single points of failure.
• Narrower variance in block execution time and fewer outlier gas spikes.

This is why you will see Ethereum Glamsterdam upgrade explained by core developers as both a fairness and performance push. It aims to lock in better incentives while laying groundwork for future scaling.

What comes next after Glamsterdam

Foundation for future scaling

By moving separation into the protocol and smoothing execution, Ethereum prepares for more rollup throughput and lighter node operation. This continues the trend set by Fusaka, which aimed to cut node costs, and opens the door to deeper data availability and execution upgrades down the road.

Better user experience by default

Users should see fewer nasty surprises in busy times. Trades and mints should face less predatory ordering. Gas should follow a steadier pattern as clients waste less time on repeated data fetches. The experience will not be perfect, but it should be more fair and more reliable.

Open collaboration remains key

None of this works without broad collaboration. Client teams, researchers, staking providers, builders, searchers, wallets, and rollups each have a role. The upgrade is an opportunity to align incentives with the network’s long-term health.

In short, the Ethereum Glamsterdam upgrade explained is a coordinated plan to reduce MEV abuse and make execution faster. ePBS (EIP-7732) moves the builder–proposer market into the protocol with cryptographic safety, and Block-level Access Lists (EIP-7928) help clients execute blocks more efficiently. If testing holds and teams deliver, users should get a fairer, smoother Ethereum in 2026 and beyond.

(Source: https://www.coindesk.com/tech/2025/12/20/ethereum-s-glamsterdam-upgrade-aims-to-fix-mev-fairness)

For more news: Click Here

FAQ