Mini Nodes, full nodes & validators
Three different ways to participate, with different responsibilities.
Choose the right role
| Role | Work performed | Consensus rewards |
|---|---|---|
| Browser Mini Node | Limited checks of block links and transaction data | No |
| Full node | Sync and verify shared history; provide local reads | Not merely for running |
| Active validator | Authorized consensus participation with the required keys and bond | Subject to participation and fee rules |
What a Mini Node can do
The browser feature checks a limited workload, including links, transaction hashes, chain identity, and signature recovery. Large blocks can be sampled. It does not re-execute the EVM or verify full validator commit certificates, and it does not add consensus TPS or earn rewards.
Browsers and phones can suspend background work when hidden, closed, or asleep. A Mini Node should not be described as an always-on full validator.
Move toward a full validator
A desktop full node can operate as an observer before any staking action. Becoming a validator is a separate enrollment and bonding process. It requires correct network identity, protected keys, proofs, availability, and eventual active-set eligibility.
Read validator participation before expecting rewards. Open candidate registration does not guarantee an active slot, and a node appearing on a map does not prove it is currently voting.
Reviewed 10 November 2026. This is an editorial reference, not a live status monitor. How we review information →