Upgrades

This page covers all installation steps required by various upgrades to testnets.

Latest Upgrade

19/05/2023 public-testnet-8 hot-fix

Due to some issues with our mempool validation, the testnet halted starting at block height 8073. We fixed this issue and released a hot-fix version to a subset of the validators. This was sufficient to keep the testnet going. It did require some validators to resync the testnet.

Latest Testnet

17/05/2023 public-testnet-8

The testnet launches on 17/05/2023 at 17:00 UTC with the genesis validators from public-testnet-8. It launches with version v0.15.3 and chain-id public-testnet-8.0.b92ef72b820. If your genesis transaction is contained in this folder, you are one of the genesis validators. In order for the testnet to come online, at least 2/3 of those validators need to be online.

The installation docs are updated and can be found here. The running docs for validators/fullnodes can be found here.

Previous upgrades:

24/04/2023 public-testnet-7 (offline)

The testnet launches on 24/04/2023 at 17:00 UTC with the genesis validators from public-testnet-7. It launches with version v0.15.1

The intended fix to solve the storage issue was only partially solved. This led to v0.15.3 which intended to fix these issues.

29/03/2023 public-testnet-6 (offline)

The testnet launches on 29/03/2023 at 17:00 UTC with the genesis validators from public-testnet-6. It launches with version v0.14.3 and chain-id public-testnet-6.0.a0266444b06. If your genesis transaction is contained in this folder, you are one of the genesis validators. In order for the testnet to come online, at least 2/3 of those validators need to be online.

The installation docs are updated and can be found here. The running docs for validators/fullnodes can be found here.

13/02/2023 public-testnet-3

On 09/02/2023 the Namada chain public-testnet-3 halted due to a bug in the Proof of Stake implementation when handling an edge case. Over the weekend, the team were able to fix and test a new patch that resolves the issue at hand. On 13/02/2023 11:30 UTC, we were able to recover the network by having internal validators upgrade to the new patch. We are now calling on validators to upgrade to the new testnet as well, which will allow you to interact with the recovered chain.

Upgrading

  1. Begin by stopping all instances of the namada node
killall namadan
  1. Build the new tag (or download the binaries here)
cd namada
export NAMADA_TAG=v0.13.4
make build-release
  1. Copy the new binaries to path. More in depth instructions can be found at here
  2. Once this has been completed, the node must tesync from genesis (see below)

How to resync from genesis:

  1. As a precautionary measure, make a backup of your pregenesis keys
mkdir backup-pregenesis && cp -r .namada/pre-genesis backup-pregenesis/
  1. Delete the relevant folder in .namada
rm -r .namada/public-testnet-3.0.81edd4d6eb6
rm .namada/public-testnet-3.0.81edd4d6eb6.toml

WARNING: Do not delete the entire .namada folder, as it contains your pre-genesis keys. If this is accidentally done, you will have to copy over the backup-pregenesis file. See these instructions for more details 3. Rejoin the network

export CHAIN_ID="public-testnet-3.0.81edd4d6eb6"
namada client utils join-network \
--chain-id $CHAIN_ID --genesis-validator $ALIAS
  1. Run the node. One can simply run the ledger again using the familiar command
  NAMADA_TM_STDOUT=true namada node ledger run

Please reach out with any questions if you have any. This upgrade can be done asynchronously, but if you wish to continue validating the chain and testing our features, you must execute the above steps.

Hotfix for Testnet public-testnet-2.1.4014f207f6d

27/01/2023

The hotfixed testnet ran during the week, when a strange bug caused the network to stall. The core team spent 1 week investigating the cause of the bug, and the result they found was quite interesting. If you are curious about the specific details of the bug, please have a read through Ray's blog post here.

25/01/2023

At around 06:15 UTC 25/01/2023, a validator with very little stake was scheduled to become part of the active validator set. From this tx, we discovered a conversion bug between the Namada state machine and Tendermint, which lead to a crash in the node. A patch was released v0.13.3 in order to deal with this issue.

23/01/2023

A new testnet was released before the fortnightly testnet release schedule due to the below hardfork not working as intended. Follow the steps in setting up a new testnet

Hardfork v0.13.1

This hardfork is set to be instantiated at block height 37370, which is predicted to occur at around 17.00 UTC on 18/01/2023.

Requirements to do before 17.00 UTC 18/01/2023

In order to install this upgrade, a user or validator must

  1. Download the binaries or install them from source

  2. Ensure the versions are correct, such that <PATH_TO_BINARY>/namada --version is v0.13.1-hardfork

  3. Interrupt the namada ledger by the interrupt command ^C

  4. Install the binaries onto $PATH (this depends on your machine). This must be done after interrupting the ledger, as otherwise an error is likely to be thrown.

  5. As soon as possible, restart the ledger by running NAMADA_TM_STDOUT=true namada node ledger run

The ledger will then update correctly at the correct height. In order to ensure a smooth fork, please do this as soon as possible.