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

L2Reward.extendDuration extending expired locking position #109

Closed
has5aan opened this issue May 2, 2024 · 0 comments · Fixed by #110
Closed

L2Reward.extendDuration extending expired locking position #109

has5aan opened this issue May 2, 2024 · 0 comments · Fixed by #110
Assignees
@has5aan
Labels
bug Something isn't working

Comments

@has5aan
Copy link
Member

has5aan commented May 2, 2024

Expected Behavior

L2Reward.extendDuration should consider the date of transaction as the expiry date when extending duration of an expired locking position.

Actual Behavior

Currently the original expiry date of the locking position is being used.

Which version(s) does this affect? (environment, OS, etc...)

lisk-contracts branch main.
@has5aan has5aan self-assigned this May 2, 2024
@has5aan has5aan mentioned this issue May 2, 2024
Merged
@matjazv matjazv added the bug Something isn't working label May 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@has5aan has5aan

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fixes: L2Reward.extendDuration for expired locking positions LiskHQ/lisk-contracts
2 participants
@matjazv @has5aan