Fix ticks prices decimals #129
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@NicolasMahe is attempting to deploy a commit to the Uniswap Team on Vercel. A member of the Team first needs to authorize it. |
Mama54y
approved these changes
May 2, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR fixes the number of decimals used to calculate the ticks' prices.
It was harcoded to use only 4 decimals, now it uses the token's decimals.
The tick's
price1is used to calculate the TVL lockedamount0. The loss of precision is causing theamount0to be incorrectly calculated.https://github.com/Uniswap/uniswap-v3-info/blob/93eaaf001dbcc4981c3605f2ac8ad3593e310f8c/src/components/DensityChart/index.tsx#L162
I also replaced the formatting of prices that used
toLocaleStringwithformatAmount(priceX, 4)