*** Welcome to Plebis — explore your favorite projects and proposals *** 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 *** Settle WBD Perpetual and Update PSKY Ticker on Injective Exchange dApps • Injective Protocol • 15h 5m left *** Withdraw Margined-Managed OSMO LST and ETH/BTC Liquidity • Osmosis • 41h left *** Withdraw Static Community Pool Liquidity • Osmosis • 41h left *** Move the 1,227,121 ATOM recovered after the Neutron exploit to the Neutron recovery multisig • Cosmos Hub • 131h left
Agoric Logo

Agoric

#121

PASSED

Recover expired Stride IBC client 07-tendermint-74 (Agoric <> Stride, channel-59)

Proposal Type: MsgRecoverClient

Proposal Contents (*the original text from the proposer)

This proposal recovers Agoric's expired light client for Stride (stride-1), 07-tendermint-74, by substituting it with 07-tendermint-129, a freshly created and actively maintained client with compatible parameters (chain-id stride-1, 1/3 trust level, 1026000s trusting period, 1209600s unbonding period, 600s max clock drift, matching proof specifications and upgrade path). The transfer channel pair Stride channel-148 / Agoric channel-59 (Stride connection-118 / Agoric connection-68) is the canonical Stride<>Agoric route registered in the cosmos/chain-registry. Its light clients on both chains were last updated on 2026-08-07 and have since expired (Stride 07-tendermint-129, trusting period 17.8 days; Agoric 07-tendermint-74, trusting period 11.9 days). As of 2026-09-30 the Stride-side escrow for channel-148 holds ~2,425 stATOM, ~5,920 stOSMO and ~14,268 stTIA — the backing for the stATOM/stOSMO/stTIA IBC vouchers held on Agoric — and there are 6 unresolved outbound packet commitments from Stride plus 1 from Agoric that will require relay or timeout processing after recovery. Because the same channel must be revived on both chains, the companion recovery proposal must also be submitted and passed on Stride. Client recovery via governance is the standard ibc-go procedure (ADR-026 / MsgRecoverClient): it copies the substitute's latest consensus state into the expired client. Recovery requires an active, newer substitute of the same client type whose trust level, unbonding period, max clock drift, proof specifications and upgrade path match the subject client; chain ID, trusting period, latest height and frozen height are permitted to differ. It moves no funds and grants no privileges to anyone; it only lets relayers resume updating the existing client so the existing channel can carry packets again. Note on identifiers: both 07-tendermint-74 (subject) and 07-tendermint-129 (substitute) are client ids on Agoric; the coincidentally identical id 07-tendermint-129 on Stride is a different client (Stride's expired client for Agoric, recovered by the companion Stride proposal).

Voting Results

Status: Quorum Met
(64.53% of the required 33.40%)
Tokens Voted
290,723,097
Yes
290,692,690
100.0%
No
0
0.0%
No With Veto
10,307
0.0%
Abstain
20,100
0.0%

Vox Populi

Community discussions related to the proposal.

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