Skip to main content

Running an Inception Validator

Validators are the backbone of the Inception network, securing the blockchain through proof-of-stake consensus. This guide covers what you need to know before running a validator.

What is a Validator?​

Validators participate in the Inception proof-of-stake consensus by:

  • Proposing blocks: Creating new blocks when selected
  • Attesting: Voting on the validity of proposed blocks
  • Securing the network: Staking 32 INCP as collateral
  • Earning rewards: Receiving INCP for honest participation

Requirements​

Hardware Requirements​

To run a reliable validator, you need:

ComponentMinimumRecommended
CPU4 cores8+ cores
RAM16 GB32 GB
Storage500 GB SSD1 TB NVMe SSD
Bandwidth10 Mbps up/down25+ Mbps up/down
Uptime95%+99%+ (critical for rewards)
Storage Growth

The blockchain grows over time. Plan for storage expansion or implement pruning strategies.

Network Requirements​

Required Open Ports:

  • 30303 TCP/UDP: Execution layer P2P
  • 13000 TCP: Consensus layer P2P
  • 12000 UDP: Consensus layer discovery

Keep Private (localhost only):

  • 8551: Engine API (execution ↔ consensus)
  • 8545: HTTP RPC (if enabled)
  • 8546: WebSocket RPC (if enabled)
Critical Security

Never expose the Engine API (port 8551), HTTP RPC (8545), or WS RPC (8546) to the public internet. Bind them to 127.0.0.1 and use a shared jwt.hex file for EL↔CL authentication.

Status Updates

For live endpoints, caps, and incident updates, always check the Inception Status page: https://inceptionera.com/status

Financial Requirements​

32 INCP Validator Requirement

Validators must deposit exactly 32 INCP to activate. This is Inception's fixed stake requirement per validator.

  • 32 INCP: Required deposit to activate validator
  • Operating Costs: Server hosting, electricity, internet
  • Buffer Funds: Extra INCP for potential penalties

Technical Skills​

You should be comfortable with:

  • Linux command line basics
  • SSH and remote server management
  • Reading logs and troubleshooting
  • Basic security practices (firewalls, key management)
  • Understanding blockchain concepts

Validator Responsibilities​

Reliability​

  • High uptime: Aim for 99%+ to maximize rewards
  • Fast sync: Keep your clients synchronized with the network
  • Monitoring: Watch for errors and performance issues
  • Updates: Keep client software up to date

Security​

  • Secure keys: Protect your validator keys at all costs
  • Firewall rules: Only expose necessary ports
  • Access control: Limit who can access your validator server
  • Backups: Regularly backup important configuration files (not keys)
Key Security

Your validator keys control your 32 INCP deposit. If compromised, an attacker could get your validator slashed. Never share keys or store them unencrypted.

Penalties and Slashing​

Validators can lose INCP through:

Inactivity Penalties (Mild)​

  • Missing attestations while offline
  • Slow to sync or respond
  • Generally small penalties, can be recovered

Slashing (Severe)​

Slashing occurs for provably malicious behavior:

  • Double signing: Signing two different blocks for the same slot
  • Surround voting: Contradictory attestation votes
  • Can lose up to 100% of your 32 INCP stake
Avoid Slashing
  • Never run the same validator keys on two machines simultaneously
  • Never import keys from one validator to another without proper migration
  • Keep accurate time synchronization (use NTP)
  • Follow proper shutdown procedures

Rewards​

Validators earn INCP rewards for:

  • Block proposals: Extra rewards when selected to propose
  • Attestations: Rewards for timely, accurate votes
  • Sync committee: Additional rewards if selected for sync committee

Factors affecting rewards:

  • Network participation rate
  • Your validator uptime
  • Accurate attestations
  • Network activity (more transactions = more rewards)
Reward Variability

Rewards fluctuate based on network conditions and your performance. Higher network participation means lower individual rewards, but a more secure network.

Getting Started​

Ready to run a validator? Follow these guides in order:

  1. Execution Layer Setup: Install and configure Geth
  2. Consensus Layer Setup: Install and configure Prysm
  3. Keys and Deposit: Generate keys and make your 32 INCP deposit

Validator Lifecycle​

Alternative: Staking Services​

Don't want to run your own validator? Consider:

  • Staking pools: Contribute less than 32 INCP
  • Staking services: Pay a service to run the validator for you
  • Liquid staking: Get a liquid token representing your staked INCP
Third-Party Risk

Using staking services means trusting a third party with your funds. Research thoroughly and understand the risks.

Important Considerations​

Before running a validator, understand:

  • Long-term commitment: Validators should plan to run for months or years
  • Capital lockup: Your 32 INCP is locked while validating
  • Exit queue: Withdrawing may take time if many validators exit at once
  • Operating costs: Ensure you can cover ongoing server and bandwidth costs
  • Technical support: You're responsible for maintaining your validator

Need Help?​

Next Steps​

Continue with the validator setup: