Update IBC for cosmoshub-irisnet

[oncloudit]

the channel-0 in IRIShub was created early when the chain supported IBC ics20, and be running by IRISnet officially. have to update the previous in the repo as the id of client and connection are different.

[JeremyParish69]

Please provide evidence of both chains voting to change the canoncial channel (or that the previous channel was never used and has no tokens stuck on the counterparty chain).

[JeremyParish69]

It looks like the currently registered connection has been used to transfer both IRIS and ATOM using the existing channel, but only as recent as late 2022.
The replace connection appears to be slightly older, and has active transfers at least throughout 2024.

This is a tricky situation, because the Cosmos Chain Registry has a policy to never allow changing the registered IBC channel unless it can be proven that either no tokens would be abandoned on either chain, or that governance on both chains has voted to update the canonical/registered channel.
However, by looking at the data, it is apparent that the suggested replacement does appear to be the primarily used channel.

[oncloudit]

thank for your reply and explanation, we should register the IBC channel more early.
if there're no other ways to pass the replacement above or modify the policy of the Cosmos Chain Registry, we'll prepare to proposal an text gov about updating the registered channel in this repo, hope them will be passed on both CosmoHub and IRISHub chain!

[JeremyParish69]

Well, @reversesigh or @dylanschultzie might have opinions on updating the policy, but I'd say I can make major changes to policy like that unilaterally, and in the meantime I think we'll need a signaling proposal on both chains.

[JeremyParish69]

Closing unless there is anything to add