Market Cap: 24h Vol: BTC: BTC Dom:
Gold: S&P 500: EUR/USD: Oil (BRENT):

Byzantine Generals Problem

The Byzantine Generals Problem comes from a 1982 paper by computer scientists Leslie Lamport, Robert Shostak, and Marshall Pease, who used the story of feuding generals surrounding an enemy city to model an older question in distributed computing: how can independent parties agree on a single, honest version of events when some of them might be liars and messages can be delayed, lost, or forged?

The paper's real contribution was mathematical rather than military. It proved that a group can only reach reliable agreement if fewer than one-third of its members are faulty or malicious, a boundary later formalized as needing at least 3f+1 participants to tolerate f bad actors. That threshold underpins what is now called Byzantine Fault Tolerance, the property a system needs to keep functioning correctly even when some nodes act dishonestly or go silent.

Public blockchains face a harder version of the puzzle, since anyone can join anonymously and there is no fixed roster of generals to poll for a vote. Rather than adopting the voting-based algorithms used in permissioned systems, Bitcoin's 2008 design made agreement expensive instead of purely social: miners on the Bitcoin network compete to solve a computational puzzle, and the chain representing the most accumulated work is treated as the truth, so lying becomes economically irrational rather than merely hard to detect.

Later networks reached the same goal with economic stakes instead of raw computation, exemplified by Proof of Stake, where validators risk their own capital and forfeit it for dishonest behavior. Every consensus mechanism in crypto is, at its core, a different practical answer to that 1982 question about trusting strangers.

Related Articles