Alea-BFT: Practical Asynchronous Byzantine Fault Tolerance

July 14, 2024 Β· Declared Dead Β· πŸ› In21st USENIX Symposium on Networked Systems Design and Implementation (NSDI 24) 2024 (pp. 313-328)

πŸ‘» CAUSE OF DEATH: Ghosted
No code link whatsoever

"No code URL or promise found in abstract"

Evidence collected by the PWNC Scanner

Authors Diogo S. Antunes, Afonso N. Oliveira, AndrΓ© Breda, Matheus Guilherme Franco, Henrique Moniz, Rodrigo Rodrigues arXiv ID 2407.14538 Category cs.DC: Distributed Computing Citations 0 Venue In21st USENIX Symposium on Networked Systems Design and Implementation (NSDI 24) 2024 (pp. 313-328) Last Checked 3 months ago
Abstract
Traditional Byzantine Fault Tolerance (BFT) state machine replication protocols assume a partial synchrony model, leading to a design where a leader replica drives the protocol and is replaced after a timeout. Recently, we witnessed a surge of asynchronous BFT protocols, which use randomization to remove the need for bounds on message delivery times, making them more resilient to adverse network conditions. However, existing research proposals still fall short of gaining practical adoption, plausibly because they are not able to combine good performance with a simple design that can be readily understood and adopted. In this paper, we present Alea-BFT, a simple and highly efficient asynchronous BFT protocol, which is gaining practical adoption, namely in Ethereum distributed validators. Alea-BFT brings the key design insight from classical protocols of concentrating part of the work on a single designated replica and incorporates this principle in a simple two-stage pipelined design, with an efficient broadcast led by the designated replica, followed by an inexpensive binary agreement. The evaluation of our research prototype implementation and two real-world integrations in cryptocurrency ecosystems shows excellent performance, improving on the fastest protocol (Dumbo-NG) in terms of latency and displaying good performance under faults.
Community shame:
Not yet rated
Community Contributions

Found the code? Know the venue? Think something is wrong? Let us know!

πŸ“œ Similar Papers

In the same crypt β€” Distributed Computing

Died the same way β€” πŸ‘» Ghosted