You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On some Pools, especially bigger ones with more than 1,000 initialized Ticks, some Ticks contain incorrect values.
While the values are incorrect in the sense of not representing the actual state of the blockchain, they are still consistent, meaning the 'ZERO_NET' etc. invariants of Pools are still met.
I suspect that some Positions are not correctly indexed.
Steps to reproduce:
Fetch all initialized ticks of a Pool for a specific block with the subgraph, as well as with RPC calls.
Compare the Ticks by tickIdx. The liquidity values will be off in some cases.
Example: USDC/ WETH with LOW fee ( tested for multiple blocks between 17607400 and 17607545):
The text was updated successfully, but these errors were encountered:
On some Pools, especially bigger ones with more than 1,000 initialized Ticks, some Ticks contain incorrect values.
While the values are incorrect in the sense of not representing the actual state of the blockchain, they are still consistent, meaning the 'ZERO_NET' etc. invariants of Pools are still met.
I suspect that some Positions are not correctly indexed.
Steps to reproduce:
Example: USDC/ WETH with LOW fee ( tested for multiple blocks between 17607400 and 17607545):
The text was updated successfully, but these errors were encountered: