Request: Recover IBC light client with UX Chain (Umee) — 38K AKT stuck

[Decone3]

Injective recently submitted Prop 646 to recover the IBC light client between UX Chain and Injective. A similar action is needed on the Akash side.

Currently ~38K AKT are supplied on the UX lending platform and completely stuck — the IBC channel between Akash and UX Chain has expired on both sides, preventing any withdrawal or liquidation.

Can the Akash core team or a validator submit a similar governance proposal to recover the IBC light client on the Akash side?

Wallet affected: akash130cnch52qz9p8ezqquhp26q680qlrxumsmw65z (Keplr)

[inoCcCent77]

An action similar to Akash proposal 294 (Reactivate expired IBC client for Umee) from mid 2025 is requested.

The IBC client 07-tendermint-118 used for Umee is currently in an expired state. If accepted, this proposal will update client 07-tendermint-118 with the data from 07-tendermint-193

It was posted on the UX discord yesterday, the devs on UMEE can take care of the UX side.

Support from Akash side is required.

[HikingDev]

Hi team, could you please sanity-check this Akash governance proposal before I submit it?

Goal: recover the expired Akash-side UX Chain IBC client for the Akash <-> UX transfer path.

Akash channel: channel-38
UX counterparty channel: channel-5
Expired subject client on Akash: 07-tendermint-92
Fresh substitute client on Akash: 07-tendermint-209

The substitute client is currently Active and matches the old client parameters:

• chain_id: umee-1
• trust_level: 1/3
• trusting_period: 1123200s
• unbonding_period: 1209600s
• max_clock_drift: 20s

Here is the exact proposal JSON I plan to submit:

{
"messages": [
{
"@type": "/ibc.core.client.v1.MsgRecoverClient",
"subject_client_id": "07-tendermint-92",
"substitute_client_id": "07-tendermint-209",
"signer": "akash10d07y265gmmuvt4z0w9aw880jnsr700jhe7z0f"
}
],
"metadata": "",
"deposit": "400000000uakt",
"title": "Recover expired UX Chain IBC client",
"summary": "This proposal recovers the expired IBC light client for UX Chain on Akash. The expired subject client 07-tendermint-92 is used by the Akash transfer channel channel-38, whose counterparty on UX Chain is channel-5. This path is needed to restore IBC transfers between Akash and UX Chain so users can recover and withdraw AKT liquidity currently stuck on UX Chain. The substitute client 07-tendermint-209 is a fresh active Tendermint client for umee-1 with matching client parameters: trust level 1/3, trusting period 1123200s, unbonding period 1209600s, and max clock drift 20s."
}

Can you confirm that this is the correct recovery path for restoring Akash channel-38 / UX channel-5?

[RSCris]

Thanks for submitting the proposal @HikingDev
One issue I noticed after checking the AKT denom trace: the live proposal appears to target a different Akash <> UX path than the AKT currently stuck on UX.

The live proposal targets:

Akash channel-38
UX channel-5
subject client 07-tendermint-92

The AKT denom currently stuck on UX appears to use:

UX channel-48
Akash channel-60
UX client 07-tendermint-169 expired
Akash client 07-tendermint-118 expired
denom: ibc/0B1D3A663E6D41C7B1CFC78DB41C829A3B8329D396B47737445AFF5E0E9DA125

So this proposal may still recover a valid UX <> Akash path, but it likely will not unlock the existing AKT denom on UX.

Since the proposal is already live, the clean fix is probably a new follow-up proposal targeting the actual stuck AKT path, especially Akash client 07-tendermint-118 / UX channel-48 <> Akash channel-60.

Can someone from Akash sanity-check this path and confirm the right substitute client for 07-tendermint-118?

[HikingDev]

Hi Chris,

thanks for the follow up.
I guess I should have waited for feedback.
Will resubmit once the proposal has concluded.

[RSCris]

We'll resubmit it today, so we can "win" 2 days, if you reached out to someone previously for support, please support this one as well

[HikingDev]

awesome! Thanks for the support. I didnt reach out but it seems that proposals like that are easily accepted. I guess mentioning that the previous proposal had a flaw