[Design]: sBTC Signer Behavior and Communication

[AshtonStephens]

Completing the issue description and arriving at a conclusion is the deliverable of this issue.

Design - sBTC Signer Behavior and Communication

This ticket holds the design of sBTC Signer Behavior and Communication and how it fits into sBTC-v1.

1. Summary

This ticket outlines expectations and message formats for Signer communication.

2. Context & Purpose

For sBTC to be operational, signers must be able to coordinate and sign transactions. This ticket defines how signers are expected to behave in DKG and signing rounds.

Relevant Research Discussions

External Resources

• [Research]: Handling Partially Overlapping Signer Approval Sets #29

3. Design

3.1 Proposed Component Design

Signers communicate through message passing.
In progress...

Message types

The following messages are sent from the coordinator to the signers

DKG messages

DkgBegin {
    dkg_id: u64
}
DkgPrivateBegin {
    dkg_id: u64,
    signer_ids: Vec<u32>,
    key_ids: Vec<u32>,
}
DkgEndBegin {
    // Same as DkgPrivateBegin
}

Signing round messages

NonceRequest {
    dkg_id: u64,
    sign_id: u64,
    sign_iter_id: u64,
    message: Vec<u8>,
}

Transport layer

3.1.1 Design Diagram

3.1.2 Coniderations & Alternatives

3.2 Areas of Ambiguity

---

Closing Checklist

• The design proposed in this issue is clearly documented in the description of this ticket.
• Everyone necessary has reviewed the resolution and agrees with the proposal.
• This ticket has or links all the information necessary to familiarize a contributor with the design decision, why it was made, and how it'll be included.

[netrome]

Superseded by #53