A dive in five depths · Blockchain

How proof-of-stake
& The Merge really work

On September 15, 2022, a live system securing over $200 billion replaced its entire consensus engine without stopping for a single second — and most explanations of how it works stop at "validators instead of miners." This guide goes all the way down: capital held hostage, mathematical finality, and the engineering of the swap itself. Stop wherever you like — each depth is complete on its own. (Part 3 of the trilogy; it builds on Guide 1 and Guide 2.)

New to it? Levels 1–2 are plenty.
Working dev? Land at 3.
Want the truth? Reach the abyss.
begin the descent
LVL 1
▸ Surface · 0–10m

Skin in the game

Guide 2 made writing history expensive by burning electricity. Proof-of-stake makes it expensive a completely different way — and the difference is where the cost sits.

Proof-of-work and proof-of-stake answer the same question — "how do we make writing to the ledger cost something un-fakeable?" — but they put the cost in opposite places. In proof-of-work, the cost is external and ongoing: electricity, burned continuously, by honest and dishonest participants alike. In proof-of-stake, the cost is internal and conditional: validators lock up their own capital as a bond, and the protocol destroys the bond of anyone caught cheating. Behaving honestly is nearly free. Cheating is financially catastrophic. Same destination — writing history is expensive — opposite mechanism.

💂
Proof-of-work · pay guards forever

Loyalty rented by the hour

You hire guards and pay wages forever; they stay honest because robbing the vault would end the paychecks. Security is payroll — and if the paychecks thin out (Guide 2's fee-only future), so does the protection. The guards keep their weapons regardless.

🔒
Proof-of-stake · guards post a bond

Their own fortune in the vault

Each guard posts their own fortune inside the vault. Rob it and their deposit burns first. And the decisive difference: the protocol can see and destroy a cheater's stake — but no protocol can confiscate an attacker's warehouse of ASICs. After a PoW attack the weapon survives; after a PoS attack it's ash.

One objection arrives immediately, so let's meet it head-on: "doesn't this just mean the rich rule?" Rewards are proportional to stake — but PoW rewards are equally proportional to hashrate. Neither is one-person-one-vote; both are one-dollar-one-lottery-ticket. What proof-of-stake actually changes isn't who wins the lottery. It's that misbehavior costs the misbehaver directly, and that there are no economies of scale — the thirty-third million dollar of stake earns exactly the same rate as the first, with no cheap-electricity arbitrage and no ASIC oligopoly to climb. (The full critique gets a fair trial in the abyss.)

The takeaway for Level 1

Proof-of-work makes history expensive to write. Proof-of-stake makes it expensive to lie about — and hands the network a weapon proof-of-work never had: the attacker's own money. Honesty is cheap; provable dishonesty is fatal.

Bond, lottery, burn — now the real vocabulary. What does a validator actually do all day, measured in 12-second heartbeats? ↓
LVL 2
▸ Sunlit zone · 10–50m

Validators, slots & epochs: a day in the life

"Proof-of-stake" is a family; this is Ethereum's, the one that matters for The Merge. Here's the cast, the clock, and a stepper that walks a block from proposed to irreversible.

A validator is 32 ETH deposited plus a machine kept online. Not a mining farm — a consumer box, a NUC on a shelf. That 32 ETH is the bond from Level 1: it's exactly what slashing burns. The chain runs on a metronome: a slot is 12 seconds (one block expected per slot), and an epoch is 32 slots = 6.4 minutes, the accounting period.

Each slot, the protocol pseudo-randomly appoints one proposer to build the block and a committee of attesters to vote on it. An attestation is a signed vote — "this block is the correct head of the chain" — plus the checkpoint votes Level 3 explains. Every active validator attests exactly once per epoch, so roughly every 6.4 minutes the entire validator set has weighed in. Where PoW votes continuously in burned watts, PoS casts explicit signed ballots on a fixed schedule — and that schedule is precisely what makes provable finality possible.

The randomness comes from RANDAO: each proposer must reveal a pre-committed random contribution that gets mixed into a shared pot, so nobody can predict or meaningfully steer who's chosen next. Get your attestations in correctly and on time and you earn a small steady reward (on the order of 3–4% a year); go offline and you leak at roughly the same rate — an absent validator is a slow drain, not an execution. The guillotine is reserved for actual lying, and that's Level 3. Today the set is roughly a million active validators backing tens of millions of ETH — a bond worth tens of billions of dollars.

Step through one block's journey from proposal to finalized. This is Level 3's theory in motion — watch the attestation weight climb past two-thirds, then watch a later checkpoint lock the earlier one shut:

Finality Stepper — how a block becomes irreversible step 0 / 7
the beacon clock · 12s slots · 32 slots = 1 epoch
attestation weight (share of all staked ETH voting)
0%
✦ Checkpoint status
0
0/7
!

"Staking is just mining with money"

No race is running. Mining is a continuous open competition — more hardware, more chances to win. Staking is a scheduled rota: the protocol appoints each slot's proposer in advance from the bonded set. A whale can't "stake harder" to win a given slot; they simply hold more raffle tickets. And stakes come in fixed 32-ETH units — large stakers run many identical validators, not one giant one.

Votes every 12 seconds — but votes for what, and when does a block stop being "probably safe" and become mathematically irreversible? ↓
LVL 3
▸ Twilight zone · 50–200m

Finality & slashing: the machinery

Two algorithms working together turn those votes into an irreversible chain — and one brutal rule makes lying about them suicidal.

Ethereum's consensus is two layers stacked. A fork-choice rule keeps the chain progressing block by block, and a finality gadget periodically pours concrete over the history behind it.

LMD-GHOST is the fork choice: at every fork, follow the branch carrying the greatest weight of the latest attestations — the "heaviest-attested subtree," not PoW's longest chain. Because it counts votes across all descendants, brief network splits resolve toward wherever the stake actually is. Casper FFG is the finality gadget: the first block of each epoch is a checkpoint, and attestations double as checkpoint ballots. When two-thirds of all staked ETH votes for a checkpoint it becomes justified; when the next checkpoint is justified on top of it, the earlier one becomes finalized. In steady state that's finality every two epochs — about 12.8 minutes.

What "finalized" actually means — the sharpest claim in this guide

Finalized is not "very probably safe" (proof-of-work's best offer). Casper FFG guarantees that two conflicting finalized checkpoints cannot exist unless at least ⅓ of all staked ETH signed provably contradictory votes — and those contradictory signatures are slashable evidence. So reverting finality costs an attacker, mechanically and unavoidably, one-third of all staked ETH — well north of $10 billion, burned. A PoW reorg costs opex you'd have spent anyway; a PoS reversion costs confiscated principal. That's the difference between "probabilistic" and "economic" finality.

Slashing — the guillotine. There are exactly two slashable crimes, and both are equivocation — signing two contradictory things:

// the two slashable offenses
// both slashable crimes are equivocation — signing two contradictory things
def is_slashable(a, b):              // a, b = two signed votes from one validator
    if a.target_epoch == b.target_epoch and a != b:
        return DOUBLE_VOTE          // two different votes for the same slot/epoch
    if a.source < b.source and b.target < a.target:
        return SURROUND_VOTE        // b's vote wraps around a's — rewriting history
    return None                       // anyone can submit a+b as on-chain evidence

A double proposal is two different blocks for the same slot. A double vote is two different attestations for the same target epoch, and a surround vote is one attestation whose range wraps around another — the move a validator would make to retroactively rewrite its own checkpoint history. The enforcement is itself decentralized: anyone can submit the two offending signatures as on-chain evidence and collect a whistleblower reward. The penalty starts around 1 ETH, then adds a correlation penalty that scales with how much other stake was slashed in the same window — up to the entire 32 ETH.

The punishment is calibrated to conspiracy, not accident

A single misconfigured validator that double-signs loses roughly 1 ETH and gets ejected — survivable. But a coordinated attack, where a third of the stake equivocates together, triggers the correlation penalty in full: everyone involved loses everything. This is the answer to the old "nothing-at-stake" objection — the worry that with costless votes you'd rationally vote on every competing fork. Votes are no longer costless; each one carries a bond on exactly one chain. (For the record: total slashings ever are a few hundred validators, overwhelmingly duplicate-key operational accidents, not attacks.)

The inactivity leak — the doomsday spring. What if finality simply stalls — say a war partitions the internet and a third of validators vanish? If more than four epochs pass without finality, the protocol begins leaking stake from the non-participating validators, quadratically, until the online set once again represents two-thirds and finality resumes. The chain is engineered to heal through a catastrophe — it just gets to redefine "everyone" down to whoever is still present.

That machine ran for 21 months guarding an empty chain — a $20 billion dress rehearsal. Now the event itself: bolting it onto a live, $200 billion Ethereum without dropping a single block ↓
LVL 4
▸ Midnight zone · 200–1000m

The Merge: swapping engines mid-flight

The event you came for. Why it happened, the architecture that made it possible, the trigger, the night itself, what changed, and the fork that failed — the trilogy's loop closing.

Why. Proof-of-stake was Ethereum's stated destination from the start (~2014) — proof-of-work was the proven bootstrap, never the goal. Three drivers pushed the switch: the energy indictment (Guide 2's abyss), issuance (paying watt-priced wages for security the bond model gets nearly free), and finality (the upgrade over probabilistic settlement). To keep everyone committed, the code even carried a difficulty bomb: a mechanism that made PoW mining exponentially harder over time — a self-imposed doomsday clock, repeatedly delayed but never removed, that made not merging eventually impossible.

The architecture insight — the part engineers love. Ethereum split itself into two programs joined by a local RPC interface, the Engine API. The execution layer (Geth, Nethermind, Besu, Erigon) holds the EVM, state, transactions, and mempool — everything users touch. The consensus layer (Prysm, Lighthouse, Teku, Nimbus, Lodestar) holds everything from Levels 2–3 — slots, attestations, fork choice, finality. The Merge was the moment the execution layer stopped listening to PoW miners and started taking orders from the consensus layer.

// the handoff, over the Engine API
// after the Merge, the consensus layer (CL) drives the execution layer (EL)
// over a local RPC — the Engine API. The EL no longer decides anything itself.

CL → EL:  engine_newPayload(block)         // "here's a block — is it valid? execute it."
EL → CL:  { status: VALID }                  // EL replays txs, checks state, reports back

CL → EL:  engine_forkchoiceUpdated(head)   // "this is the canonical head now."
// consensus (which head, is it final) lives entirely in the CL; the EL just executes.

Nothing users touch changed hands — the engine underneath did. The community's own metaphor was swapping a plane's engines mid-flight; the precise version is better still. The new engine — the beacon chain — had been flying in formation, live, with real stake, since December 1, 2020: 21 months producing empty blocks, proving itself with ~$20 billion of bonded ETH before it ever carried a single transaction. Engineers will recognize the shape immediately — it's a parallel-run / strangler-fig migration, executed on a system that could never be taken offline. Step through it:

The Merge — swapping engines mid-flight step 0 / 6
Execution layer · PoW miners
cumulative work → TTD 5.875 × 10²²
consensus layer now drives execution ↑
Consensus layer · Beacon chain (PoS)
⌁ ETHW fork (PoW continues)
Milestone
0
0/6
!

Why the trigger was a work threshold, not a date or block number

The switch fired at a Terminal Total Difficulty — cumulative chain work reaching 58,750,000,000,000,000,000,000 (5.875 × 10²²) — not at a block height. A block number is gameable: miners facing obsolescence within days had every incentive to manipulate timing and fork around a known height. A cumulative-work threshold can't be reached without actually doing the work, so there was nothing to game. The switch happened at block 15,537,393 (the last PoW block) at 06:42:42 UTC on September 15, 2022; the next block was proposed by a validator, one slot later, with no downtime.

What changed, and what pointedly didn't. This is where nearly everyone is wrong:

"The Merge made Ethereum cheaper and faster."
It did neither. Gas fees and capacity were essentially unchanged — block time only shifted from ~13.5s average to a fixed 12s. The Merge was a consensus upgrade, not a scalability one; scaling is the job of rollups and danksharding, a different program entirely.
"Balances, contracts, or history were migrated or reset."
Nothing moved. Balances, contract state, addresses, private keys, the EVM, and the entire transaction history were untouched — every PoW block remains canonical history. Only the mechanism for producing new blocks changed.
"Then nothing really changed."
Energy fell ~99.95% (a national grid's load down to a few thousand home servers); issuance fell ~90% (~13,000 ETH/day to miners became ~1,600 ETH/day to validators — the "triple halving," which with the EIP-1559 fee burn can make supply shrink); and finality became economic (~12.8 min) instead of forever-probabilistic. Miners' hardware went obsolete overnight.

The aftermath fork — legitimacy's final exam

Miners holding suddenly-worthless rigs forked the chain to keep proof-of-work alive ("ETHW"). Same history, same balances, real hashpower behind it — and it collapsed to near-nothing within days. Exchanges, apps, users, and — quietly decisive — stablecoin issuers (Circle and Tether can each honor only one chain for USDC/USDT) all followed the proof-of-stake chain. Guide 1's abyss argued that legitimacy is ultimately social; The Merge ran that experiment at $200B scale and proved it: hashpower does not confer legitimacy — the community's coordinated choice does.

Merged, finalized, 99.95% greener. Now the honest abyss: what proof-of-stake's critics get right, and where the real sharp edges still are ↓
LVL 5
▸ The abyss · 1000m+

Critiques & frontiers

Proof-of-stake won the argument for Ethereum. It did not end the argument. Every critique here gets steelmanned — the guide earns your trust by refusing to cheerlead.

If the last four levels sold you completely, this one is the correction. Some objections to proof-of-stake are real and unresolved; a few are weaker than they sound. Here's the honest ledger, including a head-to-head scorecard that is really the whole trilogy's summary.

Pod 1 Weak subjectivity — the philosophical price

A proof-of-work node syncing from nothing can find the true chain by pure arithmetic — most cumulative work wins. That's objective. Proof-of-stake has a subtle hole: validators who long ago exited (bond withdrawn, nothing left to slash) could conspire to sign a fake alternate history from back when they were active, and a node syncing from genesis can't arithmetically tell it apart from the real one. The fix is a weak-subjectivity checkpoint: a new or long-offline node must obtain a recent trusted hash — in practice, from the same source it trusted for the client software. The honest verdict: this is a real concession — PoS bootstrapping needs a pinch of social trust PoW doesn't — that in practice collapses into trust you were already extending.

Pod 2 Stake centralization — the serious one

Liquid staking (Lido has at times approached ~⅓ of all stake) and exchange staking (Coinbase, Binance, Kraken) concentrate delegated validation. The thresholds are worth memorizing:

Stake controlledWhat it enablesStill cannot
Stall finality (and start bleeding via the inactivity leak)Forge a signature, mint invalid coins, or change the rules — every node still validates (Guide 1, L3)
½Dominate fork choice; censor
Finalize a preferred chain

Protocol-level caps were rejected (delegates would just split cosmetically), so the pressure is social, market, and technical — distributed validator technology (DVT), incentives for solo staking. And note the symmetry: Guide 2 showed PoW centralizes at pools, manufacturers, and geography. Both systems' real centralization risk lives one layer above the consensus math.

Pod 3 MEV & the builder pipeline

Block proposers today mostly outsource block construction to specialized builders bidding through relays (MEV-Boost / proposer-builder separation). It exists because transaction ordering is worth money (MEV — maximal extractable value). It worries people because it's a censorship chokepoint: after the Tornado Cash sanctions (Aug 2022), blocks from OFAC-compliant relays briefly peaked around three-quarters of all blocks before neutral relays clawed it back. Neutrality here is being defended in the market layer, not the protocol — an open frontier, not a settled win.

Pod 4 PoW vs PoS — the honest scorecard

The trilogy's summary in one table:

Proof-of-workProof-of-stake
Cost basisExternal opex, forever (energy)Bonded capital, at risk
Attack costBuy/run unobtainable hardwareAcquire ⅓–⅔ of stake (buying it inflates the price against you)
Attacker's morning afterKeeps the hardware; can re-attackBond burned; community can fork the rest away — the weapon is destroyed
FinalityProbabilistic (deepen to reduce risk)Economic, absolute at ~12.8 min
Bootstrapping trustObjective (most work wins)Weak-subjective (needs a recent checkpoint)
EnergyA national grid≈ zero
Centralization gravityHardware, energy, geographyCapital, delegation
Track recordBitcoin: 15+ years unbrokenEthereum PoS: since 2022, so far unbroken
Pod 5 The critiques that don't fully land — and the ones that linger

"Rich get richer." Returns are roughly proportional in both systems, and PoS actually removes the economies of scale mining has — but staking compounds with near-zero opex, where mining recycles revenue into costs. The compounding point lingers. "Circular security" (the token secures the chain that gives the token value) is true, and PoW is one step less circular — but at Bitcoin's fee-only end-state, its security also leans on token value (Guide 2's budget problem, mirrored). "PoS is just fiat with extra steps" is wrong — issuance and validity are rule-bound and node-enforced, not discretionary. What's true is that PoS trades physics-anchoring for capital-anchoring, and that's a values choice — which is exactly why Bitcoin isn't merging, and why both philosophies now run their flagship experiments in parallel.

Pod 6 After the Merge — the road that opened

(As of mid-2026 — verify anything newer.) Shapella (Apr 2023) enabled withdrawals, ending the lock-in that had made pre-Merge staking an act of faith. Dencun (Mar 2024) added blobs / proto-danksharding — the scalability work the Merge was so often miscredited with. Pectra (May 2025) raised the maximum effective balance from 32 to 2048 ETH (EIP-7251), letting large operators consolidate many validators into one — worth flagging since Level 2 taught "32-ETH units." The active research frontier is single-slot finality: collapsing that ~12.8-minute window toward seconds.

You've reached the bottom of the stack

Three dives, one idea: a ledger nobody owns stays honest because writing it is expensive, lying to it is detectable, and — when the machines disagree — humans choose which chain deserves the name. Proof-of-work anchors that cost in physics; proof-of-stake anchors it in capital. In September 2022, one chain swapped from the first to the second in real time, at a scale of $200 billion, without dropping a block — and the community, not the hardware, decided it counted.