consensus mechanism
/kun-SEN-sus MEK-uh-niz-um/ · noun · Development · Origin: 2008
Definitions
The algorithm by which a decentralized network agrees on the current state of the blockchain without a central authority. Common mechanisms include proof of work, proof of stake, delegated proof of stake, and proof of authority. Each makes different trade-offs between security, decentralization, and performance.
In plain English: The rulebook that all computers in a blockchain network follow to agree on which transactions are valid, without anyone being in charge.
Example: The new chain uses a novel consensus mechanism that achieves finality in two seconds, though skeptics question whether it's truly decentralized.
Origin Story
The algorithmic solution to making strangers agree without trust
Consensus mechanisms in distributed systems date to Leslie Lamport's work on the **Byzantine Generals Problem** (1982), which asked how distributed nodes can agree on a value when some nodes might be malicious or faulty.
Bitcoin's **Proof of Work** (2008) was the breakthrough that solved Byzantine consensus in an open, permissionless network. Miners compete to solve cryptographic puzzles, and the network accepts the longest chain. It was elegant but energy-intensive.
Ethereum's 2022 switch to **Proof of Stake** ('The Merge') reduced energy consumption by 99.95%. Other mechanisms emerged too: Delegated Proof of Stake, Proof of Authority, Proof of History (Solana), and Proof of Space (Chia). Each trades off decentralization, security, and speed.
Coined by: Leslie Lamport, Robert Shostak, Marshall Pease (Byzantine fault tolerance)
Context: SRI International, 1982 (Lamport); Bitcoin, 2008 (Nakamoto)
Fun fact: Lamport's Byzantine Generals paper used the metaphor of generals surrounding a city needing to coordinate an attack. He originally called it the 'Albanian Generals Problem' but changed it after a colleague pointed out it might offend Albanians.