Client
rippled (xrpld)
xrpl
Install rippled (xrpld) as a self-hosted XRP Ledger full node on your server. This guide covers the agent, network selection, setup, and sync.
rippled (xrpld)
rippled JSON-RPC / WebSocket
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.
mainnettestnet
Choose mainnet, testnet in Toolkit, then follow these steps to provision and run a XRP Ledger full node.
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.