checksummed-tokens #466
Open
checksummed-tokens #466
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
ines-SKALE
requested review from
dmytrotkk,
DmytroNazarenko and
yavrsky
as code owners
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
dmytrotkk
requested changes
Feb 25, 2025
| @@ -49,7 +50,7 @@ export default function Tokens(props: { | |||
| <CopySurface | |||
| className={cls(styles.fullHeight)} | |||
| title={`${tokenSymbol.toUpperCase()}`} | |||
| value={tokenData.address} | |||
| value={getAddress(tokenData.address)} | |||
There was a problem hiding this comment.
we also need the same checksummed addresses for wrapped tokens
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.
Before this PR, when copying tokens from the frontend they were not always checksummed.
Now, with this small PR made for Portal 4.1, this issue (#454) is resolved.