Software Upgrade

This guide outlines the steps required to upgrade your Sentinel Hub software. Follow these instructions carefully to ensure a smooth process.

Upgrade List

Upgrade #	Binary Version	Name	Block Height	Proposal #	Commit Hash
upgrade-1	v0.7.0	upgrade-1	1,272,000	3	600fd5f
upgrade-2	v0.8.3	upgrade-2	2,586,000	5	fa7cd3c
upgrade-3	v0.9.2	upgrade-3	5,125,000	9	d04a400
upgrade-4	v0.10.1	upgrade-4	9,348,475	19	bbe6fab
upgrade-5	v0.11.2	v11	12,310,005	30	54c28ae

Upgrade Steps

At the specified block height, the blockchain will halt. Follow these steps only after the blockchain stops producing new blocks.

Stop the node

Run the following command to verify the latest block height matches the upgrade height:

curl -fsLS http://127.0.0.1:26657/status | jq -r '.result.sync_info.latest_block_height'

Stop the running node to prepare for the upgrade.

sudo systemctl stop sentinelhub.service

Install the new version

Clone the source code and replace <binary_version> with the version from the table:

VERSION=<binary_version>
BASE_DIRECTORY=${GOPATH}/src/github.com/sentinel-official

rm -rf ${BASE_DIRECTORY}/hub/ && mkdir -p ${BASE_DIRECTORY} && cd ${BASE_DIRECTORY}/ && \
git clone https://github.com/sentinel-official/hub.git && cd ${BASE_DIRECTORY}/hub/ && \
git checkout ${VERSION}

Build and install the software

make install

Start the node

Confirm the new version is installed correctly:

sentinelhub version --long

Start the sentinelhub process

sudo systemctl start sentinelhub.service

In Case of Upgrade Failure

• Use the version immediately before the failed upgrade (note: if you are installing software upgrade-1, use the version 0.6.3).

• Confirm the installation matches the details in the table above.

• Start the sentinelhub process with flag unsafe-skip-upgrades at the upgrade block height

sentinelhub start --unsafe-skip-upgrades <block_height>

This process ensures minimal downtime and a smooth transition between software versions.