The Network page shows THORChain's validator set as one picture: how many nodes are active and on standby, the bond they put up, what bonding pays, where the churn cycle stands, which software versions the nodes run, where they are hosted and which halts or pauses are set. All of it is read live from THORNode and Midgard.
Live data, read
| Version | Active nodes | Standby nodes |
|---|---|---|
| 3.21.0 (network) | 111 | 6 |
| Other versions (31) | 0 | 56 |
| Date | Block | Time since the churn before |
|---|---|---|
| 2026-10-11 23:34 UTC | 28,203,871 | 3d 4h |
| 2026-10-08 18:49 UTC | 28,159,005 | 3d 4h |
| 2026-10-05 13:58 UTC | 28,114,135 | 3d 11h |
| 2026-10-02 02:06 UTC | 28,064,965 | 11d 8h |
| 2026-09-20 17:25 UTC | 27,914,370 | 3d 2h |
Right now 111 nodes are active and 65 are on standby. Active nodes validate, sign for the vaults and earn rewards; the network aims for 120 active seats (DESIREDVALIDATORSET). Standby nodes wait with a bond for a seat at the next churn. All nodes lists every one of them.
A churn rotates the validator set. Every churn interval (now 43,200 blocks, about 3d 1h) THORChain removes the lowest bond, the worst performer and the oldest node, plus nodes that asked to leave or run an old version, and the ready standby nodes with the highest bond take their place (up to 4 new nodes per churn). At churn the accrued rewards are added to each bond. Unbonding and leaving are blocked while vaults migrate. While the HALTCHURNING mimir is set, no rotation happens and rewards keep building. Churning is halted right now.
The network bonding APY from Midgard, annualised from the last reward cycles, now 27.1%. It is before operator fees: each node keeps its fee from the providers' share, and slash points lower a node's share. Rewards depend on network income and RUNE's price, so past rates say nothing certain about future ones.
Bond above the hard cap does not add effective security, so it earns nothing; the cap is 1.03M RUNE now. The cap moves with the network. MINIMUMBONDINRUNE sets the minimum bond to be churned in (300k RUNE), MAXBONDPROVIDERS caps the provider list per node (100).
Upgrades are proposed on chain. Once 2/3 of active nodes (74) approve one, the new version activates at its block height and nodes have to run it from then on. Nodes on an old version can be churned out, and standby nodes on an old version cannot join.