Sync remainder of tokens to new property standard#34
Open
0xBreadguy wants to merge 20 commits intomegaeth-labs:mainfrom
Open
Sync remainder of tokens to new property standard#340xBreadguy wants to merge 20 commits intomegaeth-labs:mainfrom
0xBreadguy wants to merge 20 commits intomegaeth-labs:mainfrom
Conversation
* refactor(wrsETH): migrate to isOrigin/mechanism * Update data.json * Update data.json --------- Co-authored-by: BREAD <97642356+0xBreadguy@users.noreply.github.com>
* refactor(WETH): migrate to isOrigin/mechanism * Update megaeth properties in data.json Changed 'isOrigin' to true and added 'mechanism' field. --------- Co-authored-by: BREAD <97642356+0xBreadguy@users.noreply.github.com>
* refactor(ETH): migrate to isOrigin/mechanism * Update data.json w/ bridge Changing the canonical bridge address to the address which ultimately holds the ETH --------- Co-authored-by: BREAD <97642356+0xBreadguy@users.noreply.github.com>
* refactor: migrate remaining tokens to isOrigin/mechanism format - BTC.b: Replace isNative: false with isOrigin: false, add mechanism: mint, keep isOFT: false - USDM: Replace isNative with isOrigin (megaeth: true->true, ethereum: false->false), add mechanism (native/mint), keep isOFT: true on both - USDT0: Replace isNative: false with isOrigin: false, add mechanism: mint, keep isOFT: true - pufETH: Replace isNative with isOrigin (ethereum: true->true, megaeth: false->false), add mechanism (lock/mint), keep isOFT: true on both Completes migration from legacy isNative field to new isOrigin/mechanism format while preserving isOFT fields (LayerZero OFT standard tracking). * Update data.json --------- Co-authored-by: BREAD <97642356+0xBreadguy@users.noreply.github.com>
Contributor
Author
|
I think the CI failure is a pre-existing upstream issue. Can you verify @SilasZhr? |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Refactoring remaining token addresses to the new property naming structure