mirror of
https://github.com/bitcoin/bips.git
synced 2026-06-08 17:25:25 +00:00
BIP-0322: remove address optionality for PoF
This is cleaning up an artifact that was left over from #1352. The alternative to removing the optionality of the address would be to assume OP_TRUE in case of an empty address. But that sounds like it could open up any number of potential vulnerabilities. And a user still has the ability to use an OP_TRUE script in a p2wsh or p2tr address.
This commit is contained in:
@@ -219,7 +219,7 @@ output with prevout <code>000...000:FFFFFFFF</code> does not exist.
|
||||
|
||||
=== Verification ===
|
||||
|
||||
A validator is given as input an address ''A'' (which may be omitted in a proof-of-funds), signature
|
||||
A validator is given as input an address ''A'', signature
|
||||
''s'' and message ''m'', and outputs one of three states:
|
||||
|
||||
<ul>
|
||||
@@ -489,10 +489,12 @@ and many others for their feedback on the specification.
|
||||
|
||||
== Changelog ==
|
||||
|
||||
* '''1.0.1''' (2026-06-04):
|
||||
** Clarify that the message_challenge is ''not'' optional for "Proof of Funds".
|
||||
* '''1.0.0''' (2026-04-15):
|
||||
** Mark Complete
|
||||
** Breaking change: Add human-readable prefix to encoded signature
|
||||
** Breaking change: format of "Proof of Funds" signatures to be base64-encoded finalized PSBT
|
||||
** Breaking change: Format of "Proof of Funds" signatures to be base64-encoded finalized PSBT
|
||||
** Add new PSBT global field for PSBT-based signing
|
||||
* '''0.0.1''' (2018-09-10):
|
||||
** Proposed as draft
|
||||
|
||||
Reference in New Issue
Block a user