fix(StakeManager): add checks for whether lockup period is in range #39
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.
This commit introduces
MIN_LOCKUP_PERIOD
andMAX_LOCKUP_PERIOD
and makes use of them withinStakeManager.stake()
andStakeManager.lock()
accordingly.When users deposit tokens into their vault via
stake()
, they can provide an optional lockup time. If the value is0
it implies users do not want to lock their stake.If the value is
> 0
it has to be within the range ofMIN_LOCKUP_PERIOD
andMAX_LOCKUP_PERIOD
.Properly addresses #15
Checklist
Ensure you completed all of the steps below before submitting your pull request:
forge snapshot
?pnpm lint
?forge test
?