Run a validator. Secure the network. Earn from participation.
LiberX is secured by an independent validator quorum. Onboarding is short, hardware is modest, and rewards accrue by epoch.
Active validators
5 / 50
Live testnet cohort vs mainnet target
Estimated validator APR
9.8%
Base rewards · subject to change
Network uptime
99.3%
Rolling 30-day SLO (testnet)
Average preconfirm
3 ms
Measured at the gateway boundary
Why validate
Independent operators secure the venue.
Validators help keep matching, finalization, and bridge attestations live across the network.
Your node participates in preconfirms, finalization, and bridge attestations.
Active validators share in network rewards tied to protocol activity.
Operators help shape parameter decisions as the network evolves.
Joining the validator set is based on running infrastructure — not on private access.
Hardware
Boring, commodity machines.
Run a validator on practical hardware, with room to scale into archive or indexing workloads if needed.
Minimum
Validators running on this tier will stay online most of the time but might miss attestations during peak load. Good to pilot on.
- CPU
- 8 cores
- Memory
- 32 GB
- Storage
- 500 GB NVMe
- Network
- 1 Gbps
Recommended
RecommendedThe sweet spot. Matches the reference image we run in DE-FRA-1 and USA-IAD-1 on the current testnet cohort.
- CPU
- 16 cores
- Memory
- 64 GB
- Storage
- 1024 GB NVMe
- Network
- 1 Gbps
Pro
Headroom for archive snapshots, explorer indexing, or running multiple validator keys behind the same Tailscale endpoint.
- CPU
- 32 cores
- Memory
- 128 GB
- Storage
- 2048 GB NVMe
- Network
- 10 Gbps
5-step onboarding
From setup to active signing in minutes.
A simple operator path from install to participation.
- 1
Install the validator binary
One-line installer that fetches the pinned release and prepares the systemd unit.
$ curl -fsSL https://get.liberx.xyz/validator | bash - 2
Generate your validator key
Creates a BLS key locally. Back it up — losing it means re-registering with a new identity.
$ liberx keygen --out ~/.liberx/validator.key - 3
Register on-chain
Submit the registration extrinsic with your wallet as the payout target.
$ liberx register --stake 50000 --wallet $WALLET - 4
Open the p2p ports
Make the validator port reachable so the gateway can probe it after registration.
$ sudo ufw allow 30303/tcp && sudo ufw allow 30303/udp - 5
Start signing
Run the node against the closest gateway region; validator mode is detected automatically.
$ liberx run --gateway eu-fra-1.liberx.xyz
Node dashboard
See your validator the way the network sees it.
Track liveness, attestations, uptime, and signing performance through the validator view.
No active session.
Connect a stub session to see the dashboard. Real wallet-signed access lands in Phase 4b2 alongside the bridge connectors.
Recent epochs
The last week of rewards on the reference node.
Each row is a five-minute epoch. Base rewards come from protocol fees; the bridge bonus is the attestation stipend that validators earn per release event.
Last 7 epochs
136.4 LBX
7 epochs shown · 5 min each
| Epoch | Blocks | Attestations | Base | Bridge | Total (LBX) |
|---|---|---|---|---|---|
| #4182 | 6 | 412 | 18.70 | +1.20 | 19.90 |
| #4181 | 5 | 408 | 17.90 | +0.80 | 18.70 |
| #4180 | 7 | 419 | 19.40 | +1.70 | 21.10 |
| #4179 | 6 | 410 | 18.20 | +1.10 | 19.30 |
| #4178 | 5 | 402 | 17.60 | +0.60 | 18.20 |
| #4177 | 6 | 414 | 18.50 | +1.30 | 19.80 |
| #4176 | 6 | 411 | 18.40 | +1.00 | 19.40 |
FAQ
Operator questions that come up most often
How does slashing work?
Slashing applies only to safety faults — double-signing a preconfirm or finalisation vote. Liveness faults (downtime) are not slashed; persistent absence rotates you out of the active set without burning the bond.
What is the bond amount?
Testnet bond is 50k LBX-testnet (faucet-funded). The mainnet bond lands with the launch post — expect a figure that keeps solo operators in the game while still filtering out spam registrations.
What happens if my node goes offline?
You stop earning rewards for missed slots. Two consecutive missed epochs trigger a gateway ping; four in a row auto-rotate you to the standby set. You can rejoin without a penalty once the node is healthy.
Do you require a specific ISP or region?
No. We do ask you to publish your region in the registration payload so Explorer can show the set on a map. Residential gigabit works on testnet; for mainnet we strongly recommend a data-center peering relationship.
How do I exit?
Submit an unbond request. Your node keeps signing until the next epoch boundary, then your bond unlocks. There is no multi-week cooldown on testnet; mainnet cooldown publishes with launch.