Skip to content

Commit

Permalink
update upgrade doc for v1.4.0
Browse files Browse the repository at this point in the history
  • Loading branch information
sheldon committed Nov 15, 2022
1 parent e489787 commit ee9e7c0
Showing 1 changed file with 55 additions and 0 deletions.
55 changes: 55 additions & 0 deletions upgrade/v1.4.0.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,55 @@
# IRIS Hub Upgrade v1.4.0

## Upgrade Proposal

We are prepared to upgrade the IRIS Hub based upon

- Version: `v1.4.0`
- Commit hash: `ec747ae214bda191fe5aeeceefdfb590be802ec9`;
- Chain Halt at Block Height: `17618523`;

## Upgrade Process

### 1. Vote

```bash
iris tx gov vote <proposal-id> <yes|no|no_with_veto|abstain> --chain-id irishub-1 --fees 0.3iris --from <MyWallet>
```

### 2. Upgrade Nodes

**Note:**⚠️ This upgrade involves data migration, and the hardware configuration of the node needs to be temporarily increased:
1. CPU: >= 4C
2. Memory: >= 12G

If the **Upgrade Proposal** successfully passes, the IRIS Hub will be halted automatically at around UTC `2022-11-25 05:30:00Z`, so we can upgrade all of the irishub nodes right away.

**Note: All nodes have to be upgraded, whether it is a validator node, a seed node or a full node.**

The specific steps are as follows:

```bash
# 1. Compile and install the new version, go 1.18+ is required
git clone https://github.com/irisnet/irishub
cd irishub && git checkout v1.4.0
make install

# 2. Check the version number
iris version --long
name: iris
server_name: iris
version: 1.4.0
commit:
build_tags: netgo,ledger
go: go version go1.18 darwin/amd64

# 3. Close the old software
kill -9 <iris-pid>

# 4. Restart
iris start --home=<path-to-your-home>
```

### 3. Wait for Blocks

When the voting power of validators that have completed the upgrade exceeds 67%, irishub can resume producing blocks, and the upgrade is completed.

0 comments on commit ee9e7c0

Please sign in to comment.