|
| 1 | +# Upgrade Guide v7.0 |
| 2 | + |
| 3 | +This document provides guidelines for node operators upgrading from Regen Ledger v6.x.x to v7.0. For a general overview of the upgrade process, please refer to [Upgrade Overview](README.md). |
| 4 | + |
| 5 | +## Upgrade Info |
| 6 | + |
| 7 | +### Regen Ledger v7.0 |
| 8 | + |
| 9 | +- [Release Notes](https://github.com/regen-network/regen-ledger/releases/tag/v7.0.0) |
| 10 | + |
| 11 | +### Regen Mainnet |
| 12 | + |
| 13 | +- Upgrade Height: `25303838` |
| 14 | + |
| 15 | +## Upgrade Guidelines |
| 16 | + |
| 17 | +### Update Go |
| 18 | + |
| 19 | +**Go `1.23` or later is required.** |
| 20 | + |
| 21 | +For available downloads, see [Go Downloads](https://go.dev/dl/). |
| 22 | + |
| 23 | + |
| 24 | +### Option 1: Using Cosmovisor |
| 25 | + |
| 26 | +**Cosmovisor `v1.0` or later is required.** |
| 27 | + |
| 28 | +The following instructions assume the `cosmovisor` binary is already installed and `cosmovisor` is set up as a systemd service. If this is not the case, please refer to [Using Cosmovisor](../get-started/using-cosmovisor.md) for instructions on how to install and set up `cosmovisor`. |
| 29 | + |
| 30 | +::: warning Auto-Download Not Recommended |
| 31 | +Cosmovisor provides an auto-download option that prevents the need for the following steps in preparing for the upgrade. Although available to validators, this feature should only be used for non-validator nodes and validators should build the binary from source. |
| 32 | +::: |
| 33 | + |
| 34 | +Build the upgrade binary (`v7.0.0`) from source: |
| 35 | + |
| 36 | +```bash |
| 37 | +cd regen-ledger |
| 38 | +git fetch --tags |
| 39 | +git checkout v7.0.0 |
| 40 | +make build |
| 41 | +``` |
| 42 | + |
| 43 | +Ensure the `regen` binary has been built: |
| 44 | + |
| 45 | +```bash |
| 46 | +./build/regen version |
| 47 | +``` |
| 48 | + |
| 49 | +You should see the following: |
| 50 | + |
| 51 | +```bash |
| 52 | +v7.0.0 |
| 53 | +``` |
| 54 | + |
| 55 | +Create a `v7_0` directory and copy the upgrade binary (`v7.0.0`) to the directory: |
| 56 | + |
| 57 | +```bash |
| 58 | +mkdir -p $HOME/.regen/cosmovisor/upgrades/v7_0/bin |
| 59 | +cp ./build/regen $HOME/.regen/cosmovisor/upgrades/v7_0/bin |
| 60 | +``` |
| 61 | +Ensure the right `regen` binary has been placed in the directory: |
| 62 | + |
| 63 | +```bash |
| 64 | +$HOME/.regen/cosmovisor/upgrades/v7_0/bin/regen version |
| 65 | +``` |
| 66 | + |
| 67 | +You should see the following: |
| 68 | + |
| 69 | +```bash |
| 70 | +v7.0.0 |
| 71 | +``` |
| 72 | + |
| 73 | +At the proposed block height, `cosmovisor` will automatically stop the current binary (`v6.x.x`), set the upgrade binary as the current binary (`v7.0.0`), and then (depending on the cosmovisor settings) perform a backup and restart the node. |
| 74 | + |
| 75 | +### Option 2: Without Cosmovisor |
| 76 | + |
| 77 | +Using `cosmovisor` to perform the upgrade is not required. Node operators also have the option to manually update the `regen` binary at the time of the upgrade. |
| 78 | + |
| 79 | +First Build the upgrade binary (`v7.0.0`) from source: |
| 80 | + |
| 81 | +```bash |
| 82 | +cd regen-ledger |
| 83 | +git fetch --tags |
| 84 | +git checkout v7.0.0 |
| 85 | +make install |
| 86 | +``` |
| 87 | + |
| 88 | +Ensure the `regen` binary has been updated: |
| 89 | + |
| 90 | +```bash |
| 91 | +regen version |
| 92 | +``` |
| 93 | + |
| 94 | +You should see the following: |
| 95 | + |
| 96 | +```bash |
| 97 | +v7.0.0 |
| 98 | +``` |
| 99 | + |
| 100 | +When the chain halts at the proposed upgrade height, stop the current process running `regen`. |
| 101 | + |
| 102 | +Restart the process running `regen`. |
0 commit comments