-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: Signer message type definition #126
feat: Signer message type definition #126
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good.
pub enum Payload { | ||
SignerDepositDecision(SignerDepositDecision), | ||
SignerWithdrawDecision(SignerWithdrawDecision), | ||
StacksTransactionSignRequest(StacksTransactionSignRequest), | ||
StacksTransactionSignature(StacksTransactionSignature), | ||
BitcoinTransactionSignRequest(BitcoinTransactionSignRequest), | ||
BitcoinTransactionSignAck(BitcoinTransactionSignAck), | ||
/// Contains all variants for DKG and WSTS signing rounds | ||
WstsMessage(wsts::net::Message), | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this so that we can deserialize responses into one thing?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure I understand the question, but if you're wondering why I've chosen to represent the payload as an enum it's just to be able to represent all different types of payloads within the single SignerMessage
struct.
closes #104
This PR introduces the base message type according to the signer communication LLD, and paves the way for future work on the signer message variants and network.