Skip to content

Commit

Permalink
feat: v1.1.2 testnet upgrade (#1266)
Browse files Browse the repository at this point in the history
  • Loading branch information
benjamin852 authored Dec 11, 2024
1 parent 55c996a commit 1b564f6
Show file tree
Hide file tree
Showing 2 changed files with 62 additions and 1 deletion.
60 changes: 60 additions & 0 deletions src/content/docs/resources/testnet/upgrades/v112.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,60 @@
# Testnet upgrade: V1.1.2

import { Callout } from "/src/components/callout";

Instructions for the `2024-Dec-12` testnet upgrade to axelar-core `v1.1.2`.
Release can be found [here](https://github.com/axelarnetwork/axelar-core/releases/tag/v1.1.2)

Upgrade height `16665600` [countdown](https://www.mintscan.io/axelar-testnet/block/16665600)

## About the V1.1.2 upgrade
The `v1.1.2` upgrade is a non-consensus breaking patch release for `v1.1.x.` `v1.1.x.` Once live, it will enable the deployment of ITS Hub on testnet.

1. If you're a validator or have delegated to one, please vote for the upgrade proposal via


```bash
axelard tx gov vote 164 yes --from validator
```


2. Wait for the proposed upgrade block, `16665600`. Your node will panic at that block height with a log: `{"level":"error","module":"consensus","err":"UPGRADE \"v1.1.2\" NEEDED at height: ",`. Stop your node after chain halt.

```bash
pkill -f 'axelard start'
# Validators need to also stop vald/tofnd
pkill -f 'vald-start'
pkill -f tofnd
```

3. Backup the state:

```bash
cp -r ~/.axelar_testnet/.core/data ~/.axelar-lisbon-3-upgrade-1.1.2/.core/data
```

<Callout type="warning" emoji="⚠️">
Caution: If you backup the entire folder, `~/.axelar_testnet/.core`, that'll
also include your private keys (inside `config` and `keyring-file`
subfolders). That can be dangerous if anyone gets access to your backups. We
recommend backing up keys separately when you first create your node, and then
excluding them from any data backups.
</Callout>


4. Restart your `axelard` node with the new `v1.1.2` build.
5. If you're a validator also restart `vald` with `v1.1.2` and `tofnd` with `v1.0.1`.

Example using join scripts in [axelarate-community git repo](https://github.com/axelarnetwork/axelarate-community):



```bash
# in axelarate-community repo
git checkout main
git pull
KEYRING_PASSWORD="pw-1" ./scripts/node.sh -n testnet -a v1.1.2
# For validators, restart vald/tofnd
KEYRING_PASSWORD="pw-1" TOFND_PASSWORD="pw-2" ./scripts/validator-tools-host.sh -n testnet -a v1.1.2 -q v1.0.1
```

3 changes: 2 additions & 1 deletion src/upgrade-path-testnet.md
Original file line number Diff line number Diff line change
Expand Up @@ -27,4 +27,5 @@ layout: /src/layouts/None.astro
| [v0.33.2](/resources/testnet/upgrades/v33/) | 8528500 | 9462850 |
| [v0.34.3](/resources/testnet/upgrades/v34/) | 9462850 | 12017025 |
| [v0.35.3](/resources/testnet/upgrades/v35/) | 12017025 | 14625900 |
| [v1.0.0](/resources/testnet/upgrades/v11/) | 14625900 | N/A |
| [v1.0.0](/resources/testnet/upgrades/v11/) | 14625900 | 16665600 |
| [v1.1.2](/resources/testnet/upgrades/v112/) | 16665600 | N/A |

0 comments on commit 1b564f6

Please sign in to comment.