update(arkeo): refresh Osmosis IBC path with new client and connection IDs

[InnovationTheory]

• Updated Osmosis IBC link for Arkeo to use new clients and connections
  • src_client_id: 07-tendermint-12
  • dst_client_id: 07-tendermint-3604
  • src_connection_id: connection-13
  • dst_connection_id: connection-10951
  • src_channel_id: channel-9
  • dst_channel_id: channel-107016

This change replaces the expired IBC client with the new valid one, restoring the transfer channel between Arkeo and Osmosis.

[CryptoAssassin1]

1. Revert field naming to snake_case:
   • chain-1 → chain_1
   • chain-2 → chain_2
   • chain-name → chain_name
   • client-id → client_id
   • connection-id → connection_id
   • channel-id → channel_id
   • port-id → port_id
2. Fix schema path: Change ../../ibc_data.schema.json to ../ibc_data.schema.json

[JeremyParish69]

There is already ARKEO liquidity established on Osmosis. A new or replacement transfer/transfer channel is not allowed (unless governance on both chain approve it).
A channel can be recovered through governance by recovering the client or replacing the client, but changing the channel id's is not allowed.

[InnovationTheory]

So it looks like both the client on Arkeo and Osmosis we created have expired. I am going through the process of MsgRecoverClient for the arkeo client, but I wasn't sure the process for handling this gov prop on the Osmosis side. Do I just submit it and do these get approved naturally, or do I have to create a case for the change? Appreciate your insight and help. -p Current: arkeod q ibc client status 07-tendermint-1 -o json {"status":"Expired"} New client created for the gov prop. arkeod q ibc client status 07-tendermint-12 -o json {"status":"Active"} Current: osmosisd q ibc client consensus-states 07-tendermint-3489 -o json | jq -r '.consensus_states[-1].consensus_state.timestamp' 2025-06-12T21:53:11.693909307Z New One Created for the Gov Prop: osmosisd q ibc client consensus-states 07-tendermint-3604 -o json | jq -r '.consensus_states[-1].consensus_state.timestamp' 2025-10-10T01:30:00.492273983Z

…

On Fri, Oct 10, 2025 at 12:06 PM JeremyParish69 ***@***.***> wrote: *JeremyParish69* left a comment (cosmos/chain-registry#6651) <#6651 (comment)> There is already ARKEO liquidity established on Osmosis. A new or replacement transfer/transfer channel is not allowed (unless governance on both chain approve it) — Reply to this email directly, view it on GitHub <#6651 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AXEU6XVYEMX3QFDE64ELWA33W7YSLAVCNFSM6AAAAACIZRK7W2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTGOJRGU4TKMZZHE> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[JeremyParish69]

So it looks like both the client on Arkeo and Osmosis we created have expired. I am going through the process of MsgRecoverClient for the arkeo client, but I wasn't sure the process for handling this gov prop on the Osmosis side. Do I just submit it and do these get approved naturally, or do I have to create a case for the change? Appreciate your insight and help. -p

It looks like it's the same message. I just searched Mintscan to find previous examples of recovering expired clients
e.g., https://www.mintscan.io/osmosis/proposals/973