ePBS explained in one line: enshrined proposer-builder separation means moving key proposer–builder coordination rules into Ethereum’s protocol, so block production depends less on external relays and off-protocol arrangements than today’s MEV-Boost-style PBS.
This pillar sits under the Ethereum scaling hub. It pairs with PeerDAS explained (data availability) — ePBS is about who builds and proposes blocks, not about blob sampling.
Timing caveat: Glamsterdam-related testnet windows discussed in industry coverage (for example, a Sepolia target in late 2026) are tests, not a confirmed mainnet fork date. Specs, client readiness, and feature scope can change. Verify All Core Devs notes, published specs, and client releases before acting on a headline.
Today’s PBS vs enshrined PBS
On Ethereum today, a validator may be selected to propose a block while specialized builders assemble profitable block contents. That split lets validators access sophisticated construction without running a full builder stack. In practice, much of the coordination has relied on external infrastructure, including relays used by MEV-Boost participants.
Enshrined PBS (ePBS) proposes to place important parts of that relationship inside consensus rules: how builders commit to payloads, what proposers can verify before signing, and how missing or invalid payloads are handled. Exact mechanics depend on the active specification version under discussion or test — do not assume every ePBS design draft behaves the same.
Open questions that matter for validators and users include:
- Can smaller validators participate without heavy operational burden?
- What happens when a builder fails to deliver?
- How does the design interact with censorship resistance and latency?
- Which pieces remain optional vs mandatory at activation?
Glamsterdam: packaging name, not a finished product
Glamsterdam is a proposed Ethereum network upgrade name that groups candidate changes — commonly including ePBS and, in many roadmaps, block-level access lists (BALs). A named upgrade is a planning and testing container, not proof that every listed idea will ship unchanged to mainnet.
Sepolia (and other testnets) let client teams check that implementations agree, that validators can follow the chain, and that ordinary transactions still work. A clean testnet activation is valuable evidence — it is still only one input before any mainnet decision.
Useful checklist when you see “Glamsterdam / ePBS” news:
- Activation details — Matching fork epoch/time across client teams?
- Feature scope — Is ePBS included? Are BALs in the same activation or separate?
- Client readiness — Published compatible releases and operator instructions?
- Test artifacts — Public notes on reorgs, missed proposals, resource use, mismatches?
- Next steps — Spec changes, more tests, or only then a mainnet discussion?
Block-level access lists (related, not the same as ePBS)
Block-level access lists describe state that transactions in a block read or modify. By exposing dependencies, they may help clients find work that can execute in parallel. They are not a synonym for ePBS and do not automatically raise throughput or cut fees. Benefits depend on correct rules, client implementations, and real workloads.
Do not confuse BALs with blob data availability or PeerDAS. For DA and rollup fees, use the PeerDAS guides in this hub.
What ETH investors and L2 users should (and should not) infer
ePBS primarily concerns block production and MEV infrastructure, not a direct fee schedule for rollup users. L2 teams still care because L1 block timing, inclusion, and builder markets affect how batches land — but user fee outcomes remain multi-factor.
Investors should separate protocol development from price narratives. A Sepolia (or other testnet) milestone does not prove near-term changes to fees, ETH supply, staking rewards, or demand. Any valuation story tied to an unconfirmed mainnet scope is speculative.
Optional soft check: if you are comparing ETH market-cap scenarios under different narrative assumptions (smooth upgrade path vs delay), the scenario calculator can illustrate bag math — it cannot predict fork schedules.
Source news left on /blog (not deleted): Ethereum Glamsterdam upgrade: Sepolia ePBS. PeerDAS context: Fusaka / PeerDAS blog.
FAQ
What does ePBS mean on Ethereum?
ePBS means enshrined proposer-builder separation: putting important proposer–builder coordination into Ethereum’s protocol so the network relies less on external PBS relays and off-protocol deals. Final effects depend on the shipped specification and validator adoption.
Is Glamsterdam the same thing as ePBS?
No. Glamsterdam is an upgrade packaging name that may include ePBS and other proposals (such as block-level access lists). ePBS is one feature family inside that broader plan.
Does a Sepolia ePBS test set a mainnet date?
No. Testnet activation helps validate client implementations. Mainnet still requires review, fixes, coordinated releases, and a communicated activation plan. Dates can slip as specs evolve.
Will ePBS lower my gas fees or move ETH price?
Not in a way you can responsibly forecast from a testnet headline. ePBS targets block-building mechanics; user fees and market prices depend on many factors. Treat price claims tied to early milestones as speculation.