stacks-core icon indicating copy to clipboard operation
stacks-core copied to clipboard

Stacker liveness enforcement in the stacks-node

Open kantai opened this issue 2 years ago • 2 comments

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).

kantai avatar Jan 16 '24 16:01 kantai

Depends on info from discussion https://github.com/stacks-network/stacks-core/discussions/4195

AshtonStephens avatar Jan 16 '24 16:01 AshtonStephens

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).

kantai avatar Apr 24 '24 15:04 kantai

Depends on info from discussion https://github.com/stacks-network/stacks-core/discussions/4195

gofaraway002 avatar Jun 06 '24 20:06 gofaraway002

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)?

andrerserrano avatar Jun 27 '24 19:06 andrerserrano