Proof-of-Stake on TON
TON's consensus model. Validators lock around 300,000 TON, are elected per cycle (~18 hours), and earn rewards for signing blocks. Slashing punishes double-signing.
Aliases: ton pos, ton consensus, ton bft
Proof-of-Stake is the consensus mechanism TON uses to decide which nodes write blocks and how the network agrees on the resulting state. Unlike proof-of-work (Bitcoin) where compute decides, TON validators put up Toncoin as collateral and are weighted by stake.
The basic loop
- Election. Every ~18 hours (one validator cycle) the masterchain runs an election. Candidates send a deposit to the elector smart contract along with their bid.
- Selection. The protocol picks a fixed-size validator set, weighted by stake. The current parameters allow up to 400 active validators in a cycle (the exact cap is governance-tunable).
- Sharding committees. From the validator set, smaller committees are randomly assigned to each shardchain for the round. Each committee runs a Byzantine Fault Tolerant (BFT) consensus to produce blocks for its shard.
- Reward and exit. At the end of the cycle, validators that performed receive emissions; misbehavers get slashed; the deposit unlocks for those who did not enter the next cycle.
What “BFT” looks like in practice
The committee runs a multi-round voting protocol (a TON-specific variant of pBFT) to produce each block:
- A leader proposes a block.
- The committee votes; if a 2/3 supermajority signs, the block is finalised.
- Finalisation is fast — typically a few seconds for masterchain blocks, comparable for shards.
This gives near-instant finality: once a block is signed by 2/3, it cannot be reverted without slashing everyone who signed.
Stake threshold
A solo validator in 2026 needs around 300,000 TON as collateral. The exact minimum is a config parameter and shifts over time. At the typical TON price, that is hundreds of thousands of dollars — accessible to companies, foundations, and large pools, but not to retail users.
Nominators and pools
To bring smaller stakers into the system, TON has nominator pools: a user delegates TON to a pool, the pool runs the validator, rewards are distributed pro rata. By 2026 most TON staking volume flows through this layer, primarily via liquid-staking protocols (Tonstakers, Hipo, bemo) that wrap the pool stake in a tradable token.
Slashing
Validators that misbehave lose part of their stake. The two punishable offences:
- Double-signing — voting for two conflicting blocks at the same height. Provable on-chain; results in a hard slash.
- Severe downtime — missing the round entirely. Can result in lost emissions and, in extreme cases, partial slash.
In a nominator pool, the slash hits the operator’s own stake first, only touching nominator funds in the worst-case scenario.
Yield in 2026
Net staking yield for delegators is roughly 3–5% APR in TON, after pool/protocol fees. The base inflation rate has settled near 0.6% of supply per year, which is low among PoS chains.
Why TON’s PoS is unusual
- Dynamic sharding compatibility. The committee selection has to handle shard splits and merges within a cycle.
- Election cycle is short (~18 hours) compared with other PoS networks (Ethereum’s ~6.4 minutes per epoch but year-long withdrawal queues; Cosmos’s 21-day unbonding). TON’s cycle limits exposure but increases governance friction.
- No re-staking primitives native at protocol level; that layer is left to liquid-staking protocols on the application layer.
Risks
- Concentration. A handful of operators hold most of the stake. Healthy decentralisation requires more independent validators.
- Liquid-staking dominance. If most stake routes through three protocols, those three protocols’ choices about which validators to back become the de-facto governance of the network.
- Slashing tail risk. Rare but real; choose pools whose operators have track records and audited contracts.