Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Allow fractional relocking #122

Open
p-offtermatt opened this issue Sep 23, 2024 · 0 comments
Open

Allow fractional relocking #122

p-offtermatt opened this issue Sep 23, 2024 · 0 comments
Labels
priority: nice-to-have Features that are nice to have, but that ultimately should not block deployment.

Comments

@p-offtermatt
Copy link
Member

Right now, it's possible to just refresh an existing lock. However, users may want to lengthen the lock only for part of their tokens, and may want the other tokens to stay locked with the existing lock duration.

This need seems best served by a new parameter in RefreshLockDuration, like AmountToKeepInOldLock. If this is 0, the behaviour is as-now when refreshing locks. If it is >total_locked_in_this_lock, the lock will stay unaffected.
Otherwise, there will be two locks, the old lock with AmountToKeepInOldLock tokens left, and a new lock with the remaining tokens.
@p-offtermatt p-offtermatt added priority: nice-to-have Features that are nice to have, but that ultimately should not block deployment. and removed v2 labels Oct 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
priority: nice-to-have Features that are nice to have, but that ultimately should not block deployment.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@p-offtermatt