Find lower tick bound for canonical ticks #5525
Closed
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.
Part of: #5524
What is the purpose of the change
This PR demonstrates the minimum tick at which the tick to sqrt price conversion loses monotonicity due to precision.
Note that this is distinct from inherent non-monotonicity in
ApproxRoot
(#5517), which comes up at different values and requires a separate solution (likely related to rounding/guaranteeing some property about output)General conclusion: canonical ticks seem to start mattering at tick
-108000000
, which corresponds to a min spot price of10^-12
Testing and Verifying
N/A
Documentation and Release Note
Unreleased
section ofCHANGELOG.md
?Where is the change documented?
x/{module}/README.md
)