You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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:
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.
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
The text was updated successfully, but these errors were encountered: