(NOBIDS) fix scam token detection #2773
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
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.
Previously we used
confusables.IsDangerousto detect tokens with weird token symbols. If you look into the code of that function, you'll see it checksisConfusable && isMixedScript, i.e. whether the string is confusable with Latin letters AND uses symbols from multiple scripts. If the token symbol entirely consists of symbols in another script (e.g. https://beaconcha.in/token/0xb4db731771601654322c1a469e747a69363813e7 is "ЕТН", which is actually from the Cyrillic script) this detection failed.With this PR, we will now check
isConfusable || isMixedScript, which will detect this token as sus.