Skip to main content

​
DracoBFT: Architecture Diagrams and Protocol Flows

​
1. System Architecture Overview

System Architecture Overview

​
2. Two-Round Commit Protocol Flow

​
Classical HotStuff (3-Round)

View v-2:  Leader proposes B_{v-2}
           ┌─────┐
           │ B_k │
           └──┬──┘
              │ votes
              ▼
           ┌─────┐
View v-1:  │QC_k │  →  Leader proposes B_{k+1} with QC_k
           └──┬──┘      ┌──────────┐
              │         │ B_{k+1}  │
              │         │ (QC_k)   │
              │         └────┬─────┘
              │ votes        │
              ▼              ▼
           ┌──────┐      ┌───────┐
View v:    │QC_k+1│  →   │B_{k+2}│  → B_k COMMITTED ✅
           └──────┘      │(QC_k+1)│
                         └────────┘

Commit Time: 3Δ (3 network delays)
Two-Round Commit Protocol Flow Key Difference: Vote rule requires B.view == B.qc.view + 1 (consecutive views)

​
3. Pipelined Operation

Pipelined Operation

​
Summary

DracoBFT Architecture Highlights:
  1. 2-Round Commit: Fast finality matching modern BFT protocols
  2. Pipelined Operation: High throughput after initial latency
  3. Side Consensus Loops: Novel architecture for auxiliary workflows
  4. Change-Log Hash: Optimized state commitment for exchanges
  5. Stake-Weighted Leaders: Economic security model