BR Academy
Intro to Blockchain: How It Works and Why It Matters
0%
Exit course
Consensus and Security·Lesson 19 of 25·12 min

Proof of Stake Explained

The Concept

Proof of Stake (PoS) — used by Ethereum since 2022, and by Solana, Cardano, and most newer networks — solves the same consensus problem as Proof of Work, but swaps "cost in electricity" for "cost in locked-up capital." Instead of miners competing to burn electricity solving a puzzle, validators lock up (stake) a meaningful amount of the network's own token as collateral. The protocol then pseudo-randomly selects one staked validator to propose each new block, roughly proportional to how much they've staked — more stake means a higher chance of being chosen, similar to tickets in a raffle.

The security model flips from "expensive to compute" to "expensive to misbehave." If a selected validator proposes an invalid block, signs two conflicting blocks at the same height, or otherwise attacks the network, the protocol can slash their stake — permanently destroying a portion or all of the capital they locked up. This is the "costly to attack" property the consensus lesson described, just paid for upfront in capital rather than continuously in electricity. Honest validators who do their job correctly earn rewards (newly issued tokens plus transaction fees); dishonest ones lose real money.

Proof of Stake has a few notable differences from Proof of Work worth understanding. First, energy use: PoS networks don't need warehouses of specialized mining hardware running around the clock, so Ethereum's move to PoS cut its energy consumption by over 99% according to the Ethereum Foundation's own published estimates. Second, the barrier to becoming a validator is capital, not hardware or electricity access — Ethereum requires staking 32 ETH to run a solo validator, though staking pools let smaller holders combine funds to participate. Third, attacking the network means an attacker's own capital is directly at risk and provably destroyable by the protocol itself, whereas in PoW an attacker's mining hardware keeps its resale value even after a failed attack.

Critics of PoS raise the "nothing at stake" concern — in theory, a validator could cheaply sign multiple competing chain histories since signing costs almost nothing. Modern PoS designs answer this directly with slashing: validators who get caught signing conflicting blocks lose their entire stake, making the "sign everything" strategy financially suicidal rather than free.

There's an important distinction between running your own validator and delegating or pooling your stake, since most individual holders do the latter. Solo validating requires meeting a minimum stake (32 ETH on Ethereum, worth tens of thousands of dollars), running reliable always-on infrastructure, and accepting slashing risk directly if your setup misbehaves or goes offline at the wrong moment. Staking pools and liquid staking services let holders with far less capital contribute their tokens to a shared pool that runs the validator infrastructure on everyone's behalf, splitting rewards proportionally; some of these services even issue a tradeable receipt token representing the staked position, so the capital isn't fully locked and illiquid. This lowers the barrier to participating in securing the network, though it also concentrates influence in whichever staking services attract the most delegated stake — a centralization trade-off worth weighing against Proof of Work's own tendency toward mining pool concentration.

Finality is another concept PoS networks handle somewhat differently from PoW. Many modern PoS designs include an explicit "finality" mechanism, where after a certain number of blocks and a formal voting round among validators, a block is marked as mathematically guaranteed irreversible — a stronger and more precisely defined guarantee than Proof of Work's "probabilistically very unlikely to be reversed after enough confirmations." This is a design detail worth knowing when comparing chains, since "finalized" and "confirmed" aren't always interchangeable terms depending on which consensus family a given chain uses.

Worked Example

Imagine a simplified staking round with three validators: Alice stakes 100 tokens, Bob stakes 50 tokens, and Carol stakes 350 tokens. The protocol runs a weighted random selection for who proposes the next block — Carol, with 70% of total staked tokens (350 of 500), has roughly a 70% chance of being chosen for any given block over time, Alice about 20%, Bob about 10%. Say Carol is selected and proposes a valid block; she earns the block reward. But suppose Carol instead tries to double-sign two different versions of the same block to double-spend a transaction. Other validators detect the two conflicting signed messages (both are public and both carry Carol's cryptographic signature), submit proof of the violation to the network, and the protocol automatically slashes a large portion of Carol's 350-token stake — a loss far larger than any gain she could have made from the attack, which is exactly the deterrent the system is designed to create.

Exercise

Write two or three sentences comparing Proof of Work and Proof of Stake: where does the "cost of attacking" live in each system (hardware and electricity vs. capital at risk of slashing), and which cost do you think is easier for outside observers to verify is real? There's no single right answer — the goal is to connect each mechanism back to the "something costly" principle from the consensus lesson.

Recap

  • Proof of Stake replaces mining with staking: validators lock up capital and are chosen to propose blocks proportional to their stake.
  • Misbehavior is punished by slashing — destroying some or all of a validator's staked capital — making dishonesty directly costly rather than merely energy-wasteful.
  • PoS dramatically cuts energy use compared to PoW while preserving the same core idea: making an attack expensive in a way that can't be faked.

Resources

← Proof of Work Explained Security and Attack Vectors →