This repository has been archived by the owner on Feb 27, 2023. It is now read-only.
Improve multi-recipient/multi-sig handling #111
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Improvements to multi-recipient/multi-sig handling.
Decrypt
andVerify
.VerifyMulti
andDecryptMulti
functions for old use-cases.The new
VerifyMulti
andDecryptMulti
functions will return the index of the recipient/signature that has been verified, along with the header or signature object. This ensures that callers don't accidentally verify one signature but then read headers from another, as the oldVerify
orDecrypt
didn't say which recipient/signature ended up being valid.Because this is a subtle API change, it will likely be released as
v1.1.0
once merged into thev1
branch. I'm not aware of any public projects using this library that depend on multi-sig so I think it's acceptable to still call thisv1
.