upgrade release testnet to v11 (cosmos#2665)

chillyvee · Jul 25, 2023 · 0a4fb3c · 0a4fb3c
1 parent cdc5089
commit 0a4fb3c
Showing 1 changed file with 19 additions and 19 deletions.
diff --git a/docs/hub-tutorials/join-testnet.md b/docs/hub-tutorials/join-testnet.md
@@ -7,25 +7,27 @@ title: Joining Testnet
 
 This tutorial will provide all necessary instructions for joining the current public testnet. If you're interested in more advanced configuration and synchronization options, see [Join Mainnet](./join-mainnet.md) for a detailed walkthrough.
 
-* Current Version: v9-Lambda
+* Current Version: v10
 * Chain ID: `theta-testnet-001`
 
 ## Background
 
-The Cosmos Hub Public Testnet is currently running Gaia v8. Visit the [testnet explorer](https://explorer.theta-testnet.polypore.xyz/) to view all on-chain activity.
+The Cosmos Hub Public Testnet is currently running Gaia v10. Visit the [testnet explorer](https://explorer.theta-testnet.polypore.xyz/) to view all on-chain activity.
 
 For those who just need instructions on performing the upgrade, see the [Upgrading Your Node](#upgrading-your-node) section.
 
 ### Version History
 
 The table below shows all past and upcoming versions of the public testnet.
 
-|  Release   | Upgrade Block Height |    Upgrade Date     |
-|:----------:|:--------------------:|:-------------------:|
-| v9.0.0-rc3 |      14,476,206      |     2023-02-08      |
-| v8.0.0-rc3 |      14,175,595      |     2023-01-20      |
-| v7.0.0-rc0 |      9,283,650       |     2022-03-17      |
-|   v6.0.0   |       Genesis        | Launched 2022-03-10 |
+|   Release   | Upgrade Block Height |    Upgrade Date     |
+| :---------: | :------------------: | :-----------------: |
+| v11.0.0-rc0 |      17,107,825      |     2023-07-26      |
+| v10.0.0-rc0 |      16,117,530      |     2023-05-24      |
+| v9.0.0-rc3  |      14,476,206      |     2023-02-08      |
+| v8.0.0-rc3  |      14,175,595      |     2023-01-20      |
+| v7.0.0-rc0  |      9,283,650       |     2022-03-17      |
+|   v6.0.0    |       Genesis        | Launched 2022-03-10 |
 
 See the [Gaia release page](https://github.com/cosmos/gaia/releases) for details on each release.
 
@@ -40,7 +42,7 @@ We offer three ways to set up a node in the testnet:
 * Step-by-step instructions
   * The rest of this document provides a step-by-step walkthrough for setting up a testnet node.
 
-We recommend running public testnet nodes on machines with at least 8 cores, 16GB of RAM, and 300GB of disk space.
+We recommend running public testnet nodes on machines with at least 8 cores, 32GB of RAM, and 300GB of disk space.
 
 ## Sync Options
 
@@ -70,7 +72,7 @@ export PATH=$PATH:/usr/local/go/bin
 
 ### Installation & Configuration
 
-You will need to install and configure the Gaia binary using the script below. The Cosmos Hub Public Testnet is running Gaia [`v9.0.0-rc6`](https://github.com/cosmos/gaia/releases/tag/v9.0.0-rc6).
+You will need to install and configure the Gaia binary using the script below. The Cosmos Hub Public Testnet is running Gaia [`v10.0.2`](https://github.com/cosmos/gaia/releases/tag/v10.0.2).
 
 * For up-to-date endpoints like seeds and state sync RPC servers, visit the [testnets repository](https://github.com/cosmos/testnets/tree/master/public).
 
@@ -80,7 +82,7 @@ cd $HOME
 git clone https://github.com/cosmos/gaia
 cd gaia
 # To sync from genesis, comment out the next line.
-git checkout v9.0.0-rc6
+git checkout v10.0.2
 # To sync from genesis, uncomment the next line and skip the State Sync Setup section.
 # git checkout v6.0.4
 make install
@@ -232,7 +234,7 @@ There are three ways you can update the binary:
 
 The instructions below are for option 2. For more information on auto-download with Cosmovisor, see the relevant [documentation](https://github.com/cosmos/cosmos-sdk/tree/main/tools/cosmovisor#auto-download) in the Cosmos SDK repo.
 
-If the environment variable `DAEMON_ALLOW_DOWNLOAD_BINARIES` is set to `false`, Cosmovisor will look for the new binary in a folder that matches the name of the upgrade specified in the software upgrade proposal. For the `v9-Lambda` upgrade, the expected folder structure would look as follows:
+If the environment variable `DAEMON_ALLOW_DOWNLOAD_BINARIES` is set to `false`, Cosmovisor will look for the new binary in a folder that matches the name of the upgrade specified in the software upgrade proposal. For the `v11` upgrade, the expected folder structure would look as follows:
 
 ```shell
 .gaia
@@ -242,27 +244,25 @@ If the environment variable `DAEMON_ALLOW_DOWNLOAD_BINARIES` is set to `false`,
     │   └── bin
     |       └── gaiad
     └── upgrades
-        └── v9-lambda
+        └── v11
             └── bin
                 └── gaiad
 ```
 
-> Note: for Cosmovisor v1.0.0, the upgrade name folder is not lowercased (use `cosmovisor/upgrades/v9-Lambda/bin` instead)
-
 Prepare the upgrade directory
 ```
-mkdir -p ~/.gaia/cosmovisor/upgrades/v8-rho/bin
+mkdir -p ~/.gaia/cosmovisor/upgrades/v11/bin
 ```
 
 Download and install the new binary version.
 ```
 cd $HOME/gaia
 git pull
-git checkout v8.0.0
+git checkout v11.0.0-rc0
 make install
 
-# Copy the new binary to the v8-Rho upgrade directory
-cp ~/go/bin/gaiad ~/.gaia/cosmovisor/upgrades/v9-lambda/bin/gaiad
+# Copy the new binary to the v11 upgrade directory
+cp ~/go/bin/gaiad ~/.gaia/cosmovisor/upgrades/v11/bin/gaiad
 ```
 
 When the upgrade height is reached, Cosmovisor will stop the gaiad binary, copy the new binary to the `current/bin` folder and restart. After a few minutes, the node should start syncing blocks using the new binary.