Add swap token to native, directSend fix #140
Open
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
This makes it compatible with OpenZeppelin's burnFrom() if called by an address that is not a whitelisted bridge.
DanielCMorales
approved these changes
May 1, 2023
Spire83
approved these changes
Aug 9, 2024
| } | ||
|
|
||
| if (_dstChainId == chainId) { | ||
| _directSend(_receiver, _amountIn, chainId, _srcSwap, _nonce, srcTokenOut, srcAmtOut); |
Spire83
approved these changes
Aug 23, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
You can't swap token to native token in dst chain. So that's why nativeOut will be needed in TransferWithSwap.
When you execute directSend logic without bridging you send tokens to TransferSwap app contract in source chain, but it has to be message sender.