-
Notifications
You must be signed in to change notification settings - Fork 15
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.
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
spec: Staking module #784
Comments
I guess the requirement comes from node integration. If so, it seems super high priority, right? |
In an initial phase we should have basic spec and implementation for our test apps. In the next 1-2 weeks we will know more about the needs for starknet node integration, once we sync with the teams and start the work. |
By staking module, do you mean the mechanism used to map actual stake to the voting power of validators? Does it include the reset protocol and similar stuff? Where would the stake come from: L1 or L2? |
Yes. Should include stake/unstake operations that eventually modify the voting power, epoch configuration and anything else required for basic functionality.
Maybe not initially but we definitely want to do this in a next phase, soon after. |
Create a minimal spec for a staking module. cc @josef-widder
The text was updated successfully, but these errors were encountered: