Recover Akash IBC Client 07-tendermint-118 for UX Chain (Umee)
Akash proposal #327: This proposal recovers the expired Akash-side IBC light client for UX Chain. A previous Akash proposal targets a different Akash UX IBC...
Yes
97%
No
0%
Abstain
3%
Veto
0%
AI Summary
gpt-5.4-mini - generated 6/8/2026, 11:13:15 PM
Recover Akash IBC Client 07-tendermint-118 for UX Chain (Umee)
Proposal 327 on Akash aims to recover an expired Akash-side IBC light client used by UX Chain (Umee). It says a prior Akash proposal affected a different IBC path and would not unlock the stuck AKT liquidity. The proposal updates client 07-tendermint-118 with fresh client 07-tendermint-211 to restore the correct route for IBC transfers.
- Recover expired Akash-side IBC client 07-tendermint-118.
- Use active substitute client 07-tendermint-211 to update the subject client.
- Target the AKT route tied to UX channel-48 and Akash channel-60.
- A prior Akash proposal is described as addressing a different path and not this stuck liquidity.
Voter Impact
A yes vote would restore the IBC client needed for the specific Akash-UX route, potentially enabling the currently stuck AKT transfers. A no vote would leave the expired client unrecovered and the route unresolved.
Risk Signals
- Effectiveness depends on the proposal correctly matching the stuck AKT path.
- The description indicates an earlier proposal may not solve this issue, suggesting path-specific uncertainty.
- If the route identification is wrong, the update may not unlock the liquidity.
Original Proposal Text
This proposal recovers the expired Akash-side IBC light client for UX Chain. A previous Akash proposal targets a different Akash UX IBC path and is not expected to unlock the AKT liquidity currently stuck on UX Chain. The affected AKT denom appears to use the UX channel-48 Akash channel-60 transfer path, which depends on the expired Akash client 07-tendermint-118. This proposal updates the expired subject client 07-tendermint-118 using the fresh active substitute client 07-tendermint-211. The goal is to restore the correct Akash-side client for the stuck AKT route so IBC transfers between Akash and UX Chain can be recovered for this path.