Core Concepts
The authors present three chain-based BFT consensus protocols, called Moonshot protocols, that achieve a minimum view change block period of δ and a minimum commit latency of 3δ in the partially synchronous network model. The protocols leverage optimistic proposals and vote multicasting to enable these improvements over prior work.
Abstract
The authors present three chain-based BFT consensus protocols, called Moonshot protocols, that optimize performance in the partially synchronous network model:
-
Simple Moonshot:
- Achieves a minimum view change block period of δ and a minimum commit latency of 3δ.
- Provides responsiveness under consecutive honest leaders.
- Requires two consecutive honest leaders after GST to commit a new block.
- Ensures reorg resilience through vote multicasting.
-
Pipelined Moonshot:
- Also achieves a minimum view change block period of δ and a minimum commit latency of 3δ.
- Provides full optimistic responsiveness and has a view length of 3Δ.
- Separates the fallback proposal case from the normal proposal to enable optimistic responsiveness.
- Uses a Bracha-style amplification step for timeout messages to avoid cubic communication complexity.
-
Non-pipelined Moonshot:
- A non-pipelined variant of Pipelined Moonshot.
- Retains standard optimistic responsiveness and requires only a single honest leader to commit a new block after GST.
- Improves commit latency when blocks take sufficiently longer to propagate or process than votes.
The protocols achieve these improvements over prior work by allowing leaders to propose optimistically and having nodes multicast their votes. This enables voting for consecutive honest proposals to proceed in parallel, reducing the minimum view change block period and commit latency.
Stats
The minimum commit latency of the protocols is 3δ.
The minimum view change block period of the protocols is δ.
Quotes
"To close this gap, we present the first chain-based BFT SMR protocols with δ delay between the proposals of consecutive honest leaders and commit latencies of 3δ."
"Our protocols need not be implemented as LCO, however, it is in this setting that they have the greatest advantage."