.liked/cosmovisor/genesis/bin/liked
.liked/cosmovisor/upgrades/v2.0.0/bin/liked
.liked/cosmovisor/upgrades/v3.0.0/bin/liked
v3.0.0
is tagged on repo and binary builds are released on github via CIv3.0.0
v3.0.0
binary at the Cosmovisor upgrades folder BEFORE the upgrade time. Alternatively, operators can configure cosmovisor to download binaries automatically.v1.2.0
. A setup guide with migration instructions is available here.upgrade needed
panic. Afterwards, operators shall backup their .liked
folder, then start their node using the new version binary.DAEMON_ALLOW_DOWNLOAD_BINARIES
to true
, which is the default if our setup script or docker image was used. To be safe, we recommend you do prepare the binary manually.app.toml
config, especially the state-sync snapshots feature. By contributing state-sync snapshots, the synchronization process of new nodes can be speeded up from days to minutes. This will be vital to the growth of our network, as the full chain data size is growing rapidly due to more features and applications being added to LikeCoin chain.app.toml
:.liked/data
folder to .liked/data-backup-<date>
after the chain has halted at upgrade height and before the new binary has started.CancelSoftwareUpgrade
proposal--unsafe-skip-upgrades <upgrade height>
to their cosmovisor launch argument.sudo systemctl stop liked
/etc/systemd/system/liked.service
ExecStart=
, append --unsafe-skip-upgrades <upgrade height>
to the end.liked
folder with additional steps in the next section)sudo systemctl daemon-reload
, then sudo systemctl restart liked
.liked
folder to rollback upgradecurrent
binary symlink to the previous version (v2.0.0
for this upgrade):v3.0.0
. CI will test and build with the tagged commit, then release it on GitHub.release/v3.x
and update branch names in node setup guides.upgrade-info
should be validated on testnet beforehand.