Skip to content

Conversation

@zhiqiangxu
Copy link

@zhiqiangxu zhiqiangxu commented Jul 17, 2025

computeSwapStep doesn't necessarily compute result of a swap within a single tick, instead should be within a tick boundary.

As sqrtRatioTargetX96 may be the price of the next initialized tick(LP liquidity boundary), which may be well beyond a single tick.

computeSwapStep only cares about boundary because liquidity only changes across a boundary, or say, the liquidity doesn't change for intermediate ticks.

@stale
Copy link

stale bot commented Nov 27, 2025

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

@stale stale bot added the wontfix label Nov 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants