From 6044d2aaf3f286e97ce261bc6e3db6613a83774d Mon Sep 17 00:00:00 2001 From: Anthea Wang Date: Tue, 23 Jul 2024 04:16:01 +0000 Subject: [PATCH] GITBOOK-263: Add Upgrade Details to Step 0 Network Upgrade section --- for-node-hosts/running-nodes/cronos-mainnet/README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/for-node-hosts/running-nodes/cronos-mainnet/README.md b/for-node-hosts/running-nodes/cronos-mainnet/README.md index 6c5c798..52f14df 100644 --- a/for-node-hosts/running-nodes/cronos-mainnet/README.md +++ b/for-node-hosts/running-nodes/cronos-mainnet/README.md @@ -74,13 +74,13 @@ Note that all depends on the type of node you are running and settings will vary {% endtab %} {% endtabs %} -## Step 0 : Notes on "Huygen" Network upgrade +## Step 0 : Notes on Network Upgrade Before we start, please note that there was "_Huygen_" network upgrade at the block height `2,693,800`, which requires the node operator to update their Cronos Mainnet binary `cronosd` from `v0.6.*` to `v0.7.0`. For the host who would like to build a Full Node with complete blockchain data from scratch, one would need to: -
Block HeightBinary VersionInstruction
1 ~ 2,693,800cronos_v0.6.*Start the node with the older binary version cronos_v0.6.*

Sync-up with the blockchain until it reaches the target upgrade block height 2,693,800
2,693,800 ~ 3982500cronos_v0.7.0After it reaches the block height 2,693,800, update app.toml with new config items

Update the binary to cronos_v0.7.0
Restart the node
3982500cronos_v0.8.3After reaching block height, update iavl-disable-fastnodein app.toml

Update the binary to cronos_v0.8.3
Restart the node
6542800cronos_v1.0.2After reaching block height, update app-db-backendin app.toml.

Update the binary to cronos_v1.0.2
Restart the node
11608760v1.0.15After reaching block height, update, update the binary to v1.0.15
Restart the node
+
Block HeightBinary VersionInstruction
1 ~ 2693800cronos_v0.6.*Start the node with the older binary version cronos_v0.6.*

Sync-up with the blockchain until it reaches the target upgrade block height 2,693,800
2693800 ~ 3982500cronos_v0.7.0After it reaches the block height 2,693,800, update app.toml with new config items

Update the binary to cronos_v0.7.0
Restart the node
3982500cronos_v0.8.3After reaching block height, update iavl-disable-fastnodein app.toml

Update the binary to cronos_v0.8.3
Restart the node
6542800cronos_v1.0.2After reaching block height, update app-db-backendin app.toml.

Update the binary to cronos_v1.0.2
Restart the node
11608760cronos v1.0.15After reaching block height, update the binary to v1.0.15
Restart the node
13184000cronos v1.1.0After reaching block height, update the binary to v1.1.0
Restart the node
13520000cronos v1.2.0After reaching block height, update the binary to v1.2.0
Restart the node
14920000cronos v1.3.0After reaching block height, update the binary to v1.3.0
Restart the node
@@ -90,7 +90,7 @@ Users can refer to the [upgrade guide of "Huygen"](huygen.md) for the detailed u To patch "unlucky" transactions, follow this guide on [patching unlucky tx](patching-unlucky-tx.md) {% endhint %} -## Step 1. Get the Cronos Mainnet binary +## Step 1. Get the Cronos Mainnet Binary {% hint style="info" %} Remarks: