The "v1.3" upgrade guide (v1.2.* to v1.3.0)
The Cronos v1.3.0 - "v1.3" upgrade is proposed to be scheduled at the block height of 14,920,000. Referencing estimated time can be found here.
DO NOT UPGRADE to the binary v1.3.0 before that suggested upgrade schedule.
You might check the current block height with the Cronos Explorer
Step 0 - Don't panic
At the point of the proposed upgrade, the user will see the error message on the cronosd
similar to the below:
Don't panic - The Chain will be paused to allow the majority of validators to upgrade. Validators and full node hosts will have to upgrade your Cronos nodes to the latest release binary.
Backups
Before the upgrade, node hosts are encouraged to take a complete data backup. backup depends heavily on infrastructure, but generally, we can do this by backing up the .cronos
directory.
Step 1 - Get the v1.3.0
binary
v1.3.0
binaryTo simplify the following step, we will be using Linux-x86 for illustration. Binary for Mac Windows with different DB and architecture are also available here.
Terminate the
cronosd
; afterwards, download the1.3.0
released binaries from github:
Remarks: If you have stated cronosd
with systemd service, kindly stop it by
And replace the binary in the location where the ExecStart
states in Systemd Unit file.
Step 1.1 - Verify the version
You can verify the installation by checking the version of cronosd
, the latest version is 1.3.0
.
Step 2. - Run everything
We are ready to start the node join the network again with the new binary:
Start
cronosd
, e.g.:
Remark: Once the cronosd
is started we will see the message
and there will be an iteration over the previous blockchain data. This process will take a while, which is depending on the size of the database and the hardware specs.
Afterwards, sit back and wait for the syncing process. You can query the node syncing status by
If the above command returns false
, it means that your node is synced; otherwise, it returns true
and implies your node is still catching up.
At this step, you've successfully performed the v1.3 upgrade!
Last updated