-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enhancement/ Safety level ranking flag to tokens #900
base: v2
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't understand the logic and I think the code can be rewritten to be better
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm, really liked how you optimized for long arrays of tokens
// thus we can't trust it | ||
if (!canTokenBeChecked) return undefined | ||
|
||
Object.values(humanizerInfo.knownAddresses as unknown as HumanizerMeta).some((value) => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
add comment about .some()
doing a break
on return true
and continue
on return false
A new token flag is introduced. It is
safetyLevel
and the values it accepts are:networkId
or even betterchainId