Before you start
You need four things.- A validator in a bonded state. If you do not have one yet, start with Run a validator.
- A separate server. The SuperNode must never share a host with the validator. It keeps its own account, keys, and stake delegation, and talks to the chain over gRPC.
- Access to the validator operator key. It signs the registration transaction.
- SuperNode hardware. Plan for at least 8 CPU cores, 16 GB RAM, a 1 TB NVMe SSD, and a 1 Gbps connection. Ports 4444 (gRPC) and 4445 (P2P) must be reachable.
The path
Four stages take you from a bonded validator to a registered SuperNode.- Provision a second server. Ubuntu 22.04 LTS or later on x86_64 hardware that meets the specs above.
- Install with
sn-manager. The manager downloads thesupernodebinary, applies updates automatically, and supervises the service. Configuration lives in~/.supernode/config.yml. - Fund the SuperNode account and delegate. LEP-3, a Lumera Enhancement Proposal, defines a dual stake rule. Your validator self-delegation plus the delegation from the SuperNode account must together meet the minimum, 10,000 LUME on testnet and 25,000 LUME on mainnet. Governance can change these values.
- Register from the validator host. The validator operator key signs the transaction that binds the SuperNode endpoint and account to your validator.
Verify the stake minimum before you register. The
minimum_stake_for_sn parameter is set by governance and can change.Earning for retention
SuperNodes that keep Cascade data available receive ongoing payouts from the Everlight SN Pool, proportional to the data they retain. Everlight for SuperNode operators explains eligibility and payout mechanics.Next steps
SuperNode overview
Architecture, staking requirements, and hardware in full.
Node setup
Install and configure the SuperNode with
sn-manager.Everlight payouts
How retention compensation works for operators.