Add TRUE token to base sepolia #937
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
wbnns
approved these changes
Sep 19, 2024
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
I'm currently working on a new project that needs to bridge our own token from sepolia to base-sepolia.
sepolia: https://sepolia.etherscan.io/address/0x90c9155ec3c2c4ad624db896864fc62eb3d62626
base-sepolia: https://sepolia.basescan.org/address/0xfe8b6a4586a67160d27962dc153bf0e7e76fbf68
The token is still in development phase, I'll update the
data.jsonagain once implementation finalized.For now, I just want to make sure the bridge working as expected.
Tests
only on testnet
Additional context
Add any other context about the problem you're solving.
Metadata