Open pharr117 opened 8 months ago
We may need to pull in something from the Wormhole package in order to parse this out:
https://github.com/wormhole-foundation/wormhole/tree/main/sdk
They provide some utils to parse wormhole addresses. Docs are here:
I am not entirely sure just yet if it will be possible to pull this into an address, it could represent some other chain data that is not a Cosmos address.
After #503, we will need to do the following to fix these TXes, couple options:
reindex-message-type
- Use this to reindex ALL TXes that contain this message type, this would be a shotgun approachHey @pharr117, yes, the receiver address is malformed. The write acknowledge shows an error ack so the tx was refunded, not transferred.
@misko9 thanks for pointing that out, I see how we can parse out the write_acknowledgement
event and check for errors. Thanks for the info!
The receiver address for the wormhole Recv message contains a bad string in the receiver inside the data object. The error happens during insertion in the database since it is not proper UTF-8:
Even mintscan (as of time of writing this) is having trouble parsing out the data:
https://www.mintscan.io/osmosis/tx/E26846FCAE22AAF984731AF38673EC49F9B4DA3280F1B00D763C8CF1B963F55A?height=11980424