Consensus Mechanisms Compared
A closer look at how proof of work, proof of stake, and other consensus mechanisms actually differ.
Jump to section
What to remember
- Consensus mechanisms let a decentralized network agree on the ledger's true state without a central authority.
- Proof of work uses computational competition; proof of stake uses financial collateral and slashing.
- Other mechanisms exist and suit different network designs and priorities.
- No single consensus mechanism is objectively superior for every use case.
Why blockchains need a consensus mechanism
A blockchain network has many independent participants, each holding a copy of the ledger. A consensus mechanism is the agreed-upon process the network uses to decide which new block gets added next, and to keep every participant's copy of the ledger in agreement without relying on a single trusted authority.
Proof of work
Proof of work requires participants (miners) to compete by solving a computationally difficult puzzle. The first to solve it earns the right to propose the next block and receives a reward. The difficulty of the puzzle makes it expensive to attempt rewriting past blocks, since doing so would require redoing the computational work for every block after the one being altered.
Proof of stake
Proof of stake instead selects who proposes the next block based on the amount of cryptocurrency they've committed (staked) as collateral, rather than computational competition. Validators who act dishonestly can have a portion of their stake destroyed, a penalty called slashing. This removes the heavy energy use of mining while still giving participants a real, forfeitable stake in behaving honestly.
Proof of Work
Proof of Stake
What a participant spends or risks to earn the right to propose the next block -- computing power under proof of work, staked capital under proof of stake.
Other consensus approaches
- Delegated proof of stake: token holders vote for a smaller set of validators to produce blocks on their behalf.
- Practical Byzantine Fault Tolerance (and variants like Tendermint): validators exchange multiple rounds of messages to agree on a block before it's finalized, common in networks prioritizing fast finality.
- Proof of authority: a small set of pre-approved, identified validators produce blocks — common in private or consortium networks, not typical for open public ones.
Delegated proof of stake, PBFT/Tendermint, and proof of authority are each a distinct category of their own -- different ways a network can decide who proposes the next block, not slower or faster versions of proof of work or proof of stake.
| Mechanism | Who proposes the next block | Main trade-off | Typically used by |
|---|---|---|---|
| Proof of work | Whichever miner solves the puzzle first | High energy use for strong, battle-tested security | Open, permissionless payment networks like Bitcoin |
| Proof of stake | A validator selected by staked collateral | Lower energy use, but security depends on stake being genuinely at risk (slashing) | Most modern general-purpose public networks |
| Delegated proof of stake | A smaller, voted-in set of validators | Faster and cheaper, but concentrates block production among fewer parties | Networks prioritizing throughput over maximal decentralization |
| PBFT / Tendermint-style | Validators after multiple rounds of message exchange | Fast, deterministic finality, but more messaging overhead as validator count grows | Networks prioritizing fast, final confirmation |
| Proof of authority | A small, pre-approved, identified set of validators | High throughput and predictability, at the cost of open participation | Private or consortium networks, not typical for open public ones |
How the five mechanisms covered above compare on who proposes blocks, their main trade-off, and where each is typically used.
There is no universally "best" mechanism
Each approach makes different trade-offs between decentralization, security, speed, and energy use. A mechanism that suits a global, permissionless payment network may not suit a fast, identity-verified enterprise network, and vice versa.
What to remember
- Consensus mechanisms let a decentralized network agree on the ledger's true state without a central authority.
- Proof of work uses computational competition; proof of stake uses financial collateral and slashing.
- Other mechanisms exist and suit different network designs and priorities.
- No single consensus mechanism is objectively superior for every use case.
Related research and concepts
Nakamoto Consensus
Read the Nakamoto Consensus glossary definition
Proof of Authority
Read the Proof of Authority glossary definition
Proof of Burn
Read the Proof of Burn glossary definition
Proof of History
Read the Proof of History glossary definition
Sybil Attack
Read the Sybil Attack glossary definition
Eclipse Attack
Read the Eclipse Attack glossary definition
Proof of Stake vs. Proof of Work: A Network Security Comparison
Read the research article
Hedera
Read the Hedera research page
EOS
Read the EOS research page
XRP
Read the XRP research page
Tron
Read the Tron research page
Byzantine Fault Tolerance
Read the Byzantine Fault Tolerance glossary definition