Practical byzantine fault tolerance and proactive recovery

By Miguel Oom Temudo de Castro, Barbara H. Liskov. 2002

2,563 citations recorded by the source corpus.

Subfields: Artificial Intelligence, Computer Networks and Communications

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

In Artificial Intelligence

In Computer Networks and Communications

Citations in the corpus

Geppetto: Versatile Verifiable Computation (2015, background): “Prior work on verifying computation focused on narrow classes of computation [32, 51], relied on physical-security assumptions [41, 47], assumed uncorrelated failures [19, 20], or achieved good asymptotics [2, 28, 30, 31, 33, 38, 44] but impractical concrete performance [46, 50].”
Pinocchio: Nearly Practical Verifiable Computation (2013, background): “Other systems rely on replication, and hence assume failures are uncorrelated [1, 7, 8, 55].”
Verifying computations with state (2013, background): “Unfortunately, the faults, and their effects, may not be visible as such.”
Security and privacy for storage and computation in cloud computing (2014, background): “Under Byzantine [11] failure or even external attacks, the cloud may perform unreliable computation operations while choosing to hide the computations.”
MPSS: Mobile Proactive Secret Sharing (2010, methodology): “The primary creates a message listing the signed responses (in the order the primary processed them) and uses the BFT agreement protocol [Castro and Liskov 2002] to get the group to agree on this message.”
RapidChain: Scaling Blockchain via Full Sharding (2018, background): “Recently, several protocols have been proposed to mitigate the performance and scalability issues of Bitcoin’s blockchain [23, 29, 41, 52, 56, 47, 32, 4, 42] using hybrid architectures that combine the open-membership nature of Bitcoin with traditional Byzantine fault tolerance [57, 19].”
A Survey and Evaluation of the Potentials of Distributed Ledger Technology for Peer-to-Peer Transactive Energy Exchanges in Local Energy Markets (2019, positive): “The BFT protocol [79] is used to detect mismatches between the information shared among all the nodes, thus avoiding the malfunction of the whole system.”
A systematic literature review of blockchain-based applications: Current status, classification and open issues (2019, neutral): “proaches include Byzantine Fault Tolerance (BFT) (Castro and Liskov, 2002) and its variants (Zheng et al.”
BAR fault tolerance for cooperative services (2005, methodology): “We assume a Byzantine fault model for Byzantine nodes [10, 30, 36] and a strong adversary.”
Hyperledger fabric: a distributed operating system for permissioned blockchains (2018, methodology): “Prior to realizing the execute-order-validate architecture of Fabric, the team gained experience with building a per-missioned blockchain platform in the order-execute model, with PBFT [11] for consensus.”
Random Oracles in Constantinople: Practical Asynchronous Byzantine Agreement Using Cryptography (2000, background): “Recently, there has also been revived interest in asynchronous systems without failure detectors that relax the model only slightly in order to avoid FLP [ 18 ], [50].”
A Byzantine Fault-Tolerant Ordering Service for the Hyperledger Fabric Blockchain Platform (2017, methodology): “Under favourable network conditions and the absence of faulty replicas, BFT-SMART executes the message pattern depicted in Figure 3, which is similar to the PBFT protocol [2].”
Survey on blockchain for Internet of Things (2019, background): “Content References Characteristic description Blockchain technology [6, 12, 14, 46, 50, 51, 69, 71, 73, 75,80,102] [71] put forward the concept of bitcoin and made the blockchain step into peoples horizons; [75] introduced the workflow of blockchain; [73, 102] introduced the characteristics of decen”
Towards Blockchain-based Auditable Storage and Sharing of IoT Data (2017, methodology): “Such blockchains typically use more CPU-friendly consensus protocols, such as the Practical Byzantine Fault Tolerance protocol [8], since the set of validator nodes is known.”
Performance Modeling of PBFT Consensus Process for Permissioned Blockchain Network (Hyperledger Fabric) (2017, background): “In a private blockchain network, all the participants are whitelisted and bounded by strict contractual obligations to behave “correctly”, and hence more efﬁcient consensus protocols such as Practical Byzantine Fault Tolerance (PBFT) [5] can be used [6].”
SANE: A Protection Architecture for Enterprise Networks (2006, background): “This can be achieved via standard byzantine agreement protocols [11].”
Fault-scalable Byzantine fault-tolerant services (2005, methodology): “Castro and Liskov, in BFT [9], pioneered the use of lists of HMACs appended to messages as authenticators to implement a replicated state machine.”