Run a Validator Node

Last updated March 20, 2026 · Estimated read time: 12 minutes

1.1 Validator Overview

Validators produce blocks, execute smart contracts, and secure the Asentum network. Unlike most blockchains, Asentum validators can run on consumer hardware — a Raspberry Pi 4 is all you need. The network elects 21 active validators per epoch through stake-weighted voting.

1.2 Hardware Requirements

Minimum: Raspberry Pi 4 (4GB RAM), 64GB SD card or USB SSD, stable internet connection. Recommended: Raspberry Pi 4 (8GB RAM) with a 128GB USB SSD for better performance and longevity. Power consumption: ~5W (~$5/year electricity).

Any x86 or ARM device with equivalent specs also works — old laptops, mini PCs, cloud instances. But the whole point is you don't need cloud infrastructure.

1.3 Setup Guide

Four commands:

curl -fsSL https://asentum.io/install | bash
asentum init --validator
asentum stake 10000
asentum start

The install script handles Node.js, dependencies, and configuration. init --validator generates your validator keypair and configures the node. stake locks your ASX tokens. start begins validation.

1.4 Staking and Activation

Minimum stake: 10,000 ASX. Once staked, you become a validator candidate. If token holders vote for you (or delegate to you) and you reach the top 21, you'll be activated in the next epoch. Standby validators (positions 22-121) are ready to fill any open slots.

1.5 Validator Dashboard

Access your dashboard at http://localhost:3000 (or remotely if configured). It shows blocks validated, rewards earned, peer count, network health, uptime percentage, and delegation stats. Mobile-friendly — check your Pi from your phone.

1.6 Rewards and Economics

Block rewards: ~0.5 ASX per block validated. Transaction fees: Priority tips from transactions in your blocks. Delegation commission: Set your rate (5-20%) and earn from delegators staking through your node. Total revenue depends on block production frequency and network activity.

1.7 Slashing Conditions

Double-signing: Signing two different blocks at the same height results in immediate slashing (loss of staked tokens). Downtime: Extended offline periods (missing too many blocks in an epoch) result in partial slashing and temporary deactivation. Keep your node online and honest — the incentives are designed to make this the most profitable strategy.