We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Im currently using sdk and was working fine, but now seems there is sort of cache and portfolio data doesn’t match the one on Zerion api
Also doing a research saw the rest api is also having the same problem https://api.cryptostats.community/api/v1/treasuries/currentTreasuryPortfolio wrong data on api or using sdk
from the adapter editor all seems fine and matching zerion
https://zerion-api.vercel.app/api/portfolio/0x78605Df79524164911C144801f41e9811B7DB73D
Any idea what could be causing this?
The text was updated successfully, but these errors were encountered:
ok going deep on this found the api used https://github.com/crypto-stats/zerion-api-proxy/blob/master/pages/api/portfolio/%5Baddresses%5D.ts#L27 and seems is catching for 12 hours which seems a lot for valued expressed in USD as the case of portfolios.
Looking the zerion api rate limits seems they don't have a rate limit, so will be possible to change this at least to 1 hour to actually have accurate data on the adaptor? https://docs.zerion.io/websockets/api-faq#1.-is-there-a-rate-limit-on-the-api
Sorry, something went wrong.
No branches or pull requests
Im currently using sdk and was working fine, but now seems there is sort of cache and portfolio data doesn’t match the one on Zerion api
Also doing a research saw the rest api is also having the same problem https://api.cryptostats.community/api/v1/treasuries/currentTreasuryPortfolio
wrong data on api or using sdk
from the adapter editor all seems fine and matching zerion
https://zerion-api.vercel.app/api/portfolio/0x78605Df79524164911C144801f41e9811B7DB73D
Any idea what could be causing this?
The text was updated successfully, but these errors were encountered: