xhavic.com
GitHub (Coming Soon) Whitepaper
Docs / Node Operators

Node Operators

How to run a Xhavic node — hardware requirements, setup, and validator participation.

Running a Xhavic node allows you to independently verify all L2 transactions, serve RPC requests, and participate in the validator set.

Node Types

TypePurposeRequirements
Full NodeVerifies all transactions, serves RPCModerate hardware
Archive NodeFull node + complete historical stateHigh storage
Validator NodeFull node + participates in fraud proof challengesStaking requirement

Hardware Requirements

Full Node

ResourceMinimumRecommended
CPU4 cores8 cores
RAM8 GB16 GB
Storage200 GB SSD500 GB NVMe
Network25 Mbps100 Mbps
OSUbuntu 22.04+ / Debian 12+Ubuntu 24.04

Archive Node

ResourceMinimumRecommended
CPU8 cores16 cores
RAM16 GB32 GB
Storage1 TB NVMe2 TB NVMe
Network50 Mbps100 Mbps

Running a Full Node

1. Install Dependencies

# Install Go 1.21+
sudo apt update && sudo apt install -y golang-go

# Install xhavic-node
git clone https://github.com/xhavic/xhavic-node.git
cd xhavic-node
make build

2. Initialize

./xhavic-node init --network mainnet --datadir /data/xhavic

3. Configure

Edit the configuration file at /data/xhavic/config.toml:

[network]
chain_id = 7849
l1_rpc = "https://your-ethereum-rpc-url"

[p2p]
listen_addr = "0.0.0.0:30303"
max_peers = 50

[rpc]
http_addr = "0.0.0.0"
http_port = 8545
ws_addr = "0.0.0.0"
ws_port = 8546

4. Start

./xhavic-node start --datadir /data/xhavic

The node will sync from the latest snapshot and begin verifying new blocks.

Sync Modes

ModeDescriptionSync Time
Snap syncDownloads latest snapshot, verifies from there~30 minutes
Full syncReplays all transactions from genesis~6-12 hours

Snap sync is recommended for most operators. Full sync is only needed for archive nodes or operators who want to independently verify the complete chain history.

Becoming a Validator

Validators participate in the fraud proof system by monitoring state roots and submitting challenges when invalid state is detected.

Requirements

  1. Run a full node synced to the latest block
  2. Stake a minimum of 10,000 XHAV to the validator contract
  3. Maintain 99.5% uptime

Validator Rewards

SourceDescription
Staking rewardsProportional to stake weight
Challenge rewardsEarned for submitting valid fraud proofs
Transaction tipsShare of priority fees from users

Validator Set

ParameterValue
Maximum validators100
Selection methodTop 100 by stake
Unbonding period14 days
Slashing conditionsDowntime, invalid fraud proof submission

Monitoring

Recommended monitoring setup:

  • Prometheus + Grafana — Node metrics (block height, peer count, sync status)
  • Alerting — Block production delays, peer disconnections, disk usage

The node exposes Prometheus metrics at http://localhost:9090/metrics by default.