-
Notifications
You must be signed in to change notification settings - Fork 63
feat: asset tracker now uses local cache before fetching asset metadata #1539
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
feat: asset tracker now uses local cache before fetching asset metadata #1539
Conversation
|
2527eb3 to
c9d394f
Compare
c9d394f to
7056add
Compare
383085e to
97f8e63
Compare
mkazlauskas
left a comment
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.
Nice work! 🚀
mirceahasegan
left a comment
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.
Fantastic work, @AngelCastilloB
aa886ba to
0fd4b5b
Compare
Context
Everytime a new instance of base wallet the asset tracker will fetch metadata for all known assets in the transaction history. His could be thousands of assets on an active wallet, which could amount to 10 of thousand of fetches during the day.
Proposed Solution
The asset tracker now will fetch new asset metadata only for assets that are present in balance, and only every 7 days (+-2 days of variance to avoid re-fetching them all at once)