bitcanna-1
Cosmovisor
is a small process manager for Cosmos SDK application binaries that monitors the governance module for incoming chain upgrade proposals. If it sees a proposal that gets approved, it stops the current binary, switch from the old binary to the new one, and finally restarts the node with the new binary.
This guide will explain how to install Cosmovisor and prepare for a future chain update. A full guide about Cosmovisor can be found here.
You can build Cosmovisor from the source or download it from the official GitHub repository.
The easy way is install with Go:
go install cosmossdk.io/tools/cosmovisor/cmd/cosmovisor@v1.4.0
Version v1.2 and higher includes a new command that will create the required folder structure for you, so it will avoid you some extra steps
v1.2
binary.It should show something like:
3a) Download & copy the next version v.1.3.1
to the upgrades folder.
This guide shows how to download the binary. If you want to build the binary from the source, detailed instructions can be found in the README of our GitHub.
Check the sha256sum.
It must return: ad6784e945135454efc436d22a7661db36bc6a396e7d9cdb7572c4d8d5ccef3f
Verify that the version is:.1.3.1
Move the newly built binary to the upgrades directory.
If you build the binary from the code source move it to the same folder
3b) Download & copy the last version v.1.4.5
to the upgrades folder.
This guide shows how to download the binary. If you want to build the binary from the source, detailed instructions can be found in the README of our GitHub.
Check the sha256sum.
It must return: a4ade068a9c3face2f6e5e052bcdd4d5f2fae52c0c9d6bb804dca565c5642180
Extract and verify that the version is:1.4.5
Move the newly built binary to the upgrades directory.
3c) Download & copy the last version v.1.5.3
to the upgrades folder.
This guide shows how to download the binary. If you want to build the binary from the source, detailed instructions can be found in the README of our GitHub.
Check the sha256sum.
It must return: --------------------tda--------------------
Extract and verify that the version is:1.5.3
Move the newly built binary to the upgrades directory.
If you build the binary from the code source move it to the same folder
Very important decision now. Depending on your choice you should sync the chain using a snapshot file/service or sync from the scratch (very slow process but the only to get the whole original chain by yourself)
The output should look like this:
This will create a `$HOME/.bcna` folder
genesis.json
fileEnsure you have the correct file. Run the SHA256SUM test:
cosmovisor
service. You can avoid the 3rd line if it is a clean installation and bcnad
service doesn't exist.You can speed up the syncing using a StateSync Server or a snapshot file.
If everything is right Cosmovisor will take control of the binaries. Instead of bcnad you must use cosmosvisor run
in your commands, for example: cosmovisor run status
To do this, make the following changes:
Add to the end of the file:
cosmovisor run version
Will be v.1.4.5
before the upgrade and v1.5.3
after the upgradebcnad version
Must show the same version as abovecosmovisor run status
In the future, you must use the cosmovisor
command instead of the bcnad command if you want to perform service related commands.
For example:
sudo service cosmovisor start
sudo service cosmovisor stop
sudo service cosmovisor restart
sudo journalctl -u cosmovisor -f
cosmovisor
, bitcanna