Proposal #1048: Recover expired IBC client 07-tendermint-3353 (MedasDigital)

Proposal Discussion
1

Hi everyone,

Proposal #1048 is currently in voting (ends 2026-10-03 14:05 UTC). It is a
technical IBC housekeeping proposal, so I want to explain it here.

What it does

  • Recovers the expired IBC light client 07-tendermint-3353 on osmosis-1
    (it tracks the chain medasdigital-2) via MsgRecoverClient, using the active
    substitute client 07-tendermint-3755.

Why

  • Our relayer was down and the client passed its trusting period (last update
    2026-04-27). Recovery through governance is the only way to reuse the existing
    connection and channels.

Safety

  • The substitute client has identical client parameters (chain ID, trust level,
    trusting period 14d, unbonding 21d, clock drift 40s, proof specs) and is
    active. The counterparty client on medasdigital-2 was already recovered through
    that chain’s own governance (executed).
  • No protocol parameters are changed. The message only affects this one client.

Links

Happy to answer questions.

2 Likes
2

If this passes, will transfers resume automatically, or will users need to do anything themselves?

3

yes, old packets will timeout.. Should work, tested it just now

4

Thanks for checking and confirming. Good to hear users won’t need to take extra steps.