1
0
mirror of https://github.com/bitcoin/bips.git synced 2026-04-13 16:18:40 +00:00

BIP-0322: add format clarification table

This commit adds a table that clarifies what script types are compatible
with what signing variant and also makes more clear what the exact
format for the signatures of the different variants are.
This commit is contained in:
Oli
2026-04-09 12:46:57 +02:00
parent c77a6c5996
commit 4d36f73e7b

View File

@@ -27,6 +27,32 @@ Ultimately no message signing protocol can actually prove control of funds, both
This BIP specifies three formats for signing messages: ''legacy'', ''simple'' and ''full''. Additionally, a variant of the ''full'' format can be used to demonstrate control over a set of UTXOs.
{| class="wikitable"
|- style="font-weight:bold;"
!
! Compatible script types
! Signature format
|-
| Legacy
| <code>P2PKH</code>, <code>P2SH-P2WPKH</code><sup>1</sup>, <code>P2WPKH</code><sup>1</sup>
| compact, public key recoverable ECDSA signature, base64-encoded
|-
| Simple
| <code>P2WPKH</code>, <code>P2WSH</code><sup>2</sup>, <code>P2TR</code><sup>2</sup> <br/>
| witness stack, consensus encoded and base64-encoded
|-
| Full
| <code>all</code>
| full <code>to_sign</code> transaction, consensus and base64-encoded
|-
| Full (PoF)
| <code>all</code>
| full <code>to_sign</code> transaction, consensus and base64-encoded
|}
<sup>1</sup>: Possible on a technical level but should NOT be used anymore in the context of this BIP.<br/>
<sup>2</sup>: Excluding time lock scripts.
=== Legacy ===
New proofs should use the new format for all invoice address formats, including P2PKH.