Connect Your rippled to a Parallel Network
Various alternative test and development networks exist for developers to test their apps or experiment with features without risking real money. The funds used on these networks are not real funds and are intended for testing only. You can connect your
rippled server to any of these test networks.
Caution: On test networks with new and experimental features, you may need to run a pre-production release of the server to sync with the network. See the Parallel Networks Page for information on what code version each network needs.
To connect your
rippled server to the XRP Testnet or Devnet, complete these steps. You can also use these steps to switch back to the production Mainnet after being on the Testnet or Devnet.
1. Configure your server to connect to the right hub.
The recommended installation uses the config file
/etc/opt/ripple/rippled.cfg by default. Other places you can put a config file include
$HOME is the home directory of the user running
$HOME/.local/ripple/rippled.cfg, or the current working directory from where you start
[ips]stanza with the hub for the network you want to connect to:
Comment out the previous
[ips]stanza, if there is one:
# [ips] # r.ripple.com 51235 # zaphod.alloy.ee 51235 # sahyadri.isrdc.in 51235
[network_id]stanza with the appropriate value:
For sidechains and custom networks, everyone who connects to the network should use a value unique to that network. When creating a new network, choose a network ID at random from the integers 11 to 4,294,967,295.
Note: This setting helps your server find peers who are on the same network, but it is not a hard control on what network your server follows. The UNL / trusted validator settings (in the next step) are what actually define what network the server follows.
2. Set your trusted validator list.
validators.txt file. This file is located in the same folder as your
rippled.cfg file and defines which validators your server trusts not to collude.
Uncomment or add the
[validator_list_keys]stanzas for the network you want to connect to:
[validator_list_sites] https://vl.altnet.rippletest.net [validator_list_keys] ED264807102805220DA0F312E71FC2C69E1552C9C5790F6C25E3729DEB573D5860
[validator_list_sites] https://vl.devnet.rippletest.net [validator_list_keys] EDDF2F53DFEC79358F7BE76BC884AC31048CFF6E2A00C628EAE06DB7750A247B12
[validator_list_sites] https://vl.ripple.com [validator_list_keys] ED2677ABFFD1B33AC6FBC3062B71F1E8397C1505E1C42C64D11AD1B28FF73F4734
[validator_list_sites] http://vlamm.devnet.rippletest.net/ [validator_list_keys] 03553F67DC5A6FE0EBFE1B3B4742833D14AF7C65E79E5760EC76EC56EAFD254CE9
Tip: Preview packages might come with the necessary stanzas pre-configured, but check them just in case.
Comment out any previous
# [validator_list_sites] # https://vl.ripple.com # # [validator_list_keys] # ED2677ABFFD1B33AC6FBC3062B71F1E8397C1505E1C42C64D11AD1B28FF73F4734 # Old hard-coded List of Devnet Validators # [validators] # n9Mo4QVGnMrRN9jhAxdUFxwvyM4aeE1RvCuEGvMYt31hPspb1E2c # n9MEwP4LSSikUnhZJNQVQxoMCgoRrGm6GGbG46AumH2KrRrdmr6B # n9M1pogKUmueZ2r3E3JnZyM3g6AxkxWPr8Vr3zWtuRLqB7bHETFD # n9MX7LbfHvPkFYgGrJmCyLh8Reu38wsnnxA4TKhxGTZBuxRz3w1U # n94aw2fof4xxd8g3swN2qJCmooHdGv1ajY8Ae42T77nAQhZeYGdd # n9LiE1gpUGws1kFGKCM9rVFNYPVS4QziwkQn281EFXX7TViCp2RC # n9Jq9w1R8UrvV1u2SQqGhSXLroeWNmPNc3AVszRXhpUr1fmbLyhS
3. Enable (or Disable) Features
For some test networks using experimental features, you must also forcefully enable the appropriate feature in the config file. For other networks, you should not use the
[features] stanza. Add or modify the
[features] stanza of your config file as follows:
# [features] # Delete or comment out. Don't force-enable features on Testnet.
# [features] # Delete or comment out. Don't force-enable features on Devnet.
# [features] # Delete or comment out. Don't force-enable features on Mainnet.
(On Mainnet, Testnet, and Devnet, no you)
Warning: Do not use the
[features] stanza when connecting to Mainnet or Testnet. Forcefully enabling different features than the rest of the network could cause your server to diverge from the network.
4. Restart the server.
$ sudo systemctl restart rippled
5. Verify that your server syncs.
It takes about 5 to 15 minutes to sync to the network after a restart. After your server is synced, the server_info method shows a
validated_ledger object based on the network you are connected to.
To confirm that your
rippled is connected to the right network, compare the results from your server to a public server on the Testnet or Devnet. The
seq field of the
validated_ledger object should be the same on both servers (possibly off by one or two, if it changed as you were checking).
The following example shows how to check your server's latest validated ledger from the commandline:
rippled server_info | grep seq
You can use server_info in the WebSocket Tool to look up the latest ledger index (
seq) on the intended network.