feat: add LiquidityManager errors and constant variables #48
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.
Pull Request
Summary
This PR enhances
LiquidityManagerV2by introducing new error handling and adding important constant variables to improve safety, clarity, and maintainability.Changes
Errors
LiquidityManager__InvalidTickRangeto enforce tick validation.LiquidityManager__LiquidityLockedto prevent operations during locked states.Constants
MAX_LIQUIDITY_THRESHOLD = 1000 * 1e6→ cap for liquidity.MIN_LIQUIDITY_THRESHOLD = 10 * 1e6→ minimum to prevent dust attacks.MAX_VESTING_DURATION = 365 days→ maximum vesting period.MIN_VESTING_DURATION = 30 days→ minimum vesting requirement.SLIPPAGE_PRECISION = 10000→ basis points for slippage control.FEE_PRECISION = 1000000→ precision constant for protocol fees.Motivation
Notes