*** Authorize Indexer Performance Upgrade v1.6.1 • Injective Protocol • 0h 0m left *** Security validation for InjHub proposal rendering • Injective Protocol • 0h 0m left *** Migrate ServiceRegistry contract • Axelar Network • 0h 0m left *** Update Oracle Feeds to Pyth Pro for Various Perpetual Markets on Injective Exchange dApps Batch 2 • Stargaze • 0h 0m left *** Allow axelar14vps3ev03zyp2wmj89etx8rrxdxyltfy4rzl5m to upload wasm code • Axelar Network • 0h 0m left *** Set instantiate_default_permission to AnyOfAddresses • Axelar Network • 0h 0m left *** Allow axelar14vps3ev03zyp2wmj89etx8rrxdxyltfy4rzl5m to upload wasm code • Axelar Network • 0h 0m left *** Signaling Proposal: Freeze Hacker Funds and Recustody to a Trusted Distributor at a Later Date • Axelar Network • 0h 0m left *** Recover expired IBC client 07-tendermint-1737 (Osmosis <> Gravity Bridge) • Osmosis • 0h 0m left *** Recover Quicksilver IBC client • Cosmos Hub • 11h 34m left *** Set Minimum Notional for FanPicks (PICKS) • Injective Protocol • 14h 38m left *** Store Bluechip factory.wasm (1 of 3) • Osmosis • 97h left
Injective Protocol Logo

Injective Protocol

#678

PASSED

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

Proposal Type: MsgRecoverClient

Proposal Contents (*the original text from the proposer)

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.

Voting Results

Status: Quorum Met
(44.36% of the required 33.40%)
Tokens Voted
25,105,320
Yes
10,326,353
41.1%
No
1,290
0.0%
No With Veto
156
0.0%
Abstain
14,777,521
58.9%

Vox Populi

Community discussions related to the proposal.

There do not appear to be any discussions on this proposal at this time.