Skip to content

Commit

Permalink
GITBOOK-275: Add More Cronos Evm Testnet Updates Info
Browse files Browse the repository at this point in the history
  • Loading branch information
@aw126 @gitbook-bot
aw126 authored and gitbook-bot committed Sep 16, 2024
1 parent a7b1fbc commit 780fdc6
Showing 1 changed file with 5 additions and 14 deletions.
19 changes: 5 additions & 14 deletions for-node-hosts/running-nodes/cronos-testnet.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -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) | <p>Follow <a href="cronos-testnet.md#step-1-get-the-cronos-testnet-binary">Step 1</a> to <a href="cronos-testnet.md#step-3-run-everything">Step 3</a> and start the node with the older binary version <code>v0.6.0</code>;<br></p><p>Sync-up with the blockchain until it reaches the target upgrade block height <code>1553700</code>;</p><p><br><em>Please note that <code>panic: UPGRADE "v0.7.0" NEEDED at height: 1553700</code> is the expected error message when we hit that block.</em></p> |
| `1553700` | [cronos\_0.7.0-rc1-testnet](https://github.com/crypto-org-chain/cronos/releases/tag/v0.7.0-rc1) | <p>After it reaches the block height <code>1553700</code>, update the binary to <a href="https://github.com/crypto-org-chain/cronos/releases/tag/v0.7.0-rc1">cronos_0.7.0-rc1-testnet</a>;<br></p><p>Then update the default <code>~/.cronos/config/app.toml</code>(given there are some new parameters introduced in the upgrade), either by manually replacing the local <code>app.toml</code> with <a href="https://raw.githubusercontent.com/crypto-org-chain/cronos-testnets/main/cronostestnet_338-3/app.toml">this new app.toml</a>, or by: <code>$ curl https://raw.githubusercontent.com/crypto-org-chain/cronos-testnets/main/cronostestnet_338-3/app.toml > ~/.cronos/config/app.toml</code><br></p><p>Then continue to sync from block <code>1553700</code>;</p> |
| `1869000` | [cronos\_0.7.0-rc2-testnet](https://github.com/crypto-org-chain/cronos/releases/tag/v0.7.0-rc2) | <p>After it reaches the block height <code>1869000</code>, update the binary to <a href="https://github.com/crypto-org-chain/cronos/releases/tag/v0.7.0-rc2">cronos_0.7.0-rc2-testnet</a>;</p><p><br>Start the node again and continue to sync from block<code>1869000</code>;</p> |
| `2483600` | [cronos\_0.7.0-rc3-testnet](https://github.com/crypto-org-chain/cronos/releases/tag/v0.7.0-rc3) | <p>After it reaches the block height <code>2483600</code>, update the binary to <a href="https://github.com/crypto-org-chain/cronos/releases/tag/v0.7.0-rc3">cronos_0.7.0-rc3-testnet</a>;</p><p>Start the node again</p> |
| `4904100` | [cronos\_0.8.1-testnet](https://github.com/crypto-org-chain/cronos/releases/tag/v0.8.1) | <p>After it reaches the block height <code>4904100</code>, update the binary to <a href="https://github.com/crypto-org-chain/cronos/releases/tag/v0.8.1">cronos_0.8.1-testnet</a>;</p><p>Start the node again</p> |
| `5138880` | [cronos\_0.9.0-beta2-testnet](https://github.com/crypto-org-chain/cronos/releases/tag/v0.9.0-beta2) | <p>After it reaches the block height <code>5138880</code>, update the binary to <a href="https://github.com/crypto-org-chain/cronos/releases/tag/v0.9.0-beta2">cronos_0.9.0-beta2-testnet</a>;</p><p>Start the node again</p> |
| `6134000` | [cronos\_1.0.0-rc4-testnet](https://github.com/crypto-org-chain/cronos/releases/tag/v1.0.0-rc4) | <p>After it reaches the block height <code>6134000</code>, update the binary to <a href="https://github.com/crypto-org-chain/cronos/releases/tag/v1.0.0-rc4">cronos_1.0.0-rc4-testnet</a>; <br>Start the node again</p> |
| `6969900` | [cronos\_1.0.2-testnet](https://github.com/crypto-org-chain/cronos/releases/tag/v1.0.2) | <p>After it reaches the block height <code>6969900</code>, update the binary to <a href="https://github.com/crypto-org-chain/cronos/releases/tag/v1.0.2">cronos_1.0.2-rc4-testnet</a>; <br>Start the node again</p> |
<table><thead><tr><th width="249.33333333333331">Block Height</th><th>Binary Version</th><th>Instruction</th></tr></thead><tbody><tr><td>~ <code>1553700</code></td><td><a href="https://github.com/crypto-org-chain/cronos/releases/tag/v0.6.0-testnet">cronos_0.6.0-testnet</a></td><td><p>Follow <a href="cronos-testnet.md#step-1-get-the-cronos-testnet-binary">Step 1</a> to <a href="cronos-testnet.md#step-3-run-everything">Step 3</a> and start the node with the older binary version <code>v0.6.0</code>;<br></p><p>Sync-up with the blockchain until it reaches the target upgrade block height <code>1553700</code>;</p><p><br><em>Please note that <code>panic: UPGRADE "v0.7.0" NEEDED at height: 1553700</code> is the expected error message when we hit that block.</em></p></td></tr><tr><td><code>1553700</code></td><td><a href="https://github.com/crypto-org-chain/cronos/releases/tag/v0.7.0-rc1">cronos_0.7.0-rc1-testnet</a></td><td><p>After it reaches the block height <code>1553700</code>, update the binary to <a href="https://github.com/crypto-org-chain/cronos/releases/tag/v0.7.0-rc1">cronos_0.7.0-rc1-testnet</a>;<br></p><p>Then update the default <code>~/.cronos/config/app.toml</code>(given there are some new parameters introduced in the upgrade), either by manually replacing the local <code>app.toml</code> with <a href="https://raw.githubusercontent.com/crypto-org-chain/cronos-testnets/main/cronostestnet_338-3/app.toml">this new app.toml</a>, or by: <code>$ curl https://raw.githubusercontent.com/crypto-org-chain/cronos-testnets/main/cronostestnet_338-3/app.toml > ~/.cronos/config/app.toml</code><br></p><p>Then continue to sync from block <code>1553700</code>;</p></td></tr><tr><td><code>1869000</code></td><td><a href="https://github.com/crypto-org-chain/cronos/releases/tag/v0.7.0-rc2">cronos_0.7.0-rc2-testnet</a></td><td><p>After it reaches the block height <code>1869000</code>, update the binary to <a href="https://github.com/crypto-org-chain/cronos/releases/tag/v0.7.0-rc2">cronos_0.7.0-rc2-testnet</a>;</p><p><br>Start the node again and continue to sync from block<code>1869000</code>;</p></td></tr><tr><td><code>2483600</code></td><td><a href="https://github.com/crypto-org-chain/cronos/releases/tag/v0.7.0-rc3">cronos_0.7.0-rc3-testnet</a></td><td><p>After it reaches the block height <code>2483600</code>, update the binary to <a href="https://github.com/crypto-org-chain/cronos/releases/tag/v0.7.0-rc3">cronos_0.7.0-rc3-testnet</a>;</p><p>Start the node again</p></td></tr><tr><td><code>4904100</code></td><td><a href="https://github.com/crypto-org-chain/cronos/releases/tag/v0.8.1">cronos_0.8.1-testnet</a></td><td><p>After it reaches the block height <code>4904100</code>, update the binary to <a href="https://github.com/crypto-org-chain/cronos/releases/tag/v0.8.1">cronos_0.8.1-testnet</a>;</p><p>Start the node again</p></td></tr><tr><td><code>5138880</code></td><td><a href="https://github.com/crypto-org-chain/cronos/releases/tag/v0.9.0-beta2">cronos_0.9.0-beta2-testnet</a></td><td><p>After it reaches the block height <code>5138880</code>, update the binary to <a href="https://github.com/crypto-org-chain/cronos/releases/tag/v0.9.0-beta2">cronos_0.9.0-beta2-testnet</a>;</p><p>Start the node again</p></td></tr><tr><td><code>6134000</code></td><td><a href="https://github.com/crypto-org-chain/cronos/releases/tag/v1.0.0-rc4">cronos_1.0.0-rc4-testnet</a></td><td>After it reaches the block height <code>6134000</code>, update the binary to <a href="https://github.com/crypto-org-chain/cronos/releases/tag/v1.0.0-rc4">cronos_1.0.0-rc4-testnet</a>; <br>Start the node again</td></tr><tr><td><code>6969900</code></td><td><a href="https://github.com/crypto-org-chain/cronos/releases/tag/v1.0.2">cronos_1.0.2-testnet</a></td><td>After it reaches the block height <code>6969900</code>, update the binary to <a href="https://github.com/crypto-org-chain/cronos/releases/tag/v1.0.2">cronos_1.0.2-rc4-testnet</a>; <br>Start the node again</td></tr><tr><td><code>14046800</code></td><td><a href="https://github.com/crypto-org-chain/cronos/releases/tag/v1.1.0-rc0">cronos_1.1.0-rc0-testnet</a></td><td>After it reaches the block height <code>14046800</code>, update the binary to <a href="https://github.com/crypto-org-chain/cronos/releases/tag/v1.1.0-rc0">cronos_1.1.0-rc0-testnet</a>; <br>Start the node again</td></tr><tr><td><code>17382000</code></td><td><a href="https://github.com/crypto-org-chain/cronos/releases/tag/v1.1.0-rc2">cronos-v1.1.0-rc2-testnet</a></td><td>After it reaches the block height <code>17382000</code>, update the binary to <a href="https://github.com/crypto-org-chain/cronos/releases/tag/v1.1.0-rc2">cronos-v1.1.0-rc2-testnet</a>; <br>Start the node again</td></tr><tr><td><code>20142500</code></td><td><a href="https://github.com/crypto-org-chain/cronos/releases/tag/v1.1.0-rc4"> cronos_1.1.0-rc4-testnet</a></td><td>After it reaches the block height <code>20142500</code>, update the binary to <a href="https://github.com/crypto-org-chain/cronos/releases/tag/v1.1.0-rc4">cronos_1.1.0-rc4-testnet</a>; <br>Start the node again</td></tr><tr><td><code>20142500</code></td><td><a href="https://github.com/crypto-org-chain/cronos/releases/tag/v1.2.0-rc0"> cronos_1.2.0-rc0-testnet</a></td><td>After it reaches the block height <code>22200000</code>, update the binary to<a href="https://github.com/crypto-org-chain/cronos/releases/tag/v1.2.0-rc0">cronos_1.2.0-rc0-testnet</a>;<br>Start the node again</td></tr><tr><td><code>22200000</code></td><td><a href="https://github.com/crypto-org-chain/cronos/releases/tag/v1.3.0-rc1">cronos_1.3.0-rc1-testnet</a></td><td>After it reaches the block height <code>22200000</code>, update the binary to <a href="https://github.com/crypto-org-chain/cronos/releases/tag/v1.3.0-rc1">cronos_1.3.0-rc1-testnet</a>;<br>Start the node again</td></tr></tbody></table>

### Step 1. Get the Cronos Testnet binary

Expand Down

0 comments on commit 780fdc6

Please sign in to comment.