Prop 509: Recover expired IBC client 07-tendermint-65 (Axelar <> Carbon)

The IBC client 07-tendermint-65 on Axelar, which tracks carbon-1, expired while Carbon was halted. Carbon resumed on 29 Oct 2026. This proposal replaces its state with that of the active substitute client 07-tendermint-275 using MsgRecoverClient. The existing connection and channel (connection-44, transfer/channel-37) stay as they are, with no new channels or denoms. The proposal moves no funds and changes no parameters. Carbon's own client of Axelar was recovered through Carbon governance (proposal 431). The recovery lets relayers resume the existing channel after the halt, including the packets stuck since the expiry.

The substitute was created in tx 47BCFAFFBBE1E09C889C80BA4F9A61A21C3C417406BD0BF2C0DF955E9F7BF0CD at Axelar height 37250451. It differs from the expired client only in latest height: chain id, trust level (1/3), trusting period (14 days), unbonding period (30 days), clock drift (40s), proof specs and upgrade path all match.

To confirm this is the real Carbon chain: Axelar connection-44 (client 07-tendermint-65) and Carbon connection-11 (client 07-tendermint-12) point at each other. The chain registry lists tm-api.carbon.network as a Carbon RPC (carbon/chain.json in cosmos/chain-registry). The last state 07-tendermint-65 stored matches carbon-1 block 100278156 on that RPC: root, next validators hash and time. The substitute stores block 100609999 (hash 8435170607D01BD601D4113449ECDD0142287A86E24AC9AD4969EF3E557EEE08). Validators holding 88.28% of the voting power 07-tendermint-65 last trusted signed that block, and their keys hash to the next validators hash already stored on Axelar. A normal client update needs more than 1/3.