Node Types

The Shardeum network runs on two main types of nodes. Each node type serves a different purpose, and operators can choose the configuration that best matches how they want to support the network.

Note: Detailed setup guides for running Validator, Full, Archive, and RPC nodes are available throughout the Run a Node section of this documentation. Read on to learn about each node type.

Validator Nodes

1. Role: Validators are responsible for proposing blocks, participating in consensus, and securing the network.
2. Requirements: Requires staking SHM tokens and maintaining high uptime and performance.

Full Nodes

1. Role: Full nodes do not participate in consensus. They maintain and verify the blockchain state, functioning as a reliable “source of truth” for applications, wallets, and other network participants.
2. Configuration: Full nodes run with pruning enabled by default, storing only the most recent state needed for operation.
3. Use cases include:
   • Running infrastructure for dApps
   • Supporting RPC endpoints
   • Improving network resilience
   • Non-validating node participation

Depending on their infrastructure needs, developers, dApps, explorers, indexers, and service providers may also operate:

Archive Nodes

Archive nodes are a special configuration of full nodes.

1. Role: Archive nodes store all historical blockchain state from genesis to the present. require significantly more storage than standard full nodes.
2. Use cases include:
   • Indexers
   • Blockchain analytics
   • Data providers
   • Explorers and infra partners
3. Configuration: Disable pruning so the node retains every historical state snapshot.
4. Startup Flag:

--pruning nothing

RPC Nodes

RPC nodes provide network access for applications and infrastructure through JSON-RPC and WebSocket endpoints.

1. Role: RPC nodes serve requests from developers, dApps, wallets, indexers, and infrastructure providers. They do not participate in consensus.
2. Use cases include:
   • dApp backend integrations
   • Wallet connectivity
   • Indexing services
   • Developer environments
   • Public or private RPC infrastructure
3. Interfaces: RPC nodes can expose JSON-RPC and WebSocket endpoints
4. Configuration: RPC access is enabled through the node configuration. Custom pruning is recommended for typical RPC deployments, depending on infrastructure and historical-data requirements.