Prop 281: Recover expired IBC client 07-tendermint-174 (chain: quad)

This proposal recovers the expired Tendermint light client 07-tendermint-174 by substituting the state of the active client 07-tendermint-176, using ibc-go's standard client-recovery procedure (MsgRecoverClient, the successor to ClientUpdateProposal).

Both clients track the same counterparty chain (chain-id: quad) and match on every parameter ibc-go requires for recovery: trust level 1/3, unbonding period 21 days, max clock drift 50 seconds. The subject client expired in June 2026 when a relayer outage outlasted its short 3-day trusting period; the substitute is actively maintained and carries a corrected 12.5-day trusting period (a parameter recovery explicitly permits to differ, so the same failure cannot recur).

Recovery restores connection-181 and its interchain-accounts lane, unfreezing an ICA host account (stride137zrswt69ejeycwc7p05856a200x5wz3nm5uqzu5c52f6u0lrq2s4q7krs) holding approximately 4,932 STRD delegated to stridevaloper1dzm37phc9ax8r42nq29ypf5s8f5h2x0k80mh2w, plus accrued staking rewards, all inaccessible since the expiry.

This proposal moves no funds and changes no Stride chain parameters. It only writes the substitute client's state into the subject client, exactly as ibc-go's recovery path prescribes. Expired-client recoveries of this form are routine housekeeping and have passed on many IBC-connected chains.