MoonRunners
LogoLogo

678

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

Proposal #678

Recover expired IBC client 07-tendermint-331 (Injective <> QUAD Core lane)

PassedRecover Client

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

Yes

41.1%

100.0% without abstain

Veto

0.0%

of votes cast

Ended

31 Jul 2026

The ballotvotes cast · final tally
Yes

41.13%

of votes cast

Abstain

58.86%

of votes cast

No

0.01%

of votes cast

Veto

0.00%

of votes cast

07-tendermint-331 is Injective's IBC light client of the QUAD Core chain (chain-id: quad). It guards connection-336 and unordered transfer channel channel-457 (counterparty: QUAD connection-5 / channel-5). The connection and channel remain OPEN, but the client was created with a short 3-day trusting period and expired after relaying stopped, so the existing lane can no longer verify QUAD proofs.

This proposal performs the standard ibc-go client recovery: the expired subject client is replaced with the state of active substitute client 07-tendermint-346. The substitute tracks the same chain with the same trust level (1/3), 21-day unbonding period, 50-second maximum clock drift, proof specifications and update flags, while using a safer 14-day trusting period. Its creation and a subsequent update both committed successfully on Injective, and it is maintained by QUAD's existing client-freshness guard.

No funds move, no new permissions are granted, and no replacement connection or channel is created. Recovery revives the canonical connection-336/channel-457 lane and avoids fragmenting the existing route across duplicate IBC identifiers.

Timeline

  1. Submitted27 Jul 2026
  2. Voting started27 Jul 2026
  3. Voting ended31 Jul 2026
  4. Deposit deadline29 Jul 2026

Proposer

Address
inj1y9dt…qcnh7a
Deposit100000.00B

Rules

Not recorded for this proposal.