jferrant

[Nakamoto] stacks-signer needs track processed blocks responses, block requests, and block sign requests

5

Stacks-signer currently will just process blocks as they are received and trigger signing rounds accordingly. it does not currently check if it has already processed a particular block response (received...

Audit: It might be worthwhile to add verification of all received messages that they come either from expected miner pub keys or registered signer pub keys. Stackerdb already does write...

There are a few DKG scenarios that do not seem to be properly tested: - If DKG fails due to a timeout (i.e. non responsive signers), there should be a...

Closes https://github.com/stacks-network/stacks-core/issues/4502

[stacks-signer] signers should not wait forever for a vote to be successful and should retrigger DKG if a certain timeout is exceeded

2

Currently signers just assume that if a threshold weight of responses have not been received for a DKG vote round that they will eventually show up. This could not be...

[stacks-signer] Enable support for HTTPS with pinned certificate throughout the Stacks signer

1

The stacks node itself does not use HTTPS however a user may want to set up a more secure environment and require a certificate to communicate to and from. Enable...

Nakamoto Signer[3.0] - stacks-signers should resend their messages if no response is seen within a given timeout

1

Currently if a coordinator successfully sends a message to stackerdb, it assumes all listening parties have received it and does not ever resend. It would be good if a coordinator...

Audit suggestion: Much of the stacks-signer design is written around running a local stacks node. It would be good to print a log warning to make this clear to prevent...

Nakamoto Signer[3.0] - A signer must be able to save multiple DKG aggregate key round states and load it where appropriate

2

See: https://github.com/stacks-network/stacks-core/blob/5d2cbdd1ab6bd6cfde8f4528eb5fae5777037af5/stacks-signer/src/signer.rs#L1372 If signers see that a threshold has been reached and no approved key set, they may trigger a new DKG round. However, the key could have been approved...

Currently there is no way (Except to use Hiro's extended API) to retrieve the current transactions sitting in the mempool for a specific address. This makes it difficult to determine...