bitcoin/bips
1
0
Fork 0
mirror of https://github.com/bitcoin/bips.git synced 2026-05-18 16:59:30 +00:00
Code Issues Releases Wiki Activity

BIP-0322: link to later sections for clarity

Browse Source
This commit is contained in:
Oli
2026-05-08 09:22:37 +02:00
parent ad0e02f746
commit 52b2e6d81b
1 changed files with 6 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
bip-0322.mediawiki
View File

@@ -34,7 +34,8 @@ interoperability with existing signing hardware, we also define a signature mess
resembles a Bitcoin transaction (except that it contains an invalid input, so it cannot be spent on resembles a Bitcoin transaction (except that it contains an invalid input, so it cannot be spent on
any real network). any real network).
The Proof of Funds variant allows demonstrating control of a set of UTXOs. The [[#full-proof-of-funds|Proof of Funds]] variant allows demonstrating control
of a set of UTXOs in addition to the message being signed.
The list of UTXOs may or may not be related to the address being signed with (the The list of UTXOs may or may not be related to the address being signed with (the
<code>message_challenge</code>). <code>message_challenge</code>).
But in any case, the UTXO list does not aim to prove completeness (e.g. it does NOT mean: But in any case, the UTXO list does not aim to prove completeness (e.g. it does NOT mean:
@@ -98,7 +99,7 @@ UTXOs.
|} |}
<sup>1</sup>: Possible on a technical level but should NOT be used anymore in the context of this <sup>1</sup>: Possible on a technical level but should NOT be used anymore in the context of this
BIP.<br/> BIP, see section [[#legacy|Legacy]] below.<br/>
<sup>2</sup>: Excluding time lock scripts. <sup>2</sup>: Excluding time lock scripts.
Signers must prefix the signature with the variant that was used to create the signature. Signers must prefix the signature with the variant that was used to create the signature.
@@ -447,15 +448,15 @@ A '''transaction finalizer''' of a BIP-0322 PSBT must follow these steps:
They finalize the PSBT as specified in [[bip-0174.mediawiki#input-finalizer|BIP-0174]]. They finalize the PSBT as specified in [[bip-0174.mediawiki#input-finalizer|BIP-0174]].
</li> </li>
<li> <li>
They then encode the signature following the same steps as described in They then encode the signature following the same steps as described in [[#signing|Signing]]
[[bip-0322.mediawiki#signing|Signing]] above. above.
</li> </li>
</ol> </ol>
== Compatibility == == Compatibility ==
This specification is backwards compatible with the legacy signmessage/verifymessage specification This specification is backwards compatible with the legacy signmessage/verifymessage specification
through the special case as described above. through the special case [[#legacy|as described above]].
To support backward compatibility with implementations of this BIP before it was finalized, a To support backward compatibility with implementations of this BIP before it was finalized, a
verifier might assume the ''simple' variant in the absence of a prefix. verifier might assume the ''simple' variant in the absence of a prefix.