assetmantle

Prop 82: Recover IBC Light Client 07-tendermint-0 (Osmosis) to Revive MNTL↔OSMO Bridge

Summary

Replace the expired state of IBC light client 07-tendermint-0 (which tracks osmosis-1) with the fresh state of substitute client 07-tendermint-127. Passing this proposal restores the mantle-1 ↔ osmosis-1 IBC bridge without opening new channels, preserving the existing channel-0 ↔ channel-232 path and the canonical IBC denom of MNTL on Osmosis (ibc/CBA34207E969623D95D057D9B11B0C8B32B89A71F170577D982FDDE623813FFC).

Background

The original halving bot went offline in Q1 2026, and with it the public relayer maintaining the mantle↔osmosis IBC connection. The Osmosis light client on mantle-1 (07-tendermint-0) last received an update on 2026-01-16; trusting period is 10 days, so it has been Expired for ~95 days as of this proposal. The mirror-side client on Osmosis (07-tendermint-1923) expired on a similar timeline and a companion proposal is being filed on Osmosis to recover it.

In ibc-go v4 the allow_update_after_expiry flag (still true on this client) is no longer sufficient by itself — only a governance-approved ClientUpdateProposal can swap an expired client's state for a fresh substitute. A replacement client tracking osmosis-1, with ID 07-tendermint-127, has already been created on mantle-1 in tx 63FE0ED7E0D83EF3AEC8DCD438F987456DCEB311EF1FE5181DFB244361311F4F at height 22,002,668 and verified as Active. This proposal asks governance to promote that substitute into the slot held by 07-tendermint-0.

Why this matters

  • Pool #690 on Osmosis becomes tradeable again immediately after the companion Osmosis proposal passes. ~3.27M MNTL currently sits in that pool under the preserved IBC denom.
  • No new channel is needed. Preserving channel-0 ↔ channel-232 means existing Osmosis-held MNTL stays fungible with freshly bridged MNTL. Alternative paths (open new channel) would strand all MNTL currently on Osmosis in a legacy denom and split liquidity.
  • This is the last mantle-1 governance chore required to restore cross-chain functionality — no subsequent action needed on this chain; the companion Osmosis proposal handles the other side.

Implementation

Executes ibc.core.client.v1.ClientUpdateProposal with:

  • subject_client_id: 07-tendermint-0
  • substitute_client_id: 07-tendermint-127

Upon passage, 07-tendermint-0's frozen/expired state is overwritten with the current consensus state of 07-tendermint-127. The client ID itself and all downstream connections/channels bound to it remain valid.

Reference

Companion proposal on osmosis-1 recovers the mirror-side client 07-tendermint-1923 using substitute 07-tendermint-3679 (created in osmosis-1 tx F4DE1AA9B6633E08FD58107FFB40D6ED748546A5CB7B8930C836B21266FAE3C3 at height 59,818,759).

Both proposals must pass for the bridge to recover. This proposal alone restores the Osmosis light client as seen from mantle-1; it does not by itself restart cross-chain transfers until the companion Osmosis proposal is also approved.