Installing xrpld
4 minDifficulty Checked 2026-11-10- Production needs 8 or more cores, 64 GB of RAM and fast SSD storage.
- Packages come from the XRP Ledger Foundation's repository for Ubuntu, Debian and RHEL.
- A healthy stock server reports server_state full within about 5 to 15 minutes.
An xrpld server is a program that runs all day on a Linux machine. Setting one up takes four steps.
- Get a strong enough machine. The server re-checks every transaction on the network, every few seconds, forever. It needs a fast disk and plenty of memory. A modest machine is fine for experiments. It may not keep up with Mainnet.
- Install the package. The XRP Ledger Foundation publishes ready-made packages. You add its repository, check its signing key, and install.
- Let it sync. The server finds other servers, downloads the latest ledger and starts following along. This normally takes about 5 to 15 minutes.
- Keep it updated. New versions carry new amendments. A server that falls too far behind can stop understanding the network's rules.
You do not need the whole history of the ledger to start. Each ledger holds the complete current state, so a new server grabs the latest one and goes.
One name to know. Until 2026 the program was called rippled. It is now xrpld. Older guides, forum posts and file paths still use the old name. They mean the same software.
A server with the default settings does not vote on anything. It follows the network and answers your questions. That is a stock server.
Recommended for production (bare metal):
| Part | Spec |
|---|---|
| CPU | 3+ GHz 64-bit x86_64, 8+ cores |
| RAM | 64 GB |
| Disk | SSD or NVMe, 10,000 IOPS sustained, at least 50 GB for the database |
| Network | Gigabit interface |
| OS | Ubuntu 20.04+, Debian 11+, or RHEL |
The docs warn against AWS EBS because its latency is too high to sync reliably. Minimum for testing: 4+ cores and 16 GB of RAM. That is not enough to stay synced with Mainnet. Keep the clock accurate with NTP.
Install on Ubuntu or Debian. First save the Foundation's signing key at /etc/apt/keyrings/xrplf.asc and check its fingerprint against the install page. Then:
echo "deb [signed-by=/etc/apt/keyrings/xrplf.asc] https://packages.xrplf.org/repository/deb-stable any main" | sudo tee /etc/apt/sources.list.d/xrplf.list
sudo apt -y update && sudo apt -y install xrpld
systemctl status xrpld.serviceThe package installs /usr/bin/xrpld, creates an xrpld user, and writes a default Mainnet config to /etc/xrpld/xrpld.cfg. The service starts automatically.
Settings to know.
[node_size]: omit it to let the server choose from RAM and CPU threads.hugeis recommended for production and expects 64 GB.[node_db]:type=NuDBfor almost all purposes. RocksDB support is legacy.
Checking sync. xrpld server_info on the machine, or the server_info API method. Read server_state:
| Value | Meaning |
|---|---|
disconnected | Not connected to the network |
connected | Believes it is connected to the network |
syncing | Behind on ledger versions |
tracking | In agreement with the network |
full | Fully caught up |
validating, proposing | Taking part in validation |
complete_ledgers shows the range of ledger versions stored locally.
The rename. XLS-95 renamed the binary from rippled to xrpld and the config from rippled.cfg to xrpld.cfg, starting with version 3.2.0, released 2026-06-15. Default config and database paths changed, so existing nodes follow the migration guide. Flags such as tfNoRippleDirect keep their names because they refer to rippling, not the company.
Related: History and Clio, After the vote.
- System RequirementsRead 2026-11-10
- Install on Ubuntu or Debian LinuxRead 2026-11-10
- Migrate from rippled to xrpldRead 2026-11-10
- Capacity PlanningRead 2026-11-10
- xrpld Server Doesn't SyncRead 2026-11-10
- xrpld Server StatesRead 2026-11-10
- Introducing XRP Ledger version 3.2.0Read 2026-11-10
- XLS-95 Rename ripple(d) to xrpl(d)Read 2026-11-10
