BUG: Transfer an NFT from IRISnet Stargaze

[TheCodeor]

iris hash: 4650BF5F9771C0B51D977F368B3B74763F3E26205F09243BE1E9ABDD44B37E06
classid: isc721FanIRISId
nftid: isc721FanNFT1stId
transfer isc721FanNFT1stId to Stargaze success, But contractAddress cannot be found in Stargaze
When I replaced another nft isc721FanNFT2ndId, contractAddress can be found in Stargaze
use channel :
nft-transfer/channel-23 <> wasm.stars1ve46fjrhcrum94c7d8yc2wsdz8cpuw73503e8qn9r44spr6dw0lsvmvtqh/channel-208

When I replaced another channel， transfer isc721FanNFT1stId success，contractAddress can be found。
nft-transfer/channel-22 <> wasm.stars1ve46fjrhcrum94c7d8yc2wsdz8cpuw73503e8qn9r44spr6dw0lsvmvtqh/channel-207

[taitruong]

So you are saying you have send 2 NFTs from same collection and source chain (IRISnet) to same target chain (Stargaze), via same channel and 1st did not arrive and 2nd did arrive? I had the same issue and pretty/99% sure this an IBC relaying issue. We need to investigate more on this. I also transferred and it got 'reverted' (NFT send back to my owner wallet). Tried 2nd time and it worked.

[giansalex]

the error is probably caused by the timeout-height, since the CLI does not get the height from the remote chain, but from its own state. If the height is not updated in the state (IRIS), you will get an IBC Timeout.

To avoid this error, disable timeout-height, timeout-timestamp will be used instead.

iris tx nft-transfer transfer nft-transfer channel-24 \
  stars1ghcwp60uzgylr3kukkppzq457j0tlqw7f08kvu \
  isc721FanIRISId isc721FanNFT1stId \
  --packet-timeout-height 0-0