How to Run an XRPL Validator: Complete Setup Guide
Want to help secure the XRP Ledger? Here's the complete technical guide to running your own XRPL validator node.
Running an XRPL validator supports network decentralization and gives you a voice in governance. You need 8+ cores, 64GB RAM, 500GB+ SSD, and reliable internet. There are no financial rewards — it's a public service. Getting on the default UNL requires sustained uptime and community trust.
| Key facts | |
|---|---|
| CPU | 8+ cores recommended |
| RAM | 64GB minimum |
| Storage | 500GB+ NVMe SSD |
| Bandwidth | 100Mbps+ |
| OS | Ubuntu 22.04 LTS recommended |
| Rewards | None (public service) |
What XRPL Validators Do
XRPL validators are the backbone of the consensus process. They propose transaction sets, vote on their validity and ordering, and agree on the canonical ledger state — all in 3-5 seconds per round.
Validators propose which transactions to include and in what order, then reach consensus with other validators.
Each validator independently computes the resulting ledger state and publishes a validation confirming agreement.
Validators vote on protocol amendments — new features, bug fixes, parameter changes. 80% agreement activates an amendment.
More diverse validators = more resilient network. Geographic and organizational diversity strengthens the XRPL.
Hardware & Software Requirements
| Component | Minimum | Recommended |
|---|---|---|
| CPU | 4 cores | 8+ cores (modern Xeon/EPYC) |
| RAM | 32GB | 64GB+ |
| Storage | 250GB SSD | 500GB+ NVMe SSD |
| Network | 50Mbps | 100Mbps+ dedicated |
| OS | Ubuntu 20.04+ | Ubuntu 22.04 LTS |
| Uptime | 95% | 99.9%+ for UNL |
Setup Steps
1. Provision a Server
Set up a dedicated server or cloud instance (AWS, Google Cloud, Hetzner). Ubuntu 22.04 LTS recommended.
2. Install rippled
Add the official Ripple apt repository and install rippled: `sudo apt install rippled`. Follow the official installation guide at xrpl.org.
3. Generate Validator Keys
Use the `validator-keys` tool to generate your validator key pair. Store the secret key securely — it's your validator's identity.
4. Configure rippled.cfg
Set [validator_token] with your validator token, configure peer ports, database paths, and network parameters.
5. Enable Validation
Set `[validation_seed]` or `[validator_token]` in your config. Start rippled and verify it's participating in consensus.
6. Monitor
Set up monitoring (Prometheus/Grafana) to track sync status, validation count, peer connections, and server health.
Never share your validator secret key. If compromised, an attacker could impersonate your validator. Generate keys on a secure, offline machine and transfer only the token to your server.
Key Configuration
| Setting | Purpose | Value |
|---|---|---|
| [validator_token] | Validator identity token | Generated by validator-keys tool |
| [peer_private] | Hide validator from crawlers | 1 (recommended) |
| [network_id] | Network selection | 0 (mainnet) |
| [node_size] | Server resource allocation | huge (for validators) |
| [ledger_history] | Ledger history to keep | 256+ (or full) |
Getting on the UNL
The Unique Node List (UNL) is the set of validators that other XRPL nodes trust for consensus. Getting on the default UNL is the gold standard — it means the network trusts your validator.
Sustained Reliability
Demonstrate 99.9%+ uptime over months. The XRPL Foundation tracks validator performance metrics.
Known Entity
UNL validators are typically run by known organizations — universities, businesses, foundations. Anonymous validators are unlikely to be added.
Community Contribution
Active participation in XRPL development, governance discussions, or ecosystem projects strengthens your case.
Apply to XRPL Foundation
Submit your validator information through the XRPL Foundation's validator program for consideration.
Best Practices
Run your validator separate from any stock (full history) server. Validators should be lean and focused.
Keep rippled updated. Set up automated update processes with testing before deploying to production.
Use redundant power, network, and storage. Consider failover servers in different data centers.
Firewall all ports except peer (51235). Use SSH keys only. No unnecessary services running.
Frequently Asked Questions
What does an XRPL validator do?
Validators participate in consensus — proposing, validating, and agreeing on transaction ordering for each ledger. They use the XRP Ledger Consensus Protocol (Byzantine agreement) to achieve consensus in 3-5 seconds. No mining involved.
Do validators earn rewards?
No — unlike PoW/PoS, XRPL validators receive no block rewards or fees. Running a validator is a public service that supports decentralization and gives you a voice in network governance.
What hardware do I need?
Minimum: 8+ CPU cores, 64GB RAM, 500GB+ NVMe SSD, 100Mbps+ internet. Cloud instances like AWS c5.2xlarge work well. Enterprise-grade hardware for UNL-listed validators.
How do I get on the UNL?
Demonstrate 99.9%+ uptime, contribute to the XRPL community, be a known/trusted entity, and apply through the XRPL Foundation's validator program. It's trust-based, not automatic.
Can I run a validator at home?
Technically yes, but not recommended for production. Use a data center or cloud provider for reliability. A non-validating stock node for development is fine at home.
How many validators does the XRPL have?
The XRPL has 100+ validators globally, with 35+ on the default UNL. The network is designed to work with a diverse set of validators run by universities, businesses, exchanges, and individuals.
Continue Learning
Support the XRP Ledger
Running a validator strengthens the network for everyone. Start with the fundamentals.
Last updated: February 15, 2026. Written by the AllAboutXRP Editorial Team. Sources: XRPL.org validator documentation.
Get XRP insights delivered weekly
Free weekly newsletter. No spam, unsubscribe anytime.