Proof of stake is a consensus mechanism that lets a blockchain agree on valid transactions by requiring participants to lock up — or “stake” — cryptocurrency as collateral rather than expending electricity. It arose as a direct response to the high energy demands of proof of work, and today secures some of the largest networks in crypto, including Ethereum after its 2022 transition.
Understanding proof of stake means understanding why any consensus mechanism exists in the first place, and what trade-offs come with this particular design.
Why Blockchains Need Consensus
A blockchain is maintained by thousands of independent computers that share no central authority. When someone broadcasts a transaction, all those computers need to agree on whether it is valid and which block it belongs to — without trusting each other. Consensus mechanisms are the rules that produce that agreement.
In proof of work, agreement is enforced through computation: miners spend real-world energy racing to solve a puzzle, and the winner earns the right to add the next block. The cost of that computation makes cheating expensive. Proof of stake takes a different approach — instead of burning energy, participants put money on the line.
How Proof of Stake Works
Validators Replace Miners
In a proof-of-stake system, the participants who propose and confirm blocks are called validators (sometimes also called stakers). To become one, you must deposit a minimum amount of the network’s native token into a special smart contract or lockup address. On Ethereum, for example, the minimum is 32 ETH. That deposit is your stake.
When it is time to create a new block, the protocol selects a validator — typically using a randomised process weighted by the size of each validator’s stake — to propose the next block. Other validators then attest to (vote on) whether that proposed block looks valid. If a supermajority agrees, the block is added to the chain.
The Role of Slashing
The security of proof of stake comes from economic punishment rather than physical cost. If a validator behaves dishonestly — for example, by trying to approve two conflicting versions of the chain at the same time (called a “double-spend” attempt) — the protocol automatically destroys (“slashes”) a portion of their staked funds.
This is the core insight: a validator with a large stake has far more to lose by cheating than to gain. The bigger the total value staked across a network, the more expensive an attack becomes.
Slashing transforms bad behaviour from a profitable gamble into a guaranteed financial loss. Security is enforced not by electricity bills, but by skin in the game.
Finality
Many proof-of-stake designs offer finality — a point at which a block is considered permanently settled and cannot be reversed without destroying an enormous amount of staked value. This is different from proof of work, where blocks are considered probabilistically confirmed (the deeper a block sits in the chain, the harder it is to reverse, but there is no hard cut-off). Faster finality can be useful for applications that need to know a transaction is truly done, such as decentralised exchanges.
Proof of Stake vs. Proof of Work
| Feature | Proof of Work | Proof of Stake |
|---|---|---|
| Who secures the chain | Miners (hardware + energy) | Validators (staked capital) |
| Security cost | Electricity and equipment | Locked collateral + slashing risk |
| Energy use | Very high | Much lower |
| New coin distribution | Block rewards to miners | Block rewards to validators |
| Hardware barrier | Significant | Lower (software + capital) |
| Attack vector | 51% of hash rate | Accumulating majority stake |
Neither design is objectively superior in every dimension. Proof of work has a longer security track record and produces coins through a process that requires external resources (energy), which some argue keeps issuance more “honest.” Proof of stake is cheaper to run and easier to participate in at scale, but it concentrates influence among large stakeholders, and its long-term security assumptions are still being tested.
Delegated and Liquid Staking
The requirement to lock up a large minimum stake creates a barrier for smaller holders. Two common solutions have emerged:
Delegated proof of stake (DPoS) — Token holders vote for a smaller set of elected validators who do the actual work. This is more efficient but more centralised, since power concentrates in whoever gets the most votes. Chains like EOS and Tron use this model.
Liquid staking — Protocols such as Lido DAO accept deposits of any size, pool them to run validators, and issue a tradeable token representing the staked position. This solves the liquidity problem (your stake is no longer frozen), but introduces smart-contract risk and can concentrate validation power in a single operator. You can learn more about the mechanics in staking explained.
Participation and Rewards
Validators earn rewards — paid in the network’s native token — for honestly proposing and attesting to blocks. These rewards come from a combination of newly issued tokens (inflation) and, on some chains, transaction fees. The effective yield depends on how much total stake is active: more validators competing for the same reward pool means lower per-validator returns.
It is important to treat staking yields as compensation for running infrastructure and bearing risk, not as a guaranteed passive income. The value of the underlying token can fall far faster than any staking reward can offset. Staking rewards are also typically subject to tax in most jurisdictions — see crypto and taxes for a primer.
Risks Worth Knowing
- Slashing risk. If you run your own validator and misconfigure it — or if a third-party liquid staking protocol has a bug — your principal can be destroyed, not just reduced in value.
- Lock-up periods. Many networks impose unstaking delays of days or weeks. You may not be able to exit during a market downturn.
- Centralisation pressure. Larger stakeholders earn more rewards, which lets them stake more, which earns them more — a compounding dynamic that can concentrate validator power over time.
- Smart-contract risk. Liquid staking and DPoS delegation both route your funds through code. Bugs in that code are a real historical source of losses; see notable hacks and failures.
Key Takeaways
- Proof of stake secures a blockchain by requiring validators to lock up capital as collateral, replacing the energy expenditure of proof of work.
- Dishonest validators face slashing — automatic, protocol-enforced destruction of part of their stake — making attacks expensive without burning electricity.
- Validators are chosen to propose blocks through a randomised, stake-weighted selection process, and other validators vote to confirm each block.
- Liquid staking and delegated proof of stake lower the barrier to participation but introduce their own risks, including smart-contract bugs and centralisation.
- Staking yields are compensation for work and risk, not guaranteed returns — the value of staked tokens can still fall.
- Proof of stake has a shorter security track record than proof of work, and its long-term attack resistance remains an open research question.
Next up: Other Consensus Mechanisms