Is Solana Proof-of-Stake?

Solana secures its network with stake-weighted validator voting, but it is proof of history (PoH) that supplies the ordering and timing layer that Tower BFT uses to confirm blocks. Solana's consensus mechanism relies on both PoH and Tower BFT working together, with validators voting on PoH sequences according to their stake.

What Solana Actually Uses

At first glance, it seems Solana is simply proof of stake (PoS), as validators stake SOL to vote on the network's state. However, Solana's actual mechanism is more complex. Helius clarified that PoH is not itself a consensus mechanism, but rather a crucial tool that Tower BFT leverages to reach consensus more efficiently. In Solana's architecture, Tower BFT is the consensus layer while PoH provides a cryptographic clock that acts as a network-wide timestamping service to facilitate fast synchronization and high throughput.

The Solana developer portal explains that Tower BFT is Solana's consensus protocol, with validators voting on PoH sequences, weighted by the amount of SOL they have staked. Finality in Solana is achieved when a supermajority, defined as two-thirds or more of the total staked SOL, has voted to confirm a block. If a slot leader does not produce a block within the scheduled slot time, the next validator in the sequence is automatically assigned and voting proceeds onward, allowing the network to skip over any unresponsive or inactive validators without waiting for a full round of synchronized consensus.

How Ordering Works

Critically, PoH is a cryptographic clock used to order events and transactions on the Solana network, rather than a consensus algorithm unto itself. As GridPlus explained in its 2026 technical report, PoH is a verifiable timestamping system that measures elapsed time on the Solana network. It creates a SHA-256 cryptographic hash of the total transactions in each slot, then uses that hash as the input for the next slot's hash. This hash linking function performs two key roles: it acts as a timestamp to confirm a transaction's order within a slot, and it also establishes the sequence of slots themselves.

This hashing ordering allows any validator joining the network to synchronize their local state by referring to the latest provably-validated slot rather than waiting to catch up with every previous slot and consensus round. PoH reduces the synchronization task from verifying every single slot to simply verifying the latest block hash, streamlining the process significantly for validating nodes. Importantly, the PoH cryptographic clock is considered a separate mechanism from consensus, with Tower BFT being the true consensus algorithm on top of it.

How Consensus Finalizes Blocks

Validator voting using stake-weighted voting is an integral part of the Tower BFT consensus process. As the developer portal explains, "Tower BFT decides which blocks get confirmed and when they become finalized and canonical." While any validator can propose a block, it still requires a supermajority of 2/3+ of the total stake to be confirmed into the ledger. This ensures that malicious validators colluding to execute an attack would need enough stake to command more than one third of the total issuance.

Validators are rewarded to confirm and finalize the network, with rewards issued at the end of each epoch of 432,000 slots, roughly two days.

In the event a validator is unresponsive or otherwise fails to perform its assigned work, its slot is skipped and assigned to the next active validator in sequence.