Ethereum Glamsterdam Upgrade: ePBS, BALs, and What Is Actually Planned

Ethereum upgrades attract two kinds of noise: confident performance promises and fake instructions telling holders to “upgrade” their ETH. The Ethereum Glamsterdam upgrade deserves a calmer reading. Glamsterdam activated on Sepolia on October 6, but the Ethereum Foundation postponed its planned October 26 Hoodi activation while developers investigate how EIP-8037 interacts with mainnet smart contracts. No replacement Hoodi date or mainnet activation date has been set. This article separates the scheduled design from the guarantees and places the upgrade in our broader crypto market news framework.

What Is the Ethereum Glamsterdam Upgrade?

Glamsterdam combines the names Gloas, for the consensus-layer upgrade, and Amsterdam, for the execution-layer upgrade. It follows Fusaka, which activated in December 2025 and introduced PeerDAS for more scalable blob data availability.

The official ethereum.org Glamsterdam roadmap describes three goals: prepare Ethereum for parallel processing, expand capacity by changing how blocks are built and propagated, and control long-term state-database growth. Think of it as remodeling a busy freight terminal. Ethereum is not merely adding another loading bay; it is changing who packs each container, when inspectors receive it, and which inventory records are available before inspection begins.

How ePBS Changes Block Building

Today, many validators use MEV-Boost and third-party relays to receive blocks from specialized builders. This proposer-builder separation exists largely outside Ethereum’s core rules. EIP-7732, called enshrined proposer-builder separation (ePBS), proposes moving the exchange between proposer and builder into the protocol.

Under ePBS, the consensus block and execution payload have separate timing rules. A Payload Timeliness Committee attests to whether the builder released the payload on time, while protocol-enforced payments make the exchange less dependent on trusted relay behavior. Ethereum.org says the design expands the payload propagation window from roughly two seconds to about nine seconds.

That extra time matters because large payloads are harder to broadcast and verify quickly. A wider window can support higher gas limits and more blob data without placing the entire task on the critical path. It does not mean relays instantly disappear: builders and proposers may still use middleware for services beyond the protocol’s basic exchange.

How Block-Level Access Lists Prepare Parallel Processing

Ethereum execution is difficult to parallelize because a client may not know which accounts or storage slots a transaction will touch until it runs the transaction. Two transactions that modify the same state cannot safely be treated like independent jobs.

EIP-7928 proposes block-level access lists (BALs) containing the state accesses and post-execution values associated with a block. The easiest analogy is a warehouse pick map. If workers know which shelves every order will use, unrelated orders can be fetched at the same time; overlapping orders can be scheduled carefully.

BALs can let clients pre-load state, perform parallel disk reads, and identify non-overlapping work. Because the list includes resulting values, it may also support executionless state updates during synchronization. The important distinction is that BALs prepare and accelerate parallel work; they do not by themselves guarantee a specific mainnet transactions-per-second figure.

Gas Repricing: Some Actions Can Get Cheaper While Others Cost More

“Glamsterdam lowers gas” is too broad. The upgrade is considering several repricing changes intended to make gas reflect the hardware and storage burden of each operation more accurately.

For example, the roadmap discusses a lower intrinsic cost for a basic transaction while proposals such as EIP-8037 increase the cost of creating persistent state. The policy logic is straightforward: ordinary transfers can be cheaper, while operations that permanently enlarge Ethereum’s database should pay more of their long-term cost.

Actual fees remain a product of gas used, the protocol’s gas schedule, and demand for blockspace. Even if one transaction type receives a lower fixed gas charge, congestion can still push the market fee higher. For the underlying mechanics, see our Ethereum gas fees guide.

Where the Upgrade Stands on October 24, 2026

Glamsterdam activated on Sepolia at epoch 353,024 on October 6. The next announced step was a Hoodi activation at epoch 132,352 on October 26, paired with a Hoodi gas-limit increase to 200 million. On October 22, the Ethereum Foundation postponed that activation. Core developers made the decision at ACDE #248 to investigate interactions between EIP-8037's state-creation gas changes and mainnet smart contracts. The old Hoodi epoch, timestamp, and gas-limit schedule were removed; there is no replacement date yet.

The official Glamsterdam roadmap continues to describe Q4 2026 as the expected mainnet window, but that is not an activation commitment. The Glamsterdam meta EIP lists ePBS, BALs, intrinsic transaction gas changes, state-creation and state-access repricing, validator churn changes, and several smaller execution-layer proposals as scheduled for inclusion. Its activation table records Sepolia, while Hoodi and mainnet remain blank. The practical reading is simple: the feature set is much firmer than it was during early devnets, but a successful Sepolia fork did not eliminate the need to test application compatibility before advancing.

This is a scheduling rollback, not a rollback of Hoodi chain history. It also does not mean that Sepolia reverted or that Glamsterdam was canceled. Client interoperability, application testing, audits, and release readiness still have to converge. A scheduled EIP is not permission to treat untested behavior or performance estimates as guaranteed.

What Users, Developers, and Validators Should Do

ETH holders

Do nothing solely because of the fork. Your balance does not require conversion. Keep wallet software current through its official channel, ignore unsolicited support messages, and never enter a seed phrase into an “upgrade” page.

Application developers

Watch the final EIP set and re-test gas-sensitive assumptions. The reason for the Hoodi delay is directly relevant here: EIP-8037 changes how state creation is metered, and developers are investigating its interaction with deployed mainnet contracts. Teams that rely on fixed gas stipends, hardcoded gas limits, detailed traces, or low-level block-building behavior should review the official repricing impact guide, client release notes, and current testnet results rather than infer behavior from headlines.

Validators and node operators

Hoodi operators should remove the superseded October 26 activation from custom configurations and install only client versions whose release notes explicitly incorporate the postponement. Check both execution- and consensus-client guidance, plus validator and builder tooling. Mainnet operators do not need to change anything because of this Hoodi delay. For any future activation, follow official client notes rather than binaries linked from social-media replies.

Risks and Limits

• Schedule risk: the Hoodi postponement demonstrates that test results can move milestones. Q4 2026 is a planning window, not an activation timestamp.
• Scope risk: the scope is frozen, but the meta EIP remains in review and scheduled proposals can still change before mainnet.
• Implementation risk: a coordinated hard fork touches multiple clients. Interoperability testing reduces, but cannot erase, software and chain-split risk.
• Centralization trade-offs: higher capacity is useful only if ordinary operators can still validate the chain. This is why state growth and propagation time are part of the design discussion.
• Fee uncertainty: repricing does not guarantee every user a fixed percentage reduction. Usage and blockspace demand remain variable.
• Market risk: a protocol upgrade does not guarantee ETH appreciation. Crypto prices are volatile; use only capital you can afford to lose and do your own research.

Frequently Asked Questions

When will Glamsterdam activate?

Sepolia activated on October 6. The planned October 26 Hoodi activation was postponed on October 22, and no replacement Hoodi date has been announced. Ethereum.org still shows Q4 2026 as the expected mainnet window, but no mainnet epoch or timestamp is confirmed. Use the latest Ethereum Foundation protocol announcement and the meta EIP—not an old calendar entry—before acting.

Will Glamsterdam make Ethereum process 10,000 TPS?

No official source guarantees that figure. ePBS and BALs are structural changes designed to unlock higher capacity and future parallel execution. Real throughput will depend on the final specification, client performance, gas-limit policy, and workload.

Will every transaction become cheaper?

Not necessarily. Some base transaction costs may fall, while state-creating operations may become more expensive. Network demand will continue to influence the fee paid.

Is ePBS the same as MEV-Boost?

No. MEV-Boost is off-protocol middleware used by many validators today. ePBS places a basic proposer-builder exchange and payment mechanism inside Ethereum’s consensus rules, although optional middleware may remain.

Do I need new ETH after the hard fork?

No. There is no legitimate “Glamsterdam ETH” conversion. Keep your existing keys private and treat conversion requests as scams.

Primary Sources

• Ethereum Foundation: Glamsterdam on Hoodi postponed
• Ethereum Foundation: superseded Hoodi testnet announcement
• Ethereum.org: Glamsterdam roadmap
• EIP-7773: Glamsterdam hardfork meta
• Ethereum Foundation: Glamsterdam repricing impact

Bottom Line

Glamsterdam is best understood as plumbing for the next phase of Ethereum scaling. ePBS reorganizes block construction, BALs expose state dependencies for faster validation and future parallel execution, and repricing tries to align fees with real resource costs. Those are substantial goals. They are not promises of a fixed TPS number, a universal fee discount, or a market outcome.

Apply the same schedule-versus-certainty test when reading about the Polkadot 2026 tokenomics change or the evolving GENIUS Act stablecoin rules: verify the latest primary source, identify what has actually activated, and keep forecasts separate from protocol or legal facts.

Follow the official roadmap and client announcements as the scope matures. The Hoodi delay is a useful reminder that a testnet schedule is part of the safety process, not a promise that the next stage must happen on time. This article is educational, not financial advice. Protocol plans can change, crypto assets are volatile, and you should independently verify time-sensitive details before acting. (NFA / DYOR)