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

Store token details from Token registry #184

Open
satran004 opened this issue May 7, 2024 · 1 comment
Open

Store token details from Token registry #184

satran004 opened this issue May 7, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@satran004
Copy link
Member

Some users may need token details such as logo and decimals. It would be beneficial if the LS could prefetch this data at regular intervals and store it in a separate table. Most likely, this will be another service or part of the aggregation app.

  • There will be a 1:1 relation to the multi_asset table that stores logo, decimals, URL, and description.
  • It should detect if it's a CIP68 token.

This functionality can also be added to Yaci Store if other projects want to use this component as library. We will make this decision during implementation

@satran004 satran004 added the enhancement New feature or request label May 7, 2024
@Godspeed-exe
Copy link

Today we have db-sync that runs:

  • stand alone
  • under graphql
  • under Rosetta

But only GraphQL has this backend service that sync data from the Token Registry.
Rosetta users do not have this data
Standalone db-sync users do not have this data.

This leads to:

  • external entities having to query (and sometimes hammer - cause more resource consumption) the Token Registry
  • external entities not being aware of CIP68 standards and this ignoring / leaving out these tokens.

Us implementing support for these would have several benefits in terms of:

  • Token Registry API consumption
  • Increase ease of adoption

Let me know if you have any questions! <3

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

No branches or pull requests

2 participants