First, clone the
GeoDB-Limited/odin-testnet-public-tools repository onto your computer. Make sure that you have at least 20 GB of storage space on the disk.
git clone https://github.com/GeoDB-Limited/odin-testnet-public-tools and then
cd odin-testnet-public-tools/ to begin working within the project folder.
We have included a quickstart shell script to streamline the initialization process. You can use it by running
./node/start.sh to start the node.
If you prefer to run the commands yourself step-by-step, run the following:
cd node/ to change directory into the node folder.
docker-compose pull to pull the latest image.
docker-compose up -d to start the initialization and node containers in the background. You can then run
docker-compose logs -f to view the logs for the init and node containers. The init container is expected to stop and return exit code 0 very quickly. The node container will begin syncing with the network, which is likely to take a few hours depending on your network speed and the current size of the ledger.
You can check the network's latest block by running
docker exec -it node bandd status --node http://22.214.171.124:26657 and looking for the value
"latest_block_height":"XXXXXX". This will give you some idea of the progress your node has made to sync it.
You can check the total disk usage of your ODIN node with
docker system df -v and looking for the size of the
All of the commands in this guide use variables in commands for the chain ID. This is so that you can easily switch to a new chain during the testing phase when development moves to a new chain. To set your chain variable to the latest chain ID, run: