Recover expired Stride light client 07-tendermint-169
Band Protocol proposal #22: The Stride light client 07-tendermint-169 on BandChain expired on 2026-08-17 (last consensus state 2026-08-05; 11.9-day trusting...
Yes
100%
No
0%
Abstain
0%
Veto
0%
Original Proposal Text
The Stride light client 07-tendermint-169 on BandChain expired on 2026-08-17 (last consensus state 2026-08-05; 11.9-day trusting period lapsed). This client backs connection-150, the counterparty of Stride's connection-146, which carries every interchain account Stride uses to liquid stake BAND (delegation, withdrawal, fee, redemption and community-pool ICAs) and the transfer channel pair channel-258 (Stride) / channel-161 (Band). With the client expired, Stride cannot operate the BAND host zone at all: ~1,060 BAND of completed unbondings are stranded in the delegation ICA (band1r9sw8tc4z8sgzy8nvkzes4t7qset9seqwr7854phphlp9wkxs3vqlnj5g3) waiting to be swept back to redeeming users, two further redemption batches (~126.6 BAND) cannot begin unbonding, ~44 BAND of accrued rewards sit unclaimed in the withdrawal ICA, and ~513,000 BAND of delegations cannot be rebalanced or compounded. This proposal substitutes the expired client with 07-tendermint-397, a freshly created and actively maintained Stride client with identical parameters (chain-id stride-1, 1/3 trust level, 1026000s trusting period, 1209600s unbonding period, 600s max clock drift, same upgrade path). Client recovery via governance is the standard IBC procedure (ibc-go ADR-026 / MsgRecoverClient): it only refreshes the existing connection's light client, moves no funds, and grants no privileges to anyone. More details: Stride light client recovery on BandChain (07-tendermint-169 -> 07-tendermint-397)