Fix parsing both tokens with 0x prefix and without it #1869
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
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.
Why this change is needed
This is a temporary fix that enables local testnet again.
In a separate PR I will provide full solution with consistent usage of
0xprefix and fixed gateway issues.Local testnet was successfully started with this branch: https://github.com/ten-protocol/ten-test/actions/runs/8543430314/job/23407243846
What changes were made as part of this PR
accept both tokens with
0xprefix and without it.PR checks pre-merging
Please indicate below by ticking the checkbox that you have read and performed the required
PR checks