Node Types

TL;DR

One binary, four operating modes. A full node is the default - it verifies every block but has no stake. A consensus validator bonds stake and votes on blocks. A service node serves RPC requests for micro-fees with no stake and no slashing risk. A light client verifies block headers without storing state. The role is a startup flag, not a different binary.

Full node

The default. Downloads and verifies every block from genesis, maintains the full Sparse Merkle Tree state, and serves JSON-RPC locally. No stake, no rewards, no risk - just verification.

• Purpose - run your own RPC, verify a dapp without trusting a hosted node.
• Rewards - none.
• Risk - none.

Consensus validator

A full node that has bonded stake and is eligible for Aura proposer slots and GRANDPA voting. Produces blocks in its assigned slots and signs finality votes. Earns block rewards and priority fees when in the active set. Subject to slashing for double-signing or prolonged downtime.

• Purpose - secure the chain, earn rewards.
• Rewards - block reward share + priority tips.
• Risk - slashing for protocol-breaking behaviour. Background: Slashing Risks.

Service node

A full node that publishes itself as a public RPC endpoint. The design is for service nodes to earn micro-fees from a dedicated pool - a fraction of base fees diverted before burn (see the fee market). No stake, no consensus work, no slashing. Reward routing is planned; on the current testnet, full nodes run unrewarded.

• Purpose - provide RPC to the ecosystem, earn without slashing risk.
• Rewards - planned: per-request micro-fees from the service-node pool. Not yet active.
• Risk - none at the protocol level.

Service node is the default "participation" mode for desktop users. Small steady earnings with zero risk.

Light client

Verifies block headers and GRANDPA finality proofs without storing full state. Used inside the Chrome extension to trustlessly verify balances and transaction inclusion against a remote full node.

Picking the right role

• Just want to use the chain? Don't run a node. Use the Chrome extension or point tools at the public RPC.
• Want to participate without risk? Run a service node via the desktop app.
• Want to secure the chain and earn full rewards? Run a validator - bond stake, keep uptime, accept slashing risk. Start at Run a Validator.
• Have hardware you won't dedicate to validation? Run a full node for your own use.