MoonRunners
LogoLogo

334

  1. /
  2. Akash
  3. /
  4. Mainnet
  5. /
  6. Governance
  7. /
  8. 334
  • Docs
  • Support
2026 © Made with 💜 by MoonRunnersAPI OK
DocsSupportDonate

Proposal #334

Recover expired IBC client 07-tendermint-213 (Akash <> QUAD Core transfer lane)

PassedRecover Client

Passed on 31 Jul 2026 with 94.4% of the votes for yes.

Yes

94.4%

97.1% without abstain

Veto

0.0%

of votes cast

Ended

31 Jul 2026

The ballotvotes cast · final tally
Yes

94.39%

of votes cast

Abstain

2.83%

of votes cast

No

2.78%

of votes cast

Veto

0.00%

of votes cast

07-tendermint-213 is Akash's IBC light client of the QUAD Core chain (chain-id: quad). It guards connection-209 and the unordered transfer channel channel-142 (counterparty: quad connection-1 / channel-1). The client was originally created with a short 3-day trusting period and expired on 2026-07-01 after a relaying pause (last consensus state 2026-06-28). The connection and channel remain OPEN on both chains, and 23.359901 AKT sits in the channel-142 escrow backing vouchers on the QUAD side.

This proposal performs the standard IBC client recovery (ibc-go MsgRecoverClient): the expired client state is replaced with the state of substitute client 07-tendermint-216, created 2026-07-23 with identical chain-id, trust level (1/3), unbonding period (21 days) and max clock drift (50s), and a safer 14-day trusting period. No funds move and no new permissions are granted; recovery only revives the existing canonical lane, preventing escrow stranding and liquidity fragmentation across a duplicate channel.

QUAD ([Hidden link]) operates an Akash validator and the public akash.rpc.uquad.org RPC endpoint. After recovery the lane returns to active hermes relaying with client-freshness monitoring so it cannot idle-expire again.

Timeline

  1. Submitted24 Jul 2026
  2. Voting started24 Jul 2026
  3. Voting ended31 Jul 2026
  4. Deposit deadline07 Aug 2026

Proposer

Address
akash1hr…xhqdys
Deposit1.0K

Rules

Not recorded for this proposal.