Proposal #43
Passed on 30 Sept 2026 with 100.0% of the votes for yes.
Yes
100.0%
100.0% without abstain
Veto
0.0%
of votes cast
Ended
30 Sept 2026
100.00%
of votes cast
0.00%
of votes cast
0.00%
of votes cast
0.00%
of votes cast
This proposal revives Dymension's IBC connection to Injective so native USDC issued by Circle on Injective can be transferred to the Dymension Hub.
Background: Circle is discontinuing USDC on Noble. Noble minting stops on October 13, 2026, and Noble USDC is fully paused on January 12, 2027. The Cosmos ecosystem is migrating to Circle's native USDC on Injective. Dymension already has a transfer channel to Injective (channel-47 on Dymension, channel-259 on Injective), but Dymension's light client of Injective, 07-tendermint-41, has expired because no relayer kept it updated. The Injective side of this connection (its client 07-tendermint-257 of Dymension) is still active, so only the Dymension side needs recovery.
What this proposal does: it executes MsgRecoverClient, replacing the expired client 07-tendermint-41 with the state of a freshly created, active substitute client 07-tendermint-83 that tracks the same chain (injective-1) with identical parameters (trust level 1/3, unbonding period 21 days, max clock drift 75s). Existing connection connection-250 and channel-47 keep their identifiers, so no new channel or new USDC denom is created.
After the proposal passes, relayers will resume relaying on channel-47. Injective USDC will arrive on Dymension as ibc/3713D1D8F4BA779A6B4705B8695634DBA68D84E404D39986E983914353EF5CA2 (transfer/channel-47/erc20:0xa00C59fF5a080D2b954d0c75e46E22a0c371235a).
Validators and delegator accounts, counted one vote each.
20 of 66 validators voted, 100% yes. 1 delegator accounts voted on their own, 0% yes.
Each validator's vote, by voting power.
20 validators voted, together 23.5% of the voting power.
