diff --git a/for-node-hosts/running-nodes/cronos-testnet.md b/for-node-hosts/running-nodes/cronos-testnet.md index fb36368..9991f0e 100644 --- a/for-node-hosts/running-nodes/cronos-testnet.md +++ b/for-node-hosts/running-nodes/cronos-testnet.md @@ -70,26 +70,17 @@ Note that all depends on the type of node you are running and settings will vary {% tab title="Testnet" %} * [Seeds for Fullnode](https://github.com/crypto-org-chain/cronos-testnets/blob/main/testnet.json#L21) * [Genesis files](https://raw.githubusercontent.com/crypto-org-chain/cronos-testnets/main/cronostestnet\_338-3/genesis.json) -* Binaries are available [here](https://github.com/crypto-org-chain/cronos/releases) +* [Binaries Links](https://github.com/crypto-org-chain/cronos/releases) {% endtab %} {% endtabs %} -### Step 0 : Notes on testnet Network upgrade +### Step 0 : Notes on Testnet Network upgrade -This is a detailed documentation for setting up a full node on Crypto.org Cronos testnet `cronostestnet_338-3`. +This is a detailed documentation for setting up a full node on Cronos testnet `cronostestnet_338-3`. -Before we start, please note that there are three binary upgrades along with the testnet: +Before we start, please note that there are several binary upgrades along with the testnet: -| Block Height | Binary Version | Instruction | -| ------------ | --------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| \~ `1553700` | [cronos\_0.6.0-testnet](https://github.com/crypto-org-chain/cronos/releases/tag/v0.6.0-testnet) |

Follow Step 1 to Step 3 and start the node with the older binary version v0.6.0;

Sync-up with the blockchain until it reaches the target upgrade block height 1553700;


Please note that panic: UPGRADE "v0.7.0" NEEDED at height: 1553700 is the expected error message when we hit that block.

| -| `1553700` | [cronos\_0.7.0-rc1-testnet](https://github.com/crypto-org-chain/cronos/releases/tag/v0.7.0-rc1) |

After it reaches the block height 1553700, update the binary to cronos_0.7.0-rc1-testnet;

Then update the default ~/.cronos/config/app.toml(given there are some new parameters introduced in the upgrade), either by manually replacing the local app.toml with this new app.toml, or by: $ curl https://raw.githubusercontent.com/crypto-org-chain/cronos-testnets/main/cronostestnet_338-3/app.toml > ~/.cronos/config/app.toml

Then continue to sync from block 1553700;

| -| `1869000` | [cronos\_0.7.0-rc2-testnet](https://github.com/crypto-org-chain/cronos/releases/tag/v0.7.0-rc2) |

After it reaches the block height 1869000, update the binary to cronos_0.7.0-rc2-testnet;


Start the node again and continue to sync from block1869000;

| -| `2483600` | [cronos\_0.7.0-rc3-testnet](https://github.com/crypto-org-chain/cronos/releases/tag/v0.7.0-rc3) |

After it reaches the block height 2483600, update the binary to cronos_0.7.0-rc3-testnet;

Start the node again

| -| `4904100` | [cronos\_0.8.1-testnet](https://github.com/crypto-org-chain/cronos/releases/tag/v0.8.1) |

After it reaches the block height 4904100, update the binary to cronos_0.8.1-testnet;

Start the node again

| -| `5138880` | [cronos\_0.9.0-beta2-testnet](https://github.com/crypto-org-chain/cronos/releases/tag/v0.9.0-beta2) |

After it reaches the block height 5138880, update the binary to cronos_0.9.0-beta2-testnet;

Start the node again

| -| `6134000` | [cronos\_1.0.0-rc4-testnet](https://github.com/crypto-org-chain/cronos/releases/tag/v1.0.0-rc4) |

After it reaches the block height 6134000, update the binary to cronos_1.0.0-rc4-testnet;
Start the node again

| -| `6969900` | [cronos\_1.0.2-testnet](https://github.com/crypto-org-chain/cronos/releases/tag/v1.0.2) |

After it reaches the block height 6969900, update the binary to cronos_1.0.2-rc4-testnet;
Start the node again

| +
Block HeightBinary VersionInstruction
~ 1553700cronos_0.6.0-testnet

Follow Step 1 to Step 3 and start the node with the older binary version v0.6.0;

Sync-up with the blockchain until it reaches the target upgrade block height 1553700;


Please note that panic: UPGRADE "v0.7.0" NEEDED at height: 1553700 is the expected error message when we hit that block.

1553700cronos_0.7.0-rc1-testnet

After it reaches the block height 1553700, update the binary to cronos_0.7.0-rc1-testnet;

Then update the default ~/.cronos/config/app.toml(given there are some new parameters introduced in the upgrade), either by manually replacing the local app.toml with this new app.toml, or by: $ curl https://raw.githubusercontent.com/crypto-org-chain/cronos-testnets/main/cronostestnet_338-3/app.toml > ~/.cronos/config/app.toml

Then continue to sync from block 1553700;

1869000cronos_0.7.0-rc2-testnet

After it reaches the block height 1869000, update the binary to cronos_0.7.0-rc2-testnet;


Start the node again and continue to sync from block1869000;

2483600cronos_0.7.0-rc3-testnet

After it reaches the block height 2483600, update the binary to cronos_0.7.0-rc3-testnet;

Start the node again

4904100cronos_0.8.1-testnet

After it reaches the block height 4904100, update the binary to cronos_0.8.1-testnet;

Start the node again

5138880cronos_0.9.0-beta2-testnet

After it reaches the block height 5138880, update the binary to cronos_0.9.0-beta2-testnet;

Start the node again

6134000cronos_1.0.0-rc4-testnetAfter it reaches the block height 6134000, update the binary to cronos_1.0.0-rc4-testnet;
Start the node again
6969900cronos_1.0.2-testnetAfter it reaches the block height 6969900, update the binary to cronos_1.0.2-rc4-testnet;
Start the node again
14046800cronos_1.1.0-rc0-testnetAfter it reaches the block height 14046800, update the binary to cronos_1.1.0-rc0-testnet;
Start the node again
17382000cronos-v1.1.0-rc2-testnetAfter it reaches the block height 17382000, update the binary to cronos-v1.1.0-rc2-testnet;
Start the node again
20142500 cronos_1.1.0-rc4-testnetAfter it reaches the block height 20142500, update the binary to cronos_1.1.0-rc4-testnet;
Start the node again
20142500 cronos_1.2.0-rc0-testnetAfter it reaches the block height 22200000, update the binary tocronos_1.2.0-rc0-testnet;
Start the node again
22200000cronos_1.3.0-rc1-testnetAfter it reaches the block height 22200000, update the binary to cronos_1.3.0-rc1-testnet;
Start the node again
### Step 1. Get the Cronos Testnet binary