Nakamoto Signer[3.0] - Update the current signer module to signer_v1and create a new signer_v0 module that has an analogous Signer struct

[saralab]

stacks-signer

The signer module should become signer_v1. A new signer_v0 module should be created that has an analogous Signer struct. This Signer struct’s main point of entry should be process_event, much like the current Signer struct. It will need to handle MinerMessages, BlockValidationResponse, StatusCheck, and NewBurnBlock.

With the first version, to get to parity with signer_v1, signer_v0::Signer only needs to read miner messages for block proposals, submit the proposal to the validation endpoint, and broadcast a signature over StackerDB.

This will require some refactoring of the message code in libsigner (to support the new “block signature” message), as well as a routine for performing the signature (this should be roughly identical to the code the miner uses to sign a block).

Tasks

Beta Give feedback

1. Nakamoto Signer[3.0] Create new v0 and v1 modules to seperate signer code and place existing code in v1 module #4783
   3.0 3.0-Signer 3.0-must locked nakamoto +5
   
2. Nakamoto Signer[3.0] Create new block signature message type for v0 signer #4784
   3.0 3.0-Signer 3.0-must locked nakamoto +5
   
3. Nakamoto Signer[3.0] Create a new process_event path for v0 signer to handle v0 message types #4785
   3.0 3.0-Signer 3.0-must locked nakamoto +5
   

[blockstack-devops]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.