Early distributed consensus protocols assumed network computers were honest; Practical Byzantine Fault Tolerance proved that computer clusters can reach mathematical agreement even when one-third of the servers are actively malicious traitors. Developed in 1999 by Turing Award laureate Barbara Liskov, this sleeping giant became the consensus engine behind modern enterprise blockchains.

In distributed computing, keeping thousands of banking servers in perfect sync is easy if every computer tells the truth. However, if a sophisticated hacker compromises several servers and commands them to send conflicting financial numbers to their peers, traditional distributed networks collapse into chaos.
MIT computer scientists created a mathematical voting system designed to defeat traitors. Operating like a courtroom of skeptical judges, servers cross-verify every proposed transaction in a three-stage voting round, ensuring that the network agrees on the exact truth even if one out of every three servers is lying.
Overlooked for a decade before the cryptocurrency revolution, PBFT is the foundation of high-speed consensus. By processing thousands of financial transactions per second, by eliminating energy-wasting mining rigs, and by defending enterprise blockchains against rogue actors, traitor-proof consensus protects global digital ledgers.
Practical byzantine fault tolerance and proactive recovery
Our growing reliance on online services accessible on the Internet demands highly available systems that provide correct service without interruptions. Software bugs, operator mistakes, and malicious attacks are a major cause of service interruptions and they can cause arbitrary behavior, that is, Byzantine faults. This article describes a new replication algorithm, BFT, that can be used to build highly available systems that tolerate Byzantine faults. BFT can be used in practice to implement real services: it performs well, it is safe in asynchronous environments such as the Internet, it incorporates mechanisms to defend against Byzantine-faulty clients, and it recovers replicas proactively. The recovery mechanism allows the algorithm to tolerate any number of faults over the lifetime of the system provided fewer than 1/3 of the replicas become faulty within a small window of vulnerability. BFT has been implemented as a generic program library with a simple interface. We used the library to implement the first Byzantine-fault-tolerant NFS file system, BFS. The BFT library and BFS perform well because the library incorporates several important optimizations, the most important of which is the use of symmetric cryptography to authenticate messages. The performance results show that BFS performs 2% faster to 24% slower than production implementations of the NFS protocol that are not replicated. This supports our claim that the BFT library can be used to build practical systems that tolerate Byzantine faults.
Ask this paper your own questions, or keep browsing the verified research catalogue.