This page describes the recommended instructions for installing the latest stable version of xrpld on Red Hat Enterprise Linux, using a binary that has been compiled and published by Ripple as an rpm package.
Currently, Red Hat Enterprise Linux (RHEL) 9.6 is supported on x86_64 processors. You may also be able to adapt these instructions to similar Linux distributions including CentOS or Rocky Linux, but other configurations are not officially supported.
Before you install xrpld, you must meet the System Requirements.
Install the Ripple RPM repository:
Choose the appropriate RPM repository for the stability of releases you want:
stable- The latest stable releaseunstable- Pre-release builds such as betas or release candidatesnightly- Nightly development builds
cat << REPOFILE | sudo tee /etc/yum.repos.d/ripple.repo [ripple-stable] name=XRP Ledger Packages enabled=1 gpgcheck=0 repo_gpgcheck=1 baseurl=https://repos.ripple.com/repos/rippled-rpm/stable/ gpgkey=https://repos.ripple.com/repos/rippled-rpm/stable/repodata/repomd.xml.key REPOFILEFetch the latest repo updates:
sudo yum -y updateInstall the new
xrpldpackage:sudo yum install xrpldReload systemd unit files:
sudo systemctl daemon-reloadConfigure the
xrpldservice to start on boot:sudo systemctl enable xrpld.serviceStart the
xrpldservice:sudo systemctl start xrpld.service
It can take several minutes to sync with the rest of the XRP Ledger network, during which time the server outputs various warnings. For information about log messages, see Understanding Log Messages.
You can use the xrpld commandline interface to see if your server is synced with the network:
xrpld server_infoIf the server_state in the response is full or proposing, then your server is fully synced to the network. Otherwise, you may need to wait longer. Fresh servers usually sync within 15 minutes; servers that already have ledger history stored can take longer.
After your server has synchronized with the rest of the network, you have a fully functional XRP Ledger peer-to-peer server that you can use to submit transactions or get API access to the XRP Ledger. See Client Libraries or HTTP / WebSocket APIs for different ways to communicate with the server.
If you use the XRP Ledger for your business or you want to contribute to the stability of the network, you should run one server as a validator. For information about validating servers and why you might want to run one, see Run xrpld as a Validator.
Having trouble getting your server started? See xrpld Server Won't Start.
xrpld should connect to the XRP Ledger with the default configuration. However, you can change your settings by editing the xrpld.cfg file. For recommendations about configuration settings, see Capacity Planning.
The recommended installation uses the config file /etc/xrpld/xrpld.cfg by default. Other places you can put a config file include $HOME/.config/xrpld/xrpld.cfg (where $HOME is the home directory of the user running rippled), $HOME/.local/xrpld/xrpld.cfg, or the current working directory from where you start rippled.
The config file was renamed from rippled.cfg to xrpld.cfg. During the transition, if xrpld.cfg is not present the server still reads rippled.cfg from the same locations, so existing config files keep working without being renamed. 
See the rippled GitHub repository for a description of all configuration options.
You must restart xrpld for any configuration changes to take effect.
If you change the [debug_logfile] or [database_path] sections, you may need to grant ownership of the new configured path to the user you run xrpld as.
You must update xrpld regularly to remain synced with the rest of the XRP Ledger network. You can subscribe to the xrpld Google Group to receive notifications of new xrpld releases.
The xrpld package includes a script you can use to enable automatic updates on Linux. On other platforms, you must update manually.