AddCommittedToken was edited to avoid amount duplicate on Lockup #476
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Wgil
requested changes
Apr 30, 2024
|
Lets hold this until local dev is back to normal |
Wgil
approved these changes
May 14, 2024
cosmic-vagabond
approved these changes
May 16, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
We have a problem when the user joins a pool for a second time or higher because the lockups amount is doubled. This causes a desynchronization between the amount and the lockups that allow an unavailable amount to be withdrawn
What has Changed?
Function AddCommittedTokens was edited to resolve the problem, in line 54 there was a problem because each time that adds a new committed the amount was duplicated.