featu: add Khalani integration #534
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds Khalani integration and depends on hyperlane-xyz/hyperlane-monorepo#5845.
The core logic was added here.
Khalani has a particular flow to complete a transfer:
assetReservesFor both of these actions,
warpCore.getTransferRemoteTxsis used, ensuring the existing flow works as it does for warpRoutes.After these two actions are completed, Khalani requires a few extra steps to complete the transfer. The current implementation does not cover these, so a new condition was added for this special case. When the token standard is Khalani, a new block of code was added that enables us to:
It was also necessary to adapt the transaction store and modal to request the user signature and also to reflect the progress of the transaction.