Namada SE 2 Patch 4

Namada SE 2 Patch 3

• TLDR; There was a bug that returned non-determinstically ordered validator set updates.

v0.31.5 has a bug where the state machine returns an incorrect validator set update to the consensus machine.

The current network has progressed to block 42850, which halted due to the aformentioned problem. In order to fix it a majority of validator voting power must upgrade to v0.31.6.
In order to restart the network 2/3+1 of voting power needs to sync the chain from scratch.

Steps to upgrade

ABOVE ALL ELSE, DON'T DELETE THE KEYS OR THE VALIDATOR STATE.

I would suggest the following steps to upgrade:

1. Stop the validator node
2. Upgrade to v0.31.6
3. Initialize your validator from scratch by running join-network again (same steps as before) but on a new base directory
4. [Important] Move over whatever double-sign protection you use (<chain_id>/cometbft/data/priv_validator_state.json) to the new directory
5. Modify the consensus timeouts in order to speed up the sync
   • vim <base_dir>/shielded-expedition.88f17d1d14/config.toml
     • timeout_precommit_delta = "0ms" (used to be "500ms")
6. Start the node and sync

Restart tracking

• Please add your status under the column "Restart 5" on the Shielded Expedition Restart Tracker we need at least 2/3 of the voting power.

Notes

• Coordinate with the other validators and voting power on Discord and help each other.
• Make sure to change the config.toml in <chain_id>/config.toml and not <chain_id>/cometbft/config.toml - the latter gets overriden
• No need to change the .masp-params.
• If you have peering issues, please check the seeds and peers here