BUG: NFT stuck after apparent successful recv_packet

[gjermundgaraba]

I believe, right now at least, this particular issue to be different than most of the "stuck" issues which are just IBC transactions not relayed. In this case, the message has been relayed.

Initial transaction: https://gon.ping.pub/iris/tx/31BF0367A0CC2855A5A29D414F0026AC62F03B47E2DA20B4B45F9D84981B3499

Receive transaction: https://gon.ping.pub/stargaze/tx/4379374DCEE2CAEA5EEEBACFBE476BFC7C4D2B57993D9695C6209DDCF1073503

In the write_acknowledgement events, we can see something happened:

packet_ack: {"error":"codespace: wasm, code: 5"}

The owner of the NFT in question is still the bridge:

$ starsd q wasm contract-state smart stars1t96ufuv24knrau6d4vnzq4988v7j0um4m9efu8chh4eenmr755nsuexkcp '{"owner_of": {"token_id": "test01"}}'
data:
  approvals: []
  owner: stars1ve46fjrhcrum94c7d8yc2wsdz8cpuw73503e8qn9r44spr6dw0lsvmvtqh

[giansalex]

if recv_packet returns an ack with error, the IBC handshake has failed, it should be reversed in the IBC Acknowledge on IRIS.

But the problem here is that this token should not exist in the Stargaze chain, more details #501