📣 Summary

v9.0.0 is the new stable mainnet release of the mezod chain client software.

This release enables the Triparty Bridge feature.

⚠️ This release incurs a mandatory upgrade of all Mezo Mainnet nodes that must occur on block 8194500 (ETA Monday, April 13th, around noon UTC). Upgrading the node before the mentioned block will cause a failure.

📝 Changelog

Fix metrics scraper panic by @lukasz-zimnoch in #628
Bump testnet validators and mainnet RPC to v8.0.0 by @lukasz-zimnoch in #627
RFC-6: Triparty BTC minting - follow-up by @pdyraga in #630
RFC-6: Always call the triparty minting callback by @pdyraga in #631
Support state_override in eth_call and eth_estimateGas by @pdyraga in #629
Triparty precompile functions for block delay and bridge limits by @pdyraga in #632
Triparty Keeper's CRUD by @pdyraga in #633
Wire up the triparty precompile with the keeper to request triparty bridging by @pdyraga in #634
Minimum bridgeable amount for triparty by @pdyraga in #636
Process triparty bridge requests in PreBlocker by @lukasz-zimnoch in #635
Triparty preblocker processing followup by @pdyraga in #638
Expose getTripartyCapacity and getTripartyTotalBTCMinted in the precompile by @pdyraga in #639
Rename incrementTripartySequenceTip to incrementTripartyRequestSequenceTip by @pdyraga in #640
Triparty bridging window capacity check by @tomaszslabon in #637
Explain why not checking precompile addresses for assets locked path by @pdyraga in #641
Add missing triparty state getters to precompile by @lukasz-zimnoch in #642
Set defaults for triparty bridge in upgrade handler by @pdyraga in #644
Triparty bridging genesis by @tomaszslabon in #643
Add missing genesis validation test cases for triparty bridge by @pdyraga in #647
Triparty bridge system tests by @lukasz-zimnoch in #646
Add per-controller triparty provenance, derive total from controllers by @lukasz-zimnoch in #648
Bump testnet nodes to v9.0.0-rc0 by @pdyraga in #645
Add v9.0.0 upgrade entries to docs by @lukasz-zimnoch in #649

Full Changelog: v8.0.0...v9.0.0

⚙️ Node setup

For guidance around node setup, please refer to the Validator Kit repository.

🔐 Signatures

We're providing two pieces of information for node providers and other interested parties:

The Docker image sha256sum
The Linux binary archive sha256 sum

Both hashes are signed by the development team and verifiable on Keybase. Our Keybase usernames are all associated our GitHub usernames.

Docker image

Image: mezo/mezod:v9.0.0.
sha256 sum: sha256:6cf22eeb6221043032e11bf03cc0c49e26c17c4d2ba2163e5d8cca4fb169c7e0

Signatures from the development team (verify these in the Keybase app):

@lukasz-zimnoch
BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zk90sDpX wIX07Cfy2Yz31Xq 8mliRvTpoVIDeBV VZiP1JZd9an53p4 LJ3mrlXq0YHjuW4 kGFjhINxSwuazYw 7vV4XfrizjQzRdc jOW2LoG2ZvDsG3H w6sYfmQWrn4lEkZ DkZNeFpu5NwCGZN uZvkGeFNuXHv8ok dc8Ueg5FKuUAIQo TgB6Ds3s69c8L90 C77v1BQdlvePCcH SgZMa19N4IuC1HG VUf4z03libRqRSo UIFCiYK02dq9xBF CpMYjMeAOLA. END KEYBASE SALTPACK SIGNED MESSAGE.
@tomaszslabon
BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zk7xdHzK Gm9BtmKb2FhcVia 1x14PuUuG7fVaLE jQhGdMxCf70ALIa e6PAijKSZkKJNR7 VkihOcAPHxDgX5l 3bbZ0iKJ1m1wPbg k4njMcY1vwUvoDM OnZIqBdINHfS3rH qt5fLqe9G7fG4Cr ALnYomNt4xEebJM gfF24n3Qgv4lWaQ bZym9QK8qvcHfgS DIFc3BQdlvePCcH SgZMa19N4IuC1HG VUf4z03libRqRSo UIFCiYK02dq9xBF CpMYjMeAOLA. END KEYBASE SALTPACK SIGNED MESSAGE.

Linux binary

Archive: linux-amd64.tar.gz (see Assets section)
sha256 sum: a184a1d8404e17f9197d44955567bb59bd1f08fcfb79a70ba6968c254db9a6a9 linux-amd64.tar.gz