Validator Guide
1. Identity Registration (N105)
Validators register with Ed25519 keypairs. Identity is derived from public key and genesis hash, creating a cryptographic binding that prevents impersonation.
engine.register_validator_identity(peer_id, validator_id, public_key, voting_power);
2. Voting Process
Validators participate in three phases: Proposal, Prevote, and Precommit. Each vote is cryptographically signed and verified.
Proposal
Leader proposes block
Leader proposes block
Prevote
Validators vote
Validators vote
Precommit
QC is formed
QC is formed
3. QC Formation
A Quorum Certificate requires >2/3 of voting power. With 4 validators and equal 100 VP each, quorum is 300/400.
QC_CHECK: approvals=3 power=300 total=400 quorum=true
4. Slashing Conditions
Validators are penalized for: Double voting, Equivocation, Extended downtime. Slashing evidence is stored on-chain via N110.4c.
5. Hardware Requirements
CPU: 4 cores
RAM: 8 GB
Storage: 100 GB SSD
Network: 100 Mbps