Prop 388: Recover expired IBC client with Noble (noble-1)

Juno's IBC light client for Noble, 07-tendermint-334 (connection-322, transfer/channel-224 <-> Noble transfer/channel-3), has expired. It was last updated on 2026-08-14 and its trusting period is ~17.8 days.

Cause: no relayer has updated the client since 2026-08-14. A dedicated relayer for this path is now running and funded.

Impact: while the client is expired no packets can move between Juno and Noble on this channel, including Noble USDC transfers.

Action: MsgRecoverClient replaces the state of the expired client with that of substitute client 07-tendermint-594, which tracks noble-1 with identical client parameters (trust level 1/3, unbonding 21d, max clock drift 600s). The existing connection and channel are preserved, so all ibc/... denoms on both chains remain unchanged.