ChainLayer offers two types of downloads for Cosmos, default and archive.
We provide an ansible playbook to rollout a new server. This is the fastest way to get a new server going. Especially if you are already using ansible.
git clone https://github.com/chainlayer/quicksync-cosmos
vim group_vars/cosmos.yml # edit your cosmos information here
vim ansible-hosts.yml # edit your hosts here
# The quicksync for the smallest download runs approximately 30 minutes based on your region and download speed.
# You can check the progress of the download on the destination server with
# `tail aria.log`
Making a sha512 of the complete download takes a long time, so instead we make a sha512 hash of every 1st mb block every 1Gb. These hashes are then stored in a checksum file. The hash of that checksum file is stored onchain on the
cosmos account as a memo.
So in short you can verify the sha512 of the checksum file by looking up the transaction hash on-chain. Then you can use the checksum file to validate the download. A checksum.sh script script it provided to do so.
We recommend you to use a download manager like Aria2 to speed up downloads and make sure you can resume when something goes wrong
Whenever a new file is added, the old one is still kept for 24 hours to allow users to finish a download.
# Stop Cosmos Daemon first
sudo apt-get update -y
sudo apt-get install wget liblz4-tool aria2 -y
sudo su - [cosmosuser]
aria2c -x5 https://get.quicksync.io/$FILENAME
# Compare checksum with onchain version. Hash can be found at https://get.quicksync.io/columbus-3-pruned.DATE.TIME.tar.lz4.hash
curl -s https://lcd-cosmos.cosmostation.io/txs/`curl -s https://get.quicksync.io/$FILENAME.hash`|jq -r '.tx.value.memo'|sha512sum -c
lz4 -d $FILENAME | tar xf -
# Start Cosmos Daemon
Remember to set your nodes pruning and indexing settings to match the download you are getting