Unreceived Packets in IBC Token Transfers

[cifer-ai]

Summary of Bug

Hi,

We've successfully set up an IBC relayer path. However, we're encountering issues with token transfers. Specifically, withdrawals via Osmosis Zone and IBC transfers through Keplr are getting stuck and showing as unreceived packets when we check with hermes tx packet-recv

While transferring token via Hermes using hermes tx ft-transfer went well.

It's important to note that our server is constantly running hermes start

We're reaching out to investigate the potential causes of this problem. Any insights you can offer would be greatly appreciated.

For reference, this issue is related to the one discussed in this GitHub pull request: osmosis-labs/assetlists#1417

Thank you for your support.

Version

Hermes v1.8.2

Steps to Reproduce

Testing on Osmosis Zone

1. Go to https://app.osmosis.zone/?to=CIF&from=USDC or https://app.osmosis.zone/?to=CIF&from=OSMO and swap for some CIF
2. Go to https://app.osmosis.zone/assets?show_preview_assets=true
3. Withdraw CIF, it will show as "pending" in transaction history

Testing on Keplr wallet

1. Add chain "Cifer" on Keplr extension
2. Try IBC transfer CIF IBC from Osmosis to Cifer via Keplr (wallet address prefix = cife), add new IBC channel: select Cifer as destination chain, with channel-39205
3. It will show as "Transaction success" but no CIF token received in wallet.

Acceptance Criteria

Please provide any insights which can be the cause of this problem.

---

For Admin Use

• Not duplicate issue
• Appropriate labels applied
• Appropriate milestone (priority) applied
• Appropriate contributors tagged
• Contributor assigned/self-assigned

[ljoss17]

Hi,
Do you mean that your running instance, hermes start, is not relaying the packets but if you run the manual relaying hermes tx packet-recv it succeeds?
If it is the case, can you share the configuration used by the running Hermes instance as well as logs at debug level of the instance running 10 minutes before and after the transfer?