Stacker liveness enforcement in the stacks-node
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).
Depends on info from discussion https://github.com/stacks-network/stacks-core/discussions/4195
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).
Depends on info from discussion https://github.com/stacks-network/stacks-core/discussions/4195
Hi team - what was the solution here? What are the exact penalties signers should expect (i.e. rewards will be halted after a signer is down for X blocks)?