Node Requirements

Comprehensive specifications for running an Inception validator node

Complete Requirements

Category Specification Details
HARDWARE
CPU 4-8 vCPU Minimum 4 cores for stable validation; 8 cores recommended for peak performance
RAM 16-32 GB 16 GB minimum; 32 GB recommended for handling high block volumes
Storage 1-2 TB NVMe SSD NVMe required for state database performance; 2 TB recommended for future growth
Network 100 Mbps minimum Stable, dedicated connection required; 1 Gbps preferred for optimal performance
SOFTWARE
Operating System Linux (Ubuntu 22.04+) Linux distributions with kernel 5.15+ support required; Ubuntu 22.04 LTS or Debian 11+ recommended
Execution Client Geth Client Latest stable version of Go-Ethereum; handles transaction execution and state management
Consensus Client Prysm Client Latest stable version of Prysm; manages consensus and validator duties
NETWORK
IP Configuration Static IP Address Public-facing static IP required for peer discovery and network participation
Port Forwarding Open Ports 30333, 12000, 13000 Port 30333 (execution), 12000-13000 (consensus) must be open and forwarded correctly
Firewall Appropriate Rules Configure firewall to allow inbound connections on validator ports while maintaining security
FINANCIAL
Minimum Stake 32 INCP Required to activate validator; stake determines tier and earning potential
Slashing Risk Variable Up to 32 INCP at risk if validator misbehaves; follow security best practices

Hardware Details

CPU Requirements

A minimum of 4 virtual CPUs is required for baseline stability. Modern processors (Intel Xeon, AMD EPYC, or equivalent) are preferred. 8 vCPUs are recommended for handling peak load during high transaction volume periods and for better multithreading performance in consensus operations.

RAM Allocation

16 GB is the operational minimum, allowing the consensus and execution clients to maintain the validator state. 32 GB is recommended to accommodate future growth and provide buffer for temporary memory spikes during high activity periods.

Storage (NVMe SSD)

NVMe SSD is mandatory for state database performance. Standard SSDs or HDDs will cause validator lag and missed proposals. Initial requirement is 1 TB; 2 TB recommended for sustained operation and growth. Ensure redundancy with RAID-1 or equivalent backup for data protection.

Network Connectivity

A minimum of 100 Mbps stable, dedicated internet connection is required. Shared or unstable connections will result in missed attestations. 1 Gbps is strongly preferred for professional-grade operations. Ensure low latency (under 100ms to peer nodes) and consistent uptime (99.5% or better).

Software Configuration

Operating System

Linux is the recommended and supported operating system. Ubuntu 22.04 LTS or Debian 11+ are standard choices. Ensure your kernel version is 5.15 or later. Regular security updates and patches must be applied consistently.

Execution Client (Geth)

Geth is the Go implementation of the Ethereum protocol adapted for Inception. Download the latest stable release from the official repository. Geth handles transaction execution, state management, and RPC interfaces for the consensus layer.

Consensus Client (Prysm)

Prysm is a Go implementation of the consensus protocol. It manages validator duties including block proposals and attestations. Always run the latest stable version and monitor releases for security patches and performance improvements.

Network Configuration

Static IP Address

Your validator must be reachable at a consistent IP address. If using cloud providers, allocate an Elastic IP or equivalent static address. Dynamic IPs will cause peer discovery failures and network partition.

Port Configuration

  • Port 30333: Execution layer P2P protocol (TCP/UDP)
  • Ports 12000-13000: Consensus layer P2P (TCP/UDP)
  • Forward these ports from your router or cloud security groups to your node's internal IP
  • Verify ports are open using port scanning tools (e.g., nmap)

Firewall & Security

Configure ufw or iptables to allow inbound connections on validator ports while blocking unnecessary traffic. Use fail2ban or similar tools to prevent brute-force attacks on SSH. Consider restricting direct RPC access and using reverse proxies for added security.

Best Practices

Hardware Security Module (HSM)

Strongly recommended for securing validator signing keys. HSMs like YubiHSM or Ledger Stax protect keys from unauthorized access and slash prevention.

Doppelgänger Protection

Enable doppelgänger detection in your client configuration to prevent running duplicate validators accidentally, which would trigger slashing.

Monitoring & Alerting

Implement Prometheus, Grafana, or similar tools to monitor node health, peer count, attestation performance, and uptime metrics continuously.

Backup & Recovery

Maintain secure backups of your validator keystore and database. Test recovery procedures regularly. Never lose your seed phrase or private keys.

Regular Updates

Keep clients, OS, and dependencies updated. Monitor release notes and apply security patches promptly to avoid vulnerabilities.

Redundancy Planning

Consider backup nodes or failover mechanisms for critical operations. Multiple nodes on the same infrastructure introduces centralization risks.

Financial Requirements

Minimum Stake: 32 INCP

32 INCP tokens is the minimum required to activate a validator node. This stake is held in your validator account and can be withdrawn after the unbonding period (typically 3-7 days after initiating withdrawal).

Slashing Risk

Your entire 32 INCP stake is at risk if you engage in prohibited behavior (equivocation, attestation violations). Major slashing can result in loss of up to 32 INCP. Maintaining best practices and proper configuration significantly reduces this risk.

Summary Checklist