Submitted by broccoli
The function RangeFeeGrowth (ConcentratedLiquidityPool.sol#L601-L633) would revert the transaction in some cases.
When a pool cross a tick, it only updates either feeGrowthOutside0 or feeGrowthOutside1. Ticks.sol#L23-L53
RangeFeeGrowth calculates the fee as follow:
feeGrowthBelow + feeGrowthAbove is not necessary smaller than _feeGrowthGlobal. Please see POC.
Users can not provide liquidity or burn liquidity. Fund will get stocked in the contract. I consider this is a high-risk issue.
Hardhat
Its either modify the ticks algo or RangeFeeGrowth. The quick-fix I come up with is to deal with the fee in RangeFeeGrowth. However, I recommend the team to go through ticks logic again.
sarangparikh22 (Sushi) disputed:
alcueca (judge) commented:
sarangparikh22 (Sushi) confirmed:
