v7.0.2

Full Changelog: v7.0.1...v7.0.2

v7.0.0

What's Changed

What's Changed

• refactor: migrate crosschain keeper by @kingpinXD in #829
• docs(readme): fix typos by @omahs in #811
• feat: ci - Rename old A2 Actions by @billyyang423 in #854
• chore: update CODEOWNERS by @lumtis in #870
• fix: refactor: use temporary context for cleaner error handling by @brewmaster012 in #845
• chore: remove config.yml by @lumtis in #875
• refactor: simplify code generated by Ignite CLI by @lumtis in #850
• fix: set inbound finalized height for cctx by @kingpinXD in #886
• fix: SetLastObserverCount during genesis by @kingpinXD in #885
• feat: enable nonce-mark UTXO check and outTx Vin check by @ws4charlie in #847
• fix: removed nonce and persistence of includedTx by @ws4charlie in #893

New Contributors

• @omahs made their first contribution in #811

Full Changelog: v6.0.1...v7.0.0

v6.2.0

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.1.0...v6.2.0

v6.1.0

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

v6.0.1

What's Changed

• fix: V5.0.4 patch by @kevinssgh in #844

Full Changelog: v6.0.0...v6.0.1

v6.0.0

What's Changed

• fix: ci - fixed inputs and increased restart time to 90 seconds per region by @CharlieMc0 in #821
• feat: zeta utils by @kingpinXD in #804
• refactor: typed events by @kingpinXD in #803
• chore: Remove node-operations-athens3.yml by @billyyang423 in #827
• feat: WIP - Post Blame data from TSS keysign response by @kevinssgh in #833
• fix: avoid setting pending nonce low backwards by @brewmaster012 in #823
• feat: defensive: bitcoin deduplication via simulating nonce by @brewmaster012 in #812
• fix: remove SetCrossChainTx() at the first ballot creation time by @brewmaster012 in #837

Full Changelog: v5.0.2...v6.0.0

v5.0.4

Full Changelog: v5.0.3...v5.0.4

v5.0.3

Full Changelog: v5.0.2...v5.0.3

Fixed a bug that causes pending cctx to be exposed to wrong chains in the GetAllPendingCctx() RPC method

v5.0.2

What's Changed

• fix: Hot fix v5.0.2 by @kevinssgh in #822

Full Changelog: v5.0.0...v5.0.2

v5.0.1

Full Changelog: v5.0.0...v5.0.1