Aurora-to-eth Fast Bridge: combine unlock with withdraw #100
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
karim-en
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Currently the user need to do 3 calls to do the refund for aurora to eth fast bridge transfers:
unlockwithdrawFromNearwithdrawThis pr remove the
withdrawFromNearby implementing a new apiunlock_and_withdrawon the NEAR side, so by that just two call will be needed to do a refund.unlockwithdrawIt is also will be good to combine those two calls on the aurora side, but there are some challenges to do that now that could be covered in a separate pr.