Home/Networks/XRP Ledger

xrpl

XRP Ledger full node

Run rippled as a full XRP Ledger node — complete ledgers back to genesis, not a stock short-history server.

Client

rippled (xrpld)

RPC

rippled JSON-RPC / WebSocket

History

complete_ledgers from genesis (32570 mainnet, 1 testnet) — not a short window.

Stock rippled can look healthy while history is a thin window. On Install you pick how much history to keep: stock (~2h), 1 day, 2 weeks (default), or full genesis→tip (~39 TiB, no public snapshot). Synced is complete_ledgers covering that window (32570 on mainnet for full).

Mainnet and testnet are separate envs. After start, Node Config edits xrpld cfg. Clio is not required day one — clients still hit the Go proxy.

Environments

mainnettestnet

Install

  1. On Ubuntu 24.04 LTS:
    bash
    curl -fsSL "https://toolkit.rpcnode.dev/install/agent.sh" | sudo bash
    Supported and recommended: Ubuntu 24.04 LTS (amd64 or arm64). Other operating systems have not been tested.
  2. Panel → Add server (Agent URL + token) → Add node → XRP Ledgermainnet.
  3. Confirm ports, choose install options if this chain has them, install rippled (xrpld), snapshot if required, start. Watch sync on the node page.

Operate from the panel

After the node is up you manage it in the same UI — Node Config (edit the live files and apply), client updates, restart, logs, public RPC. You do not need SSH to change conf. Install-time choices (snapshot flavor, history window, disk layout) are stored on that node.

FAQ

How do I run a XRP Ledger full node?
Install the host agent, add the server, then Add node → XRP Ledger. Toolkit provisions rippled (xrpld).
Can I change the XRP Ledger config later?
Yes. Node page → Node Config. Edit and apply; restart from the same page. A different snapshot or history flavor is an Install choice — changing it later usually means wipe and Add node again.
Pruned or light?
complete_ledgers from genesis (32570 mainnet, 1 testnet) — not a short window.
Catalog
/clients/xrpl/ · catalog.json

Other networks