Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
multisig - signature format #23
For storing signatures. Should be analogous to
Note: this is just a quick writeup, up for debate.
Following the usual structure:
Signature itself is defined as:
"multisig" is better known as an obvious (and general) solution to threshold signatures. A multisig signature consists of "multiple signatures". I.e. Alice and Bob within a group of Alice, Bob, Carol, Dave; co-signed an object on behalf of the group - not just themselves.
Multisig is commonly referenced within the cryptocurrency community.
FWIW: An ideal threshold signature (like Schnorr signatures; I.e. ed25519) is identical to a signature form a single party, requiring no difference in the representation nor verification process.
If you plan to support "multisig (list)" in "multisig (this project)", you will need to support .. lists. Alternatively you may consider each signature independent and leave the rest to the application.
Unfortunately, I do not have any alternative naming suggestions for identifying signatures, especially within this collection of "multi*".
Naming problems aside; I would really like to see this distinct kind of multiformat but in addition to something like
Regarding the structure, I'd propose the following:
Where signature is the signed bytes of the hash defined by
The format and padding information would yield distinct DSA types such as:
Regarding naming: given the specific attention to signatures and key material (ipfs/specs#58) and the inevitable attention that encryption will draw soon, it may be worthwhile to consider a