ZKsync: provide public actions for fetching token addresses on L1 and L2 chains #3133
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
🦋 Changeset detectedLatest commit: fdc3af8 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
@danijelTxFusion is attempting to deploy a commit to the Wevm Team on Vercel. A member of the Team first needs to authorize it. |
danijelTxFusion
force-pushed
the
zksync/l1-l2-token-addresses
branch
2 times, most recently
from
fe04f25 to
2873078
Compare
danijelTxFusion
force-pushed
the
zksync/l1-l2-token-addresses
branch
from
2873078 to
fdc3af8
Compare
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.
To enable seamless bridging of assets across chains, it is necessary to retrieve the corresponding token address on the other chain for a given asset. This involves implementing two public actions to facilitate the mapping between L1 and L2 token addresses.
Implementend the following public actions:
getL1TokensAddress()- returns the L1 token address equivalent for a L2 token address.getL2TokensAddress()- returns the L2 token address equivalent for a L1 token address.