anoma / namada

Rust implementation of Namada, a Proof-of-Stake L1 for interchain asset-agnostic privacy

Home Page:https://namada.net

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

IBC-transfers do not reach the recipient

TerzoMillenio opened this issue · comments

I've sent IBC-transfer to my osmosis address

root@root:~# namadac ibc-transfer --receiver osmo16h4gj7yqef90452hlwen3lpyl9nup46xhychg5 --source a --token NAAN --amount 1 --memo $MEMO --channel-id channel-995
Enter your decryption password:
Transaction added to mempool.
Wrapper transaction hash: 32F755E3430DC301573F2C4AE061405FB06661D4CDECEF05BA013DB4F2597731
Inner transaction hash: 3C9C8FC33A9008ED5A011674499E66E896E05DF71979EFDEF1F47D072C82555A
Wrapper transaction accepted at height 301871. Used 26 gas.
Waiting for inner transaction result...
Transaction was successfully applied at height 301872. Used 6193 gas.

As you can see, transaction was successfully applied, but there's no transactions on mintscan
https://www.mintscan.io/osmosis-testnet/address/osmo16h4gj7yqef90452hlwen3lpyl9nup46xhychg5

I've tried other channels and the result is the same

From Namada side, the sending succeeded. Do you know any idea about Hermes for the channel channel-995?

I created a channel to theta-testnet-001 also. Doesn't work either. We have transactions going out from Namada, but never reaching the recipient on target chain. This is the target address we set in the command: https://www.mintscan.io/cosmoshub-testnet/address/cosmos1f9d03fen0hqfwp6lctyrrvpnx86ptjcpcwnrv0. Relayer cosmos address: https://www.mintscan.io/cosmoshub-testnet/address/cosmos13lmtw0rkldz84q6e9gxd77snl02rawew4lx226. Transaction on Namada: https://testnet-explorer.madakimi.mobi/transactions/F3E054A6DD0FEA5CE39C6CB7B6B8CE055FD7F7AFC09D396D9AB18645808D9200. However, the inner transaction on this explorer shows error status, even though the CLI shows this:
Transaction added to mempool.
Wrapper transaction hash: F3E054A6DD0FEA5CE39C6CB7B6B8CE055FD7F7AFC09D396D9AB18645808D9200
Inner transaction hash: 1947A2C47CFDB02F550D2884AA7BF9D7F938BC9A5F1D7592EC4415518215842B
Wrapper transaction accepted at height 390593. Used 24 gas.
Waiting for inner transaction result...
Transaction was successfully applied at height 390594. Used 6193 gas.

@TerzoMillenio Thank you. Could you share the logs of Hermes(relayer) for the channel?

@TerzoMillenio Thank you. Could you share the logs of Hermes(relayer) for the channel?

What kind of log?

I made another channel, logs are clear

photo_2024-04-17_02-28-01
photo_2024-04-17_02-28-09

tx from namada sent successfully, but still doesn't reach destination
namadac ibc-transfer --source a --receiver cosmos1f9d03fen0hqfwp6lctyrrvpnx86ptjcpcwnrv0 --token NAAN --amount 50 --channel-id channel-1333
Enter your decryption password:
Transaction added to mempool.
Wrapper transaction hash: 9423F387B45A0660D04A7DF7290378BFEA77C8BCB2CD8E706D0FDF18F21B3866
Inner transaction hash: 5C28E82343AB6B2D694B075B213B76352081270DE73E4E19CEEA9E02CF7E0788
Wrapper transaction accepted at height 399268. Used 24 gas.
Waiting for inner transaction result...
Transaction was successfully applied at height 399269. Used 6193 gas.

Same result using RPC

namadac ibc-transfer --source a --receiver cosmos1f9d03fen0hqfwp6lctyrrvpnx86ptjcpcwnrv0 --token NAAN --amount 50 --channel-id channel-1333 --node https://namada-testnet-rpc.itrocket.net:443
Enter your decryption password:
Transaction added to mempool.
Wrapper transaction hash: DF8DD8E294E143E5E6A5D351EA30B8CA75645CB10D981567A38E522D14730D91
Inner transaction hash: 863133229744DFF54DFC3125FA39481CF940DBA467E8A0BF3E8C3006D02EAC15
Wrapper transaction accepted at height 399282. Used 24 gas.
Waiting for inner transaction result...
Transaction was successfully applied at height 399283. Used 6193 gas.

https://www.mintscan.io/cosmoshub-testnet/address/cosmos1f9d03fen0hqfwp6lctyrrvpnx86ptjcpcwnrv0

there are enought NAAN and ATOM on relayer's wallets

@TerzoMillenio I'd like to see the logs of hermes start that should relay IBC packets.

@TerzoMillenio I'd like to see the logs of hermes start that should relay IBC packets.

hermes.log

@TerzoMillenio I'd like to see the logs of hermes start that should relay IBC packets.

hermes.log

@TerzoMillenio Probably no one is relaying in the channels you are using to make the transactions, so it ends up with assets not being succesfully transferred (probably because one of its IBC clients already expired/frozen on one or both sides).

Regarding your Hermes config, you have not established any filter packets config. You can take a look at Hermes related docs for further reference.