This directory contains python scripts to tests and explore side chains.
This document walks through the steps to setup a side chain running on your local machine and make your first cross chain transfers.
This section describes how to install the python dependencies, create the environment variables, and create the configuration files that scripts need to run correctly.
You will need at least Python 3.8 for this.
pip install sidechain-launch-kit
Checkout the sidechain branch from the rippled repository, and follow the usual process to build rippled.
The python scripts need to know the locations of two files and one directory. These can be specified through command line arguments, by adding variables in the .env file, or by setting environment variables.
Please note that 'standalone' mode means that the main chain is running as a standalone XRPL network and is not an instance of the XRPL mainnet, testnet or devnet. Also, the sidechain needs a mainchain to start and cannot exist by itself.
- The location of the rippled executable used for main chain servers. Either set the environment variable
RIPPLED_MAINCHAIN_EXE(in your system or in the.envfile) or use the command line switch--exe_mainchain. Until a new RPC is integrated into the main branch (this will happen very soon), use the code built from the sidechain branch as the main chain exe. - The location of the rippled executable used for side chain servers. Either set the environment variable
RIPPLED_SIDECHAIN_EXE(in your system or in the.envfile) or use the command line switch--exe_sidechain. This should be the rippled executable built from the sidechain branch. - The location of the directory that has the rippled configuration files. Either set the environment variable
RIPPLED_SIDECHAIN_CFG_DIR(in your system or in the.envfile) or use the command line switch--cfgs_dir. The configuration files do not exist yet. There is a script to create these for you. For now, just choose a location where the files should live and make sure that directory exists. - The number of federators to have in the sidechain. This must be a number between 1 and 8. Either set the environment variable
NUM_FEDERATORS(in your system or in the.envfile) or use the command line switch--num_federators. The script that creates the config files uses this number to create the right config files for that number of federators.
- The IP address of a node on the mainchain. Either set the environment variable
MAINNET(in your system or in the.envfile) or use the command line switch--mainnet. This is used in both the script that creates the config files and in the script that runs the sidechain. - The public Websocket port of the mainchain node. Either set the environment variable
MAINNET_PORT(in your system or in the.envfile) or use the command line switch--mainnet_port. This is used in both the script that creates the config files and in the script that runs the sidechain. - The seed of the issuer of the cross-chain token. Either set the environment variable
IOU_ISSUER(in your system or in the.envfile) or use the command line switch--iou_issuer. This is used in both the script that creates the config files and in the script that runs the sidechain. - The seed of the door account on the mainchain. Either set the environment variable
DOOR_ACCOUNT_SEED(in your system or in the.envfile) or use the command line switch--door_seed. This is used in the script that creates the config files.
Setting environment variables can be very convenient. For example, a small script can be written to set these environment variables when working with sidechains.
Assuming rippled is built, and the environment variables are set, run the following script:
sidechain-config --assets USD
There should now be many configuration files in the directory specified by the RIPPLED_SIDECHAIN_CFG_DIR environment variable. The --assets usd creates a sample cross chain asset for USD -> USD transfers.
There is an interactive shell that can be used to explore side chains. It will use the configuration files built above to spin up test rippled main chain running in standalone mode as well as 5 side chain federators running in regular consensus mode.
To start the shell, run the following script:
sidechain-launch --shell
The shell will not start until the servers have synced. It may take a minute or two until they do sync. The script should give feedback while it is syncing.
Once the shell has started, the following message should appear:
Welcome to the sidechain test shell. Type help or ? to list commands.
SSX>
Type the command server_info to make sure the servers are running. An example output would be:
SSX> server_info
pid config running server_state ledger_seq complete_ledgers
main 0 136206 mainchain/rippled.cfg True proposing 75 2-75
side 0 136230 sidechain_0/rippled.cfg True proposing 92 1-92
1 136231 sidechain_1/rippled.cfg True proposing 92 1-92
2 136232 sidechain_2/rippled.cfg True proposing 92 1-92
3 136233 sidechain_3/rippled.cfg True proposing 92 1-92
4 136234 sidechain_4/rippled.cfg True proposing 92 1-92
Of course, you'll see slightly different output on your machine. The important thing to notice is there are two categories, one called main for the main chain and one called side for the side chain. There should be a single server for the main chain and five servers for the side chain.
Next, type the balance command, to see the balances of the accounts in the address book:
SSX> balance
balance currency peer limit
account
main root 99,999,989,999.999985 XRP
door 9,999.999940 XRP
side door 99,999,999,999.999954 XRP
There are two accounts on the main chain: root and door; and one account on the side chain: door. These are not user accounts. Let's add two user accounts, one on the main chain called alice and one on the side chain called bob. The new_account command does this for us.
SSX> new_account mainchain alice
SSX> new_account sidechain bob
This just added the accounts to the address book, but they don't exist on the ledger yet. To do that, we need to fund the accounts with a payment. For now, let's just fund the alice account and check the balances. The pay command makes a payment on one of the chains:
SSX> pay mainchain root alice 5000
SSX> balance
balance currency peer limit
account
main root 99,999,984,999.999969 XRP
door 9,999.999940 XRP
alice 5,000.000000 XRP
side door 99,999,999,999.999954 XRP
bob 0.000000 XRP
Finally, let's do something specific to side chains: make a cross chain payment. The xchain command makes a payment between chains:
SSX> xchain mainchain alice bob 4000
SSX> balance
balance currency peer limit
account
main root 99,999,984,999.999969 XRP
door 13,999.999940 XRP
alice 999.999990 XRP
side door 99,999,995,999.999863 XRP
bob 4,000.000000 XRP
Note: the account reserve on the side chain is 100 XRP. The cross chain amount must be greater than 100 XRP or the payment will fail.
Making a cross chain transaction from the side chain to the main chain is similar:
SSX> xchain sidechain bob alice 2000
SSX> balance
balance currency peer limit
account
main root 99,999,984,999.999969 XRP
door 11,999.999840 XRP
alice 2,999.999990 XRP
side door 99,999,997,999.999863 XRP
bob 1,999.999990 XRP
If you typed balance very quickly, you may catch a cross chain payment in progress and the XRP may be deducted from bob's account before it is added to alice's. If this happens just wait a couple seconds and retry the command. Also note that accounts pay a ten drop fee when submitting transactions.
Finally, exit the program with the quit command:
SSX> quit
Thank you for using the sidechain shell. Goodbye.
WARNING: Server 0 is being stopped. RPC commands cannot be sent until this is restarted.
Ignore the warning about the server being stopped.
Those two cross chain payments are a "hello world" for side chains. It makes sure you're environment is set up correctly.
If you run into any bugs or other problems with the library, please report them as issues in the Sidechain Launch Kit repo.