TL;DR
The IBC light client 07-tendermint-1499 on Osmosis, which tracks BitCanna (bitcanna-1), has expired because no relayer was updating it. This proposal replaces its state with that of a freshly created substitute client 07-tendermint-3761 using MsgRecoverClient. It restores the existing transfer channel without creating new channels or new IBC denoms.
Background
Osmosis side: client 07-tendermint-1499, connection connection-1167, channel transfer/channel-51
BitCanna side: client 07-tendermint-1, connection connection-1, channel transfer/channel-1
Last client update: 2026-10-03T17:12:46.068772238Z.
Trusting period: 10 days. The client is currently Expired (osmosisd q ibc client status 07-tendermint-1499).
An expired client cannot be revived by a normal update client; only governance can substitute it.
A matching recovery proposal for the BitCanna-side client (07-tendermint-1, tracking osmosis-1) is being submitted being prepared on BitCanna governance.
Impact of the expiry
IBC transfers over this channel cannot be relayed in either direction. Tokens in flight cannot be acknowledged or timed out. Existing ibc/ denoms of BCNA on Osmosis and OSMO on BitCanna remain unchanged; no tokens are moved by this proposal.
Substitute client
07-tendermint-3761, created on oct 25th, with identical chain-id (bitcanna-1), trust level (1/3), unbonding period (14 days = 1209600s), max clock drift (5s), proof specs and upgrade path as the subject client. Trusting period: 10 days. It is kept Active by BitCanna Community until execution.
Verification
osmosisd q ibc client state 07-tendermint-1499 -o json
osmosisd q ibc client state 07-tendermint-3761 -o json
Relaying going forward
BitCanna Community will run a Hermes relayer on this channel with client-freshness monitoring, so the client does not expire again.
Voting
Yes: recover 07-tendermint-1499 using substitute 07-tendermint-.
No: leave the client expired.
NoWithVeto: proposal is spam or violates governance standards.
Abstain: no opinion.