Run Nodes
Full, validator, and archive nodes
Run Selendra nodes for RPC access, block production, or historical data.
Node Types
| Type | Purpose | Storage | RAM | Stake | Rewards |
|---|---|---|---|---|---|
| Full | RPC, queries | 200GB | 8GB | No | No |
| Validator | Block production | 200GB | 16GB | 10K SEL | Yes |
| Archive | Full history | 2TB+ | 32GB | No | No |
Guides
Hardware Requirements - Specs by node type
Full Node - dApp backend
Archive Node - Explorers, indexing
Validator - Block production
Staking - Earn rewards
Monitoring - Performance tracking
Maintenance - Updates, backups
Troubleshooting - Common issues
Network
Current: 4 validators | Target: 20 (2026), 50+ (2027)
Database: Configurable via --base-path. Separate volume recommended.
Backups: Validator keys essential. Full node state reconstructs from network. Archive backups valuable.
Mainnet
- Chain ID: 1961
- RPC:
https://rpc.selendra.org - WebSocket:
wss://rpc.selendra.org - Explorer:
https://explorer.selendra.org - Validators: 4 (2 reserved, 2 non-reserved)
Testnet
- Chain ID: 1953
- RPC:
https://rpc-testnet.selendra.org - WebSocket:
wss://rpc-testnet.selendra.org - Explorer:
https://testnet.explorer.selendra.org
Statistics
- Uptime: 100% for 5.5+ months
- Transactions: 500+ daily average
- Block time: 1 second (Aura)
- Finality: 2-3 seconds (AlephBFT)
- Total blocks: 2.5M+
Community
Validator applications considered as network scales.
Contribute
Found an issue or want to contribute?
Help us improve this documentation by editing this page on GitHub.