Skip to content
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

Add ERC721 and ERC20 to hardcoded named accounts #798

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

buberdds
Copy link
Contributor

@buberdds buberdds commented Nov 12, 2024

In Explorer we want to show token names instead of contract addresses in multiple places

  • moved hardcoded addresses to named-accounts
  • split paratime files into runtime specific
  • get verified contracts from evm_tokens API endpoint

@buberdds buberdds changed the title Mz/named acc Add ERC-721 and ERC-20 to hardocded named accounts Nov 12, 2024
@buberdds buberdds changed the title Add ERC-721 and ERC-20 to hardocded named accounts Add ERC721 and ERC20 to hardcoded named accounts Nov 12, 2024
"Description": "ERC20"
},
{
"Name": "YuzuSwap LP Token",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why do we have multiple "YuzuSwap LP Token" 's/"Wrapped ROSE"... here? I thought we would just have "trusted"/"official" addresses, not the list of all verified tokens.

If we have a list of all verified contracts, can't we get that via the existing API? (

/{runtime}/evm_tokens:
). This seems just a duplicate of that one, with the downside that this one needs to be maintained manually.

"Description": "ERC20"
},
{
"Name": "Sapphire Inu",
Copy link
Member

@ptrus ptrus Nov 12, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same question here; I thought we would just have a couple of known/trusted addresses here, not all contracts.
Some of the token names are quite apparently non-serious/spam and don't belong in any "official list" like this one.

Also this seems really hard to maintain, whats the benefit vs using the evm_tokens API?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

agree, lists need more removals. Will try to find someone who can decide which tokens are "trusted" for us.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants