Skip to content

v6.1.0
Compare
Choose a tag to compare
@Auto-Zeta Auto-Zeta released this 27 Jul 21:11
· 708 commits to develop since this release
v6.1.0
37aee5b

We identified the cause of this chain halt incident: one validator was unbonded and removed from validators sets before its vote on block has been processed. This was an edge case of Cosmos SDK/Tendermint modules enabled by our mis-configured very short unbonding period parameter.

To recover from this, there are two bug fix releases of zetacored: V6.1.0 and V6.2.0, and two steps.

(for observer/keysigners only, you should stop the zetaclientd process before this step).
You should first restart your node with the new binary V6.1.0. This release avoids the panic by disabling distribution, slashing, and evidence module for one block. You will almost immediately see an error message like this: When we have enough validators upgraded to V6.1.0, your node will see an error message and pause:

ERR CONSENSUS FAILURE!!! err="pause at 946264; please revert back to v6.0.0 and restart" module=consensus server=node stack="goroutine 94 [running]:\nruntime/debug.Stack()\n\t/usr/local/go/src/runtime/debug/stack.go:24 +0x64\ngithub.com/tendermint/tendermint/consensus.
....

This error message is to be expected and an indication of successful deployment of V6.1.0.

Then you will need to replace your zetacored binary with version V6.2.0. Restart, and you might not see new blocks being produced right away. When enough validators have upgraded to V6.2.0, blocks will start being produced and this recovery is complete.
(zetaclientd can be started after this step).

Binaries are available in github repo: https://github.com/zeta-chain/node/tags
Alternatively you can checkout the tags and build your self.

Full Changelog: v6.0.0...v6.1.0

Assets 6
Loading