# \[PROP #43\] Restore the Dymension ↔ Injective IBC Connection

**URL:** <https://forum.dymension.xyz/t/prop-43-restore-the-dymension-injective-ibc-connection/4287>\
**Category:** Dymocracy\
**Created:** [September 28, 2026, 3:11pm UTC](https://forum.dymension.xyz/t/prop-43-restore-the-dymension-injective-ibc-connection/4287 "2026-09-28T15:11:49Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Yishay](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.dymension.xyz/yishay/32/2240_2.png) [@Yishay](https://forum.dymension.xyz/u/Yishay)\
**Post date:** [September 28, 2026, 3:11pm UTC](https://forum.dymension.xyz/t/prop-43-restore-the-dymension-injective-ibc-connection/4287/1 "2026-09-28T15:11:49Z")

</div>

# **[PROP** #43] **Restore the Dymension ↔ Injective IBC Connection**

### **TL;DR**

#### Dymension’s IBC light client for Injective (07-tendermint-41) expired about a year ago, which has disabled channel-47. This proposal replaces it with a fresh client using the standard MsgRecoverClient, so that transfers between Dymension and Injective work again. This is needed for USDC.inj, which replaces Noble USDC. Circle is retiring Noble USDC: minting stops Oct 13, and the contract is paused Jan 12, 2027.

**Context**

| | | | |
| --- | --- | --- | --- |
| Channel | channel-47 ↔ Injective | channel-259 | |
| Connection | connection-32 ↔ Injective | connection-250 | |
| Client on Dymension | 07-tendermint-41 (injective-1), **Expired** | | |
| Last update | Injective height 130,415,694 (Aug 24, 2025); expired ~Sep 7, 2025 when the 14-day trusting period lapsed | | |
| Injective side | Client | 07-tendermint-257 | , **Active** |

- The client was created with allow\_update\_after\_expiry: true, so it can be recovered through governance.
- Recovering it keeps channel-47 and every existing IBC denom (INJ, and USDC.inj once it arrives). Opening a new connection instead would give the same assets a second, different denom on Dymension.
- ~311.5K Noble USDC sits on Dymension today. Holders need a working route to Injective to migrate it through Skip:Go.
- An incentive plan to bootstrap a new liquid pool will be proposed after the migration and initiation of USDC.inj.

### **Proposal**

- Execute MsgRecoverClient, replacing subject client 07-tendermint-41 with substitute client 07-tendermint-XX. The substitute is a new injective-1 client that uses the same parameters (trust level 1/3, trusting period 14d, unbonding period 21d, max clock drift 75s).

- A relayer commits to keeping channel-47 updated after recovery, so the client doesn’t expire again.

- After it passes: send test transfers, then ask Skip:Go to add Dymension to the USDC.inj migration route.

### **Governance Votes**

**YES** : Replace the expired client and restore the Dymension ↔ Injective IBC channel.

**NO** : Leave channel-47 disabled.

**NO WITH VETO** : The proposal is spam or harmful to the protocol.

**ABSTAIN** : Counts toward quorum without taking a side.