-
Notifications
You must be signed in to change notification settings - Fork 741
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
totalSupply Function Does Not Return Expected Results #139
Comments
I'll inspect this one further. I am noticing that the totalSupply is incorrect on a pool that I'm testing on the hosted service, however the decentralized network subgraph seems to give me a correct version. |
@PaladinDotEth with the resync, this should be resolved. Can you double check that you're now receiving the expected values? |
@Data-Nexus query: result: token with correct totalSupply from etherscan: |
Interesting, I assumed you were interested in the pool's total supply. Honestly I wouldn't use the token.totalSupply since this is fetched at the time the token is first utilized in the subgraph, and does not change over time. So for WETH, it would fetch the total supply at the time the first WETH pool was created, as more ETH gets wrapped this will not change the token's totalSupply. If the token was minted with a hard cap, it'd probably be fine. |
I am interested in the tokens total supply, i get the Liquidity through "totalLiquidity". I need the total supply for each Token i fetch for my Project, so it would be really nice if one could fix it. Edit: V3 shows the right totalSupply |
Exactly what I just noticed. TokenSupply is all wrong |
I'm currently utilizing the version hosted at uniswap-v2-dev, but I'm consistently receiving incorrect values '15640' or '14448.' Are there alternative versions available for use?
The text was updated successfully, but these errors were encountered: