Feat: Locked Staking #169
Draft
Feat: Locked Staking #169
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
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.
This is an Initial implementation of
locked staking. This PR introduces:The factory creates an instance by creating a new storage contract and proxying all the logic to the template contract (logic contract). Moreover it allows the factory admins to extend any staking based future strategy by deploying a new template, then publish it on the factory.
The template allows user to stake automatically prior creating the new instance. This means that users can't have multiple locked stakes within the same contract, however to do that user has to create a new instance. Moreover the new created instance only owned by the user's wallet. Also the lockup period is variable so it can managed by the frontend.