What Is Tower BFT in Solana?
Tower BFT is Solana’s consensus mechanism, a variant of Practical Byzantine Fault Tolerance (PBFT) optimized using Proof of History as a clock. It enables validators to reach consensus on the state of the ledger without the communication overhead of traditional BFT protocols.
How Tower BFT works
Validators vote on blocks they observe. Each vote includes a lockout period — a commitment to not vote on a conflicting fork for a number of slots. As a validator accumulates consecutive votes on the same fork, the lockout period doubles exponentially. After 32 consecutive votes, the oldest vote reaches maximum lockout and the block is considered finalized.
Vote lockout
| Consecutive votes | Lockout (slots) |
|---|---|
| 1 | 2 |
| 2 | 4 |
| 3 | 8 |
| … | … |
| 32 | 2^32 (~4 billion) |
This exponential lockout means that once a validator has voted consistently on a fork, switching to a different fork becomes prohibitively expensive — it would forfeit all accumulated lockout and staking rewards.
Relationship to commitment levels
Tower BFT’s voting mechanism directly maps to Solana’s commitment levels:
- Processed — the leader has produced the block
- Confirmed — a supermajority (66.7%+) of stake has voted on the block
- Finalized — the block has reached maximum lockout (31+ votes deep)
FAQ
How is Tower BFT different from standard PBFT? Traditional PBFT requires O(n²) message exchange between validators. Tower BFT uses Proof of History timestamps to eliminate the need for explicit communication rounds, reducing consensus overhead.
Can Tower BFT handle Byzantine faults? Yes. Tower BFT tolerates up to one-third of stake being controlled by malicious validators, the standard BFT threshold.
Updated: