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.
| Question | Taproot Fields for PSBT |
|---|---|
| What the text proposes | BIP 371, Taproot Fields for PSBT. The new per-input types are defined as follows: {| ! Name ! ! ! Description ! ! Description ! Versions Requiring Inclusion ! Versions Requiring Exclusion ! Versions Allowing Inclusion |- | Taproot Key Spend Signature | PSBT_IN_TAP_KEY_SIG = 0x13 | None | No key data '''Why is there no key data for PSBT_IN_TAP_KEY_SIG '''The signature in a key path spend corresponds directly with the pubkey provided in the output script. |
| Who may write | Ava Chow |
| What is settled | The new per-input types are defined as follows: {| ! Name ! ! ! Description ! ! Description ! Versions Requiring Inclusion ! Versions Requiring Exclusion ! Versions Allowing Inclusion |- | Taproot Key Spend Signature | PSBT_IN_TAP_KEY_SIG = 0x13 | None | No key data '''Why is there no key data for PSBT_IN_TAP_KEY_SIG '''The signature in a key path spend corresponds directly with the pubkey provided in the output script. |
| Load-bearing assumption | A signature scheme is not a privacy system. It hides the signer only if the protocol says so. |
| What this library says afterwards | Status in the source: Deployed. A reading of the public specification, not a copy of it and not a certification. |
| Rights | Official external source only |