Validator System Architecture

Spicenet uses a two-tier validator system to balance performance with decentralization. Let's examine each type in detail:

Non-Voting Validators

Think of non-voting validators as the network's observers and verifiers. They:

• Maintain a full copy of the state

• Verify all transactions and state updates

• Provide RPC endpoints for users

• Cannot participate in consensus

Required Setup:

bashCopy# Minimum Hardware Configuration
CPU: 8 cores
RAM: 16GB
Storage: 500GB SSD
Network: 500Mbps

# Basic Validator Node Setup
$ spicenet-node init --non-voting
$ spicenet-node start --rpc-endpoint "0.0.0.0:8545

Voting Validators

Voting validators are the network's active participants. They:

• Participate in consensus

• Generate and verify fraud proofs

• Challenge invalid state transitions

• Maintain network security

Required Setup:

bashCopy# Minimum Hardware Configuration
CPU: 16 cores
RAM: 32GB
Storage: 1TB NVMe SSD
Network: 500Mbps

# Voting Validator Setup
$ spicenet-node init --voting
$ spicenet-node generate-keys
$ spicenet-node start --consensus --fraud-proof-generation

You can learn more about Spicenet validator here