-
Notifications
You must be signed in to change notification settings - Fork 574
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
adds multisig/aggregateSigningShares RPC #4677
Conversation
takes a publicKeyPackage, an unsignedTransaction, a signingPackage for that transaction, and a list of signatureShares for that signingPackage uses UnsignedTransaction.signFrost to aggregate the signatureShares, sign the transaction, and produce a signed transaction returns a signed transaction serialized as hex
ironfish/src/rpc/clients/client.ts
Outdated
@@ -821,6 +823,15 @@ export abstract class RpcClient { | |||
}, | |||
} | |||
multisig = { | |||
aggregateSignatureShares: ( |
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.
We should either rename this to match signFrost
or rename signFrost
to match this.
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.
Merging as is for now, we'll settle on naming in a followup
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, we just need to rename this (or signFrost) and in a subsequent PR write integration test like you suggested offline.
s/Signature/Signing/
Summary
takes a publicKeyPackage, an unsignedTransaction, a signingPackage for that transaction, and a list of signatureShares for that signingPackage
uses UnsignedTransaction.signFrost to aggregate the signatureShares, sign the transaction, and produce a signed transaction
returns a signed transaction serialized as hex
Testing Plan
RPC integration test will be added in a followup PR
Documentation
Does this change require any updates to the Iron Fish Docs (ex. the RPC API
Reference)? If yes, link a
related documentation pull request for the website.
Breaking Change
Is this a breaking change? If yes, add notes below on why this is breaking and
what additional work is required, if any.