Join the XRP Ledger EVM Sidechain Devnet


The EVM compatible sidechain implementation is a proof of concept extension to the XRP Ledger protocol and is for development purposes only. There is no official amendment currently and it is not available on the production Mainnet. The EVM compatible sidechain bridge is connected to the XRP Ledger Devnet. Do not send transactions in Mainnet.

This tutorial walks you through the steps to join the existing XRP Ledger EVM Sidechain Devnet.

For ease of use, create an alias, exprd, to run all commands inside your Docker container.

EVM Sidechain Node Hardware Requirements

  • Linux/AMD64 operating system.
  • 4 or more physical CPU cores.
  • At least 500GB of NVME SSD disk storage.
  • At least 32GB of RAM.
  • At least 100Mbps network bandwidth.


Before proceeding to initialize the node, ensure that the following pre-requisites are installed and running:

  • Docker 19+
  • Create an alias to run all commands in this tutorial inside a Docker container:
    alias exrpd="docker run -it --rm -v ~/.exrpd:/root/.exrpd peersyst/xrp-evm-blockchain:latest exrpd"

Initialize Node

The first task is to initialize the node, which creates the necessary validator and node configuration files.

  1. Initialize the chain parameters using the following command:
    exrpd config chain-id exrp_1440002-1
  2. Create or add a key to your node. For this tutorial, we use the test keyring:
    exrpd keys add <key_name> --keyring-backend test

    Note the key_name you enter as you need to reference it in subsequent steps.

    Note For more information on a more secure setup for your validator, refer to cosmos-sdk keys and keyrings and validator security.

  3. Initialize the node using the following command:
    exrpd init <your_custom_moniker> --chain-id exrp_1440002-1

    Monikers can contain only ASCII characters. Using Unicode characters renders your node unreachable.

All these commands create your ~/.exrpd (i.e $HOME) directory with subfolders config/ and data/. In the config directory, the most important files for configuration are app.toml and config.toml.

Genesis & Seeds

  1. Copy the Genesis File.

    Download the genesis.json file from here and copy it to the config directory: ~/.exrpd/config/genesis.json. This is a genesis file with the chain-id and genesis accounts balances.

    wget ~/.exrpd/config/

    Verify the genesis configuration file:

    exrpd validate-genesis
  2. Add Persistent Peer Nodes

    Set the persistent_peers field in ~/.exrpd/config/config.toml to specify peers with which your node maintains persistent connections. You can retrieve them from the list of available peers on the archive repo (

    To get a list of entries from the peers.txt file in the PEERS variable, run the following command:

    PEERS=`curl -sL | sort -R | head -n 10 | awk '{print $1}' | paste -s -d, -`

    Use sed to include them in the configuration. You can also add them manually:

    sed -i.bak -e "s/^persistent_peers *=.*/persistent_peers = \"$PEERS\"/" ~/.exrpd/config/config.toml

Start a Node

  1. Start a node container.
    exrpd start
  2. Provide Peersyst ( ) with the key from this command:
    exrpd keys show <key_name> --keyring-backend=<keyring>

    Note: Peersyst provides your node with proof of authority to validate blocks on Devnet. This process takes 2-3 days.

Run a Devnet Validator Node

Warning: Before creating a Devnet validator node, ensure that:

  • Peersyst provides your node with proof of authority.
  • You're running the node container.

Create a Devnet validator node with this command:

exrpd tx staking create-validator \
  --amount=1000000axrp \
  --pubkey=$(exrpd tendermint show-validator) \
  --moniker="<your_custom_moniker>" \
  --chain-id=<chain_id> \
  --commission-rate="0.05" \
  --commission-max-rate="0.20" \
  --commission-max-change-rate="0.01" \
  --min-self-delegation="1000000" \
  --gas="auto" \
  --gas-prices="0.025axrp" \


  • If you used a different keyring backend from the default os , you need to include this option:
  • When specifying commission parameters, the  commission-max-change-rate  is used to measure %  point  change over the  commission-rate . For example, 1% to 2% is a 100% rate increase, but only 1 percentage point.
  • Min-self-delegation  is a strictly positive integer that represents the minimum amount of self-delegated voting power your validator must always have. A  min-self-delegation  of  1000000  means your validator will never have a self-delegation lower than  1 axrp .

Once enough voting power (+2/3) from the genesis validators is up-and-running, the node starts producing blocks.