Run a WCAHT Validator
Help secure the network by producing blocks and voting on finality.
The bundle is a signed, pre-compiled binary with the canonical genesis, a config template and a launcher — no build tools or source required. Verify its SHA-256 before running:9d2a4392bd8743546f6d434503111e99cb6b39710a951ad8d6c108c1e13321da
RegisterValidator transaction is automatically activated into the voting set at the next
epoch boundary — deterministic atomic-delta staking, bound into the state root, with no operator approval and
no wall-clock race. The validators listed here are simply the current active set, not a fixed group. Validator
rewards and fee splits are finalized in the Incentivized Testnet phase. Introduce your validator
below to help grow decentralization and liveness.
What a validator does
WCAHT uses stake-weighted BFT consensus (Skyfall). Validators stake WCAHT, take turns producing blocks on a deterministic round-robin schedule (12 slots each), and vote to finalize blocks at a ≥⅔ stake supermajority. More validators = stronger liveness (the network keeps finalizing even if some nodes drop) and stronger decentralization.
Requirements
| Item | Recommended |
|---|---|
| CPU | 8+ modern cores (parallel execution scales with cores) |
| RAM | 16 GB+ (32 GB for sustained load) |
| Disk | NVMe SSD, 200 GB+ free (chain + snapshots; stays read-only below a 20 GB floor) |
| Network | Stable low-latency link; a public IP or reliable NAT traversal for QUIC |
| Min registration stake | 100,000,000,000 kak (100 WCAHT) |
| OS | Linux (x86-64, glibc 2.34+), Windows, or macOS |
Ports to open
| Port | Purpose |
|---|---|
8901 TCP | HTTP / JSON-RPC (public API, explorer, EVM at /eth) |
9001 UDP | QUIC consensus transport (block & vote propagation) |
8001 UDP | Gossip (peer discovery, transaction relay) |
Validator Onboarding Terminal
Generate the commands for a new Ubuntu validator and work through them one stage at a time. This guide runs entirely in your browser: it does not connect to your server, request an SSH password, or upload validator keys.
Enter your server details, then select Generate commands.
Public operator security rules
Safe operating model
- Download builds only from the approved release channel and verify the published SHA-256 checksum/signature.
- Generate a unique identity on the validator server; keep an encrypted offline backup.
- Use SSH keys, disable password/root login, patch the OS, and restrict SSH by source IP.
- Expose only
8901/tcp,8001/udp, and9001/udp; rate-limit public RPC. - Register only after identity, sync, peer count, and public reachability all pass.
Never do this
- Never paste a private key, seed, SSH password, API token, or full environment file into this page, chat, support, or screenshots.
- Never reuse another validator's identity or accept keys from an unknown operator.
- Never pipe an unknown download directly into
bashor expose a browser-based remote shell. - Never register an offline or unsynchronized node.
- Never retire an active voter until its replacement has active consensus weight.
Dashboard staking walkthrough
These annotated example views contain no live addresses or secrets. The wallet's derived native address must match the node identity exactly.
1. Import the validator key file
Choose the 64-byte backup. Confirm the derived address equals the node identity before Import.
2. Confirm node detection
Stop if it says node not detected, observer runtime, or syncing. Fix the node before registration.
3. Register and self-stake
Review address, amount, fee, and commission. Sign locally and save the transaction hash.
4. Wait for activation
Awaiting activation is normal. Keep the node synchronized and online through the epoch boundary.
How onboarding works
- Provision a nodeMeet the hardware above and open the three ports. A public IP (or a working QUIC/NAT path) lets peers reach you.
- Download the validator bundleGet the validator bundle — a signed, pre-compiled binary with the canonical genesis, config template and launcher (no source or build tools). Verify the published SHA-256 checksum before running. Each validator runs its own identity keypair.
- Generate your keysThe node creates a validator identity + vote keypair on first run. Back these up — they are your validator's identity and cannot be recovered.
- Sync from a snapshotA new node fast-syncs to the finalized tip from a quorum-verified snapshot (
WCAHT_RECOVERY_SNAPSHOT_PEERS) rather than replaying from genesis — usually a few minutes. - Start in validator modeAn observer cannot register or vote. Set
NODE_TYPE=validator, restart once, and confirm the node is synced and detected online with the same identity as your wallet. - Fund your walletUse the in-dashboard faucet to fund your validator identity. Request a little more than the stake minimum (e.g. ~101 WCAHT) so the registration network fee is covered on top of the 100 WCAHT self-stake.
- Register & stakeSubmit a
RegisterValidatortransaction and delegate your self-stake (minimum 100 WCAHT). The stake is queued for activation at the next epoch boundary. - Produce & voteYour node produces blocks in its scheduled 12-slot windows and votes on every block. Stay online — sustained downtime forfeits rewards (and is slashable once slashing activates).
Current network topology
The network currently runs three active voting validators (each self-staked 100,000 WCAHT) plus supporting observer / RPC nodes. The active set is dynamic — it grows automatically as new validators register and activate at each epoch boundary, so the validators shown on the Explorer are the current set, not a fixed group. New validators should bootstrap and sync from one of the active voters (never from an observer), and no existing voter should be retired until its replacement already holds active consensus weight — doing so before the epoch boundary can reduce finality safety.
Get started
Onboarding is self-serve and permissionless — no approval needed. Download the bundle above, sync your node, then register and stake from the dashboard. Join the community for bootstrap peers, help, and announcements: