Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

docs: release testnet upgraded to v11 #2668

Merged
merged 2 commits into from
Aug 11, 2023
Merged

docs: release testnet upgraded to v11 #2668

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
66255a1
testnet upgraded to v11
dasanchez Jul 26, 2023
260a555
replace v11.0.0-rc0 with v11.0.0
dasanchez Aug 9, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 11 additions & 10 deletions docs/hub-tutorials/join-testnet.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,12 +7,12 @@ 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: v10
* Current Version: v11
* Chain ID: `theta-testnet-001`

## Background

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.
The Cosmos Hub Public Testnet is currently running Gaia v11. 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.

Expand All @@ -22,6 +22,7 @@ The table below shows all past and upcoming versions of the public testnet.

| Release | Upgrade Block Height | Upgrade Date |
| :---------: | :------------------: | :-----------------: |
| v12.0.0-rc0 | TBA | TBA |
| 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 |
Expand Down Expand Up @@ -72,7 +73,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 [`v10.0.2`](https://github.com/cosmos/gaia/releases/tag/v10.0.2).
You will need to install and configure the Gaia binary using the script below. The Cosmos Hub Public Testnet is running Gaia [`v11.0.0`](https://github.com/cosmos/gaia/releases/tag/v11.0.0).

* For up-to-date endpoints like seeds and state sync RPC servers, visit the [testnets repository](https://github.com/cosmos/testnets/tree/master/public).

Expand All @@ -82,7 +83,7 @@ cd $HOME
git clone https://github.com/cosmos/gaia
cd gaia
# To sync from genesis, comment out the next line.
git checkout v10.0.2
git checkout v11.0.0
# To sync from genesis, uncomment the next line and skip the State Sync Setup section.
# git checkout v6.0.4
make install
Expand Down Expand Up @@ -234,7 +235,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 `v11` 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 `v12` upgrade, the expected folder structure would look as follows:

```shell
.gaia
Expand All @@ -244,25 +245,25 @@ If the environment variable `DAEMON_ALLOW_DOWNLOAD_BINARIES` is set to `false`,
│ └── bin
| └── gaiad
└── upgrades
└── v11
└── v12
└── bin
└── gaiad
```

Prepare the upgrade directory
```
mkdir -p ~/.gaia/cosmovisor/upgrades/v11/bin
mkdir -p ~/.gaia/cosmovisor/upgrades/v12/bin
```

Download and install the new binary version.
```
cd $HOME/gaia
git pull
git checkout v11.0.0-rc0
git checkout v12.0.0-rc0
make install

# Copy the new binary to the v11 upgrade directory
cp ~/go/bin/gaiad ~/.gaia/cosmovisor/upgrades/v11/bin/gaiad
# Copy the new binary to the v12 upgrade directory
cp ~/go/bin/gaiad ~/.gaia/cosmovisor/upgrades/v12/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.