Skip to content

Compare

Four documents, the same five questions.

No throughput league table and no yield. The cells are what this library is willing to say about the text.

QuestionMuSig2 PSBT Fields
What the text proposesBIP 373, MuSig2 PSBT Fields. The new per-input types are defined as follows: {| ! Name ! ! ! ! Versions Requiring Inclusion ! Versions Requiring Exclusion ! Versions Allowing Inclusion |- | rowspan="2"|MuSig2 Participant Public Keys | rowspan="2"| PSBT_IN_MUSIG2_PARTICIPANT_PUBKEYS = 0x1a | | | rowspan="2"| | rowspan="2"| | rowspan="2"| 0, 2 |- | The MuSig2 aggregate public key (compressed) '''Why the compressed aggregate public key instead of x-only?''' [[bip-0032.mediawiki|BIP 32]] public keys can be derived from a [[bip-0327.mediawiki|BIP 327]] MuSig2 aggregate public key (see: [[bip-0328.mediawiki|BIP 328]]).
Who may writeAva Chow
What is settledThe new per-input types are defined as follows: {| ! Name ! ! ! ! Versions Requiring Inclusion ! Versions Requiring Exclusion ! Versions Allowing Inclusion |- | rowspan="2"|MuSig2 Participant Public Keys | rowspan="2"| PSBT_IN_MUSIG2_PARTICIPANT_PUBKEYS = 0x1a | | | rowspan="2"| | rowspan="2"| | rowspan="2"| 0, 2 |- | The MuSig2 aggregate public key (compressed) '''Why the compressed aggregate public key instead of x-only?''' [[bip-0032.mediawiki|BIP 32]] public keys can be derived from a [[bip-0327.mediawiki|BIP 327]] MuSig2 aggregate public key (see: [[bip-0328.mediawiki|BIP 328]]).
Load-bearing assumptionA signature scheme is not a privacy system. It hides the signer only if the protocol says so.
What this library says afterwardsStatus in the source: Complete. A reading of the public specification, not a copy of it and not a certification.
RightsOfficial external source only