This PR adds support for a custom XRPL message ID, which comprises of just a 32-byte hash.
To initiate bridging from XRPL, a Payment transaction is made into an XRPL multisig (which can be though of as a replacement for the AxelarGateway).
Since XRPL does not support batched transactions, there can only be one bridging transaction per XRPL transaction, so an event index is redundant.
Todos
[x] Unit tests
[ ] Manual tests
[ ] Documentation
[ ] Connect epics/issues
Steps to Test
Expected Behaviour
Other Notes
We do not have full context of all the moving pieces that this PR affects. Please review and let us know if you see any issues or recommend any changes.
Description
This PR adds support for a custom XRPL message ID, which comprises of just a 32-byte hash. To initiate bridging from XRPL, a
Payment
transaction is made into an XRPL multisig (which can be though of as a replacement for theAxelarGateway
). Since XRPL does not support batched transactions, there can only be one bridging transaction per XRPL transaction, so an event index is redundant.Todos
Steps to Test
Expected Behaviour
Other Notes
We do not have full context of all the moving pieces that this PR affects. Please review and let us know if you see any issues or recommend any changes.