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.

QuestionPay-to-contract tweak fields for PSBT
What the text proposesBIP 372, Pay-to-contract tweak fields for PSBT. The new per-input type is defined as follows: {| ! Name ! ! ! Description ! ! Description ! Versions Requiring Inclusion ! Versions Requiring Exclusion ! Versions Allowing Inclusion |- | P2C Key Tweak | PSBT_IN_P2C_TWEAK = 0x19 | | 33 bytes of compact public key serialization specifying to which keys the P2C tweak may be applied (i.e.
Who may writeMaxim Orlovsky
What is settledThe new per-input type is defined as follows: {| ! Name ! ! ! Description ! ! Description ! Versions Requiring Inclusion ! Versions Requiring Exclusion ! Versions Allowing Inclusion |- | P2C Key Tweak | PSBT_IN_P2C_TWEAK = 0x19 | | 33 bytes of compact public key serialization specifying to which keys the P2C tweak may be applied (i.e.
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: Draft. A reading of the public specification, not a copy of it and not a certification.
RightsOfficial external source only