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

**URL:** <https://forum.osmosis.zone/t/proposal-1048-recover-expired-ibc-client-07-tendermint-3353-medasdigital/4140>\
**Category:** Proposal Discussion\
**Created:** [September 28, 2026, 2:09pm UTC](https://forum.osmosis.zone/t/proposal-1048-recover-expired-ibc-client-07-tendermint-3353-medasdigital/4140 "2026-09-28T14:09:20Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![oxygene](https://avatars.discourse-cdn.com/v4/letter/o/85f322/32.png) [@oxygene](https://forum.osmosis.zone/u/oxygene)\
**Post date:** [September 28, 2026, 2:09pm UTC](https://forum.osmosis.zone/t/proposal-1048-recover-expired-ibc-client-07-tendermint-3353-medasdigital/4140/1 "2026-09-28T14:09:20Z")

</div>

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

- Proposal: [OSMOSIS Proposal 1048 - Mintscan](https://www.mintscan.io/osmosis/proposals/1048)

Happy to answer questions.