*** 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 • 10h 31m left *** Set Minimum Notional for FanPicks (PICKS) • Injective Protocol • 13h 34m left *** Store Bluechip factory.wasm (1 of 3) • Osmosis • 96h left
Cosmos Hub Logo

Cosmos Hub

#1048

FAILED

Recover expired IBC Client for Gravity Bridge

Proposal Type: Text (Signaling)

Proposal Contents (*the original text from the proposer)

This proposal seeks to recover IBC Client 07-tendermint-582 connecting CosmosHub to Gravity Bridge. The recovery process will replace the state of expired client with the state of newly created substitute client 07-tendermint-1496.

Due to an exploit executed on Gravity Bridge, the network was down for several weeks, causing IBC clients to expire.

Discussion: https://forum.cosmos.network/t/gravitybridge-ibc-reactivation/17168

Voting Results

Status: Quorum Not Met
(18.72% of the required 40.00%)
Tokens Voted
61,082,400
Yes
58,635,762
96.0%
No
5,868
0.0%
No With Veto
2,282
0.0%
Abstain
2,438,487
4.0%

Vox Populi

Community discussions related to the proposal.

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