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.

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

Stacker liveness enforcement in the stacks-node #4248

Open
kantai opened this issue Jan 16, 2024 · 2 comments
Open

Stacker liveness enforcement in the stacks-node #4248

kantai opened this issue Jan 16, 2024 · 2 comments

Comments

@kantai
Copy link
Member

kantai commented Jan 16, 2024

The stacks-node will take the signer participation bit vectors as a given from the signer set (#4241), but it does need to implement the punishment for non-participation. As discussed in the SIP, this should take the form of losing PoX rewards, but the exact design of this still needs to be designed and implemented.

Because it impacts a block-commit's outputs, this means that block-commits cannot be validated without the data that goes into the punishment (the prior stacks block's bit vectors).

@AshtonStephens
Copy link
Collaborator

Depends on info from discussion #4195

@kantai
Copy link
Member Author

kantai commented Apr 24, 2024

This should be implemented with the minimal consensus impact: the bitvec should be enforced on the next block (i.e., the sortition can do a single look back for discovering punishment).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Status: 📋 Backlog
Development

No branches or pull requests

3 participants