Staking
Stake to secure the network
Stake directly, or delegate to an operator. Staking is how the network stays secure and neutral — and how the validator set is held accountable.
Mechanics
How staking works.
Stake is bonded to secure the network. In return, an operator earns rewards from the security budget — and accepts that the same stake can be slashed. Unbonding takes time by design.
Rewards are security economics — they fund the cost of keeping the network neutral and live, not a yield. The confirmed parameters are published in the docs.
Delegation
Delegation.
If you do not run hardware, you can delegate your stake to an operator. You keep ownership; the operator does the work and takes a commission. Choose on performance, not promises.
Choose an operator
Compare operators on uptime, commission, and stake in the live table.
Commission
Each operator sets a commission, taken from rewards before they reach you.
Performance
Downtime and slashing affect delegators too. Performance is verifiable, live.
Risks
Risks.
Staking carries real risk. State it plainly before you bond anything.
Slashing, jailing, and lock-up
Bonded stake can be slashed if your operator equivocates or commits a provable fault, and an operator can be jailed for downtime — both affect delegators. Stake is also locked during the unbonding period and is not liquid until it completes. Confirmed conditions and timing are published in the docs.Operators
The operator table.
The live operator set lives in the explorer — uptime, commission, stake, and status, drawn from the network itself, never from this page.
Comparing operators is the whole point: stake to the ones that stay online and set their commission fairly. The table is live in the explorer, so the numbers are the network's, not marketing's.
Stake to secure the network.
Compare operators on live performance, understand the risk, then delegate.