Try   HackMD

Namada SE 2 Restart 2

Namada SE 2 Restart 1

  • TLDR; There was a bug that reordered ABCI messages.

v0.31.2 has a bug that causes jailing operations to be applied in a non-determinstic order. This was caught uniquely due to the bug in v0.31.1, which caused a number of random jailing events.

The current network progressed to block 8671 which resulted in committing a broken state. In order to fix it a majority of validator voting power must upgrade to v0.31.4 and resync.

Steps to upgrade

Image Not Showing Possible Reasons
  • The image file may be corrupted
  • The server hosting the image is unavailable
  • The image path is incorrect
  • The image format is not supported
Learn More →
ABOVE ALL ELSE, DON'T DELETE THE KEYS OR THE VALIDATOR STATE.
Image Not Showing Possible Reasons
  • The image file may be corrupted
  • The server hosting the image is unavailable
  • The image path is incorrect
  • The image format is not supported
Learn More →

I would suggest the following steps to upgrade:

  1. Stop the validator node
  2. Upgrade to v0.31.4
  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 your p2p stack according to this message: https://discord.com/channels/833618405537218590/1192974425423892550/1206615315618857040
  6. Modify the consensus timeouts in order to speed up the sync
    • vim <base_dir>/shielded-expedition.88f17d1d14/config.toml
      • timeout_propose = "3000ms"
      • timeout_propose_delta = "500ms" (used to be "500ms")
      • timeout_prevote = "1000ms"
      • timeout_prevote_delta = "500ms" (used to be "500ms")
      • timeout_precommit = "1000ms"
      • timeout_precommit_delta = "0ms" (used to be "500ms")
      • timeout_commit = "10000ms"
  7. Start the node and sync

Restart tracking

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.
Last changed by 
 
Heliax
2017

Read more

Namada SE 2 Patch 4

Namada SE 2 Patch 2

Feb 22, 2024
Namada SE 2 Restart 1

There was a bug that was introduced in version v0.31.1. v0.31.2 has been released, which fixes the bug.

Feb 12, 2024
An autonomous ecologist's guide to Namada & Anoma

aka

Jul 16, 2023
On Benchmarking Zero Knowledge Proof Systems.

In the Zero Knowledge sphere, there exists a plethora of Zero Knowledge Systems and languages. From zk-SNARK languages like Zokrates, Leo, and Vamp-IR; to STARK machines like Triton VM, Miden VM, and RISC Zero. It is difficult in the current landscape to make an informed decision about which system fits their use case best. This benchmarking endeavor seeks to alleviate these issues by readily making performance numbers between the various systems be known and provide an easy way to compare the same program across languages and systems. Currently, the amount of backends and programs that are compared is limited. However, community contributions should amplify the value provided by the benchmarking project. In particular, the benchmarking results and programs will be most useful to five kinds of individuals: Users who are building an application with a Zero Knowledge System. Compiler writers who wish to target a Zero Knowledge System. Users who have a choice of the Zero Knowledge System in their application. Zero Knowledge System implementers who wish to know optimization points.

Oct 25, 2022
Read more from Heliax
Published on HackMD