The upliftFeeBps variable in UpliftOnlyExample lacks a setter function, making it immutable after contract deployment despite the implementation suggesting it should be mutable (Storing data in poolsFeeData so that future upliftFeeBps doesn't retroactively affect them)
The contract stores upliftFeeBps in poolsFeeData for each position, indicating an intention to allow fee changes while preserving historical rates for existing positions. However, there is no function to modify the upliftFeeBps state variable after deployment.
Contract owner cannot adjust uplift fees to respond to market conditions
Contradicts design intention to allow fee modifications
Manual Review
Add an owner-controlled setter function similar to setHookSwapFeePercentage():
Likelihood: Low, it cannot be changed but should not need to be changed often. Impact: Low, the code still works with fees.
The contest is live. Earn rewards by submitting a finding.
This is your time to appeal against judgements on your submissions.
Appeals are being carefully reviewed by our judges.