Stake locks extracted out of TokenStaking into a library #1888
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 change allows us to save some bytecode space in TokenStaking for top-ups implementation. The contract size went down from
24926
to22409
(-2517
bytes).I have also introduced initTokenStaking function in
initContracts.js
to keep the details aboutTokenStaking
library linking and deployment there and not pollute every unit test with the same logic.Last but not least,
LockUtils
library has been moved to sit next toLocks
library.