Before Blockchains, There Was State Machine Replication

What It Covers

Turing Award winner Barbara Liskov traces the origins of blockchain consensus protocols to her 1980s distributed systems research at MIT, explaining how ViewStamp Replication and Practical Byzantine Fault Tolerance (PBFT) became the foundational architecture underlying every major blockchain protocol operating today.

Key Questions Answered

• •State Machine Replication as blockchain foundation: Every blockchain consensus mechanism descends from state machine replication principles developed in the 1980s. The core idea — that replicas maintain identical logs of ordered operations regardless of the application layer — is why Ethereum and Solana can run arbitrary smart contracts. Builders should understand SMR as the conceptual layer beneath any consensus protocol they evaluate or implement.
• •View-change protocol for fault tolerance: ViewStamp Replication solved the "embarrassing pause" problem in two-phase commit by introducing a structured primary-to-backup failover mechanism. When a primary replica stops responding, backups execute a view-change protocol electing a new primary while preserving the complete prior history. Modern blockchain leader-rotation mechanisms — used in protocols like HotStuff — directly inherit this architecture.
• •PBFT's 3f+1 replica threshold for Byzantine tolerance: Handling malicious nodes requires 3f+1 total replicas to tolerate f Byzantine failures, versus only 2f+1 for benign crash failures. PBFT addresses lying primaries by requiring two-thirds majority certificates — collections of 2f+1 signed messages confirming the same state — before committing any operation. Blockchain engineers designing validator sets should size them against this threshold explicitly.
• •Cryptographic certificates as trust anchors: PBFT introduced the use of signed certificate bundles — 2f+1 matching signed messages — as verifiable proof that a protocol checkpoint was reached honestly. This mechanism, borrowed from theoretical cryptography and made practical by PBFT, is now the standard method by which proof-of-stake blockchains like Ethereum finalize blocks and detect equivocation by validators.
• •AI shifts coding toward specification and verification: Liskov argues that as AI generates code from specifications, the critical skill becomes verifying correctness rather than writing syntax. The MIT course she co-developed with John Guttag since the late 1970s — centered on design, modularity, specifications, and verification of large systems — describes exactly the competency profile developers need to audit and manage AI-generated code effectively.