feat: optimize sync + checkpoint sync v3 + better tracing #135
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.
Motivation
BURN/MINT/SWAP
logs for v3 sync. - Syncing v3 pool tick data properly from a cached checkpoint.Solution
JoinSet
when syncing the Mint/Burn/Swap logs on v3 pools.liquidity, liquidity_gross
toi128
allowing underflow to happen if we hit a burn log before the corresponding mint log. This will yield the same final state when fully synced assuming no overflow on thei128
(unlikely).PR Checklist