@ProgrammerSmart@return It represents the ratio of "virtual" reserves. If you check the contract on Etherscan you see that the actual ratio can be anything.
Your transaction can still be sandwiched together with others creating a high price impact for the bundle trade. This is why the transaction I did is still stupid. Saying slippage matters only when price impact is greater than the pool's fee would be a good rule of thumb.
If you're worried about getting sandwiched but your price impact is less than 0.6% (ie most people who worry) - you don't have to be as the chances of that happening are practically 0.
If you're a big trader with a price impact >0.6% you should set your slippage closer to 0 and then send the transaction with a high max fee so it gets mined in the next few blocks even if the base fee increases (๐1559)
@NoahZinsmeister@SushiIntern@josephdelong@SushiSwap The thing is even if you didn't open the v3-core repo and just implemented the algorithm according to the whitepaper you would come up with the exact same function for calculating range fee growth.