Refactored token types & whitelising process #1053
Merged
Conversation
This file contains 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
docs/bridge/token-types.md
Outdated
| **1. Mint/Burn & Native on MultiversX < - > EVM-chain has Mint/Burn & Non-Native** | ||
|
|
||
| This bridge token-type configuration has the advantage of not holding a single token in the bridge. | ||
| The swapped tokens are minted/burned on both sides. The total token quantity of tokens equals the (minted - burned) on MultiversX |
There was a problem hiding this comment.
The total token quantity of tokens ---> maybe avoid repetition of the word token/tokens
evelinemolnar
previously approved these changes
Jan 29, 2025
evelinemolnar
approved these changes
Jan 29, 2025
sstanculeanu
approved these changes
Jan 29, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description of the pull request (what is new / what has changed)
Did you test the changes locally ?
Which category (categories) does this pull request belong to?