Revisiting Speculative Leaderless Protocols for Low-Latency BFT Replication

📅 2026-01-06
🏛️ arXiv.org
📈 Citations: 0
Influential: 0
📄 PDF
🤖 AI Summary
This work proposes Aspen, a leaderless Byzantine fault-tolerant (BFT) protocol that addresses the high overhead and latency incurred by existing leaderless BFT protocols under high-concurrency request contention, where inconsistent reception ordering across replicas frequently triggers costly recovery procedures. Aspen is the first leaderless BFT protocol to integrate loose clock synchronization, network delay estimation, and a best-effort ordering layer, achieving near-optimal commit latency of 2Δ+ε in a system with 3f+2p+1 replicas, tolerating f Byzantine and p delay-faulty nodes. When optimistic conditions are violated, Aspen safely falls back to a PBFT-style mechanism to guarantee both liveness and safety. Experimental results demonstrate that Aspen achieves sub-75ms latency and 19,000 transactions per second (TPS) throughput in wide-area networks, outperforming state-of-the-art protocols by 1.2–3.3×.

Technology Category

Application Category

📝 Abstract
As Byzantine Fault Tolerant (BFT) protocols begin to be used in permissioned blockchains for user-facing applications such as payments, it is crucial that they provide low latency. In pursuit of low latency, some recently proposed BFT consensus protocols employ a leaderless optimistic fast path, in which clients broadcast their requests directly to replicas without first serializing requests at a leader, resulting in an end-to-end commit latency of 2 message delays ($2\Delta$) during fault-free, synchronous periods. However, such a fast path only works if there is no contention: concurrent contending requests can cause replicas to diverge if they receive conflicting requests in different orders, triggering costly recovery procedures. In this work, we present Aspen, a leaderless BFT protocol that achieves a near-optimal latency of $2\Delta + \varepsilon$, where $\varepsilon$ indicates a short waiting delay. Aspen removes the no-contention condition by utilizing a best-effort sequencing layer based on loosely synchronized clocks and network delay estimates. Aspen requires $n = 3f + 2p + 1$ replicas to cope with up to $f$ Byzantine nodes. The $2p$ extra nodes allow Aspen's fast path to proceed even if up to $p$ replicas diverge due to unpredictable network delays. When its optimistic conditions do not hold, Aspen falls back to PBFT-style protocol, guaranteeing safety and liveness under partial synchrony. In experiments with wide-area distributed replicas, Aspen commits requests in less than 75 ms, a 1.2 to 3.3$\times$ improvement compared to previous protocols, while supporting 19,000 requests per second.
Problem

Research questions and friction points this paper is trying to address.

Byzantine Fault Tolerance
Low-Latency Consensus
Leaderless Protocols
Contention Handling
BFT Replication
Innovation

Methods, ideas, or system contributions that make the work stand out.

leaderless BFT
low-latency consensus
best-effort sequencing
contention handling
partial synchrony
🔎 Similar Papers
No similar papers found.