Mezo Client v9 is Live

TLDR:

• Bitcoin can now be bridged into Mezo through a new triparty minting flow, adding a more flexible path beyond the existing two-party setup.
• New bridge capacity and minted supply functions give users and developers better visibility into bridge state in real time.
• Built-in guardrails, including minimum bridgeable amounts and capacity checks, help protect the system from abuse or over-minting.
• Developers get better gas estimation and contract simulation via state_override support in eth_call and eth_estimateGas.

Read on for feature details.

Triparty Bridge

The headline feature in v9.0.0 is the introduction of the Triparty Bridge. The Triparty Bridge adds a third participant, a controller, to that flow. Protocols and custodians can take the controller role in the bridging process.

For users, the Triparty Bridge is an additional path for moving BTC onto Mezo. The existing two-party bridge continues to operate alongside it.

Bridge capacity visibility

v9.0.0 adds two new precompile functions: getTripartyCapacity and getTripartyTotalBTCMinted. These expose the bridge's current limits and the total BTC minted through it. Applications can check capacity before initiating a bridge transaction. Monitoring tools can track minted supply directly from the chain state.

That makes the bridge easier to reason about. It also makes integrations easier to build and monitor.

Guardrails at the protocol level

The Triparty Bridge includes limits at the protocol level.

There is a minimum bridgeable amount. There are also windowed capacity checks that restrict how much BTC can be minted over time. These controls reduce the risk of abuse and prevent the bridge from expanding faster than its configured limits allow.

The bridge design now has more flexibility and clearer boundaries.

Better simulation for developers

v9.0.0 also improves day-to-day developer workflows.eth_call and eth_estimateGas now support state_override. Developers can run better simulations and get more accurate gas estimates before sending transactions onchain.

That improves contract testing. It also makes it easier to build applications that depend on precise execution.

What's next

v9.0.0 expands how BTC moves onto Mezo. The Triparty Bridge opens a new path for BTC to enter the chain, and the new precompile functions make bridge state observable in real time. Applications and integrations will begin using these capabilities in the coming weeks.

If you run infrastructure or want to go deeper, check out:

• The full v9.0.0 changelog and release are on GitHub.
• The Mezo Validator Kit for node setup and upgrade details.