Unique ID enabling matches between source (Burn) and destination (mint) #62
Description
Hi all, we are integrating CCTP into our cross chain vault product.
One problem we've encountered is the ability to match deposit for burn events (and their message sent events) to the mint and withdraw events (and their message received events).
it seems the only way we can uniquely identify these is through the nonce, which is in the destination chain event but not in the source chain event. The nonce comes from iris.
The cctp documentation says nonces are deterministic. It would be helpful to know how nonces are constructed. It would make it easier for our indexing system to match events belong to the same bridge transfer.
or if that's not possible, would be helpful to hear your thoughts on how to pair events on source and destination chains.
thank you!