// learn / ethereum-scaling
Ethereum Scaling: PeerDAS, ePBS & L2
Ethereum’s scaling roadmap is changing how data availability and block building work — from PeerDAS and Fusaka to ePBS / Glamsterdam and the Layer 2 stack that depends on them. This hub gathers plain-English explainers for investors and L2 users who want the mechanism, the limits, and the metrics that matter.
Who this hub is for
Rollup users, app builders, and investors who keep hearing “PeerDAS,” “blobs,” or “ePBS” in upgrade headlines and want a durable explanation — not just a launch-day news flash.
What you will learn
- What PeerDAS (peer data availability sampling) does for blob capacity and why L2 fees care
- How ePBS / Glamsterdam reframes block building and proposer–builder separation for everyday users
- How to read capacity and fee claims without treating fork calendars as fixed promises
- Where daily Fusaka / Glamsterdam coverage on the blog fits next to these evergreen guides
Protocol timing can change; treat dates as educational context and verify against current Ethereum client and developer documentation.
Guides in this hub
Guide
PeerDAS Explained: Fusaka, Blobs & What L2 Users Should Know
A durable explainer of PeerDAS (Peer Data Availability Sampling) in the Fusaka era: how sampling differs from downloading every blob, what that means for rollups, and how to read capacity claims without treating upgrade timing as fixed.
Guide
ePBS Explained: Glamsterdam, Proposer-Builder Separation & What to Watch
Plain-English ePBS (enshrined proposer-builder separation) for ETH holders, validators, and L2 users — including Glamsterdam context, how it differs from external PBS, and why testnet milestones are not mainnet promises.
Supporting guide
What PeerDAS Means for L2 Throughput and Rollup Fees
A shorter supporting guide: the path from PeerDAS blob capacity to rollup fees, why TPS headlines mislead, and which indicators L2 users should compare.
Coming soon
These guides are planned for this hub. Titles may refine slightly when they publish.
Upcoming
Blob data availability after PeerDAS