jferrant

SDK: Move stacks_client.rs code to the SDK

1

HTTP client code for interacting with a stacks node should be pulled into the SDK, spruced up, and generalized such that a user could modify its signing algorithm for example.

Closes https://github.com/stacks-network/stacks-core/issues/4784 I made the process_event logic take a generic type which implements StacksMessageCodec to enable having different message types for v1 and v2 without borking up code in each...

Closes https://github.com/stacks-network/stacks-core/issues/4783 Didn't want to do too many changes at once in case I inadvertently broke things. I am sure there is some further break down that could be done...

Closes https://github.com/stacks-network/stacks-core/issues/4785 I have yet to add tests but please add some comments.

The necesesary types would include MinerMessages, BlockValidationResponses, StatusCheck, NewBurnBlock, and BlockSignature

Would be good to separate the v1 message types from the v0 message types if possible. Otherwise, just add this new message type to the existing enum and ignore it...

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

Currently this behaviour has been observed: Signers N-1 come online. Read stackerdb. See nothing. do DKG, Signers N come online. Read stackerdb. See nothing. do DKG Signers N+1 come online....

First pass focusing on warn and info level logging. Couple debugs

3

I have been tearing my hair out trying to compare across log lines without knowing what is a burn header hash vs stacks block hash vs consensus hash etc. This...