Skip to content

BIP-322 nit fixes #2162

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jonatack merged 1 commit into from
May 19, 2026
Merged

BIP-322 nit fixes #2162

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions bip-0322.mediawiki
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -167,7 +167,7 @@ A ''full'' signature consists of the variant-prefixed (<code>ful</code>) base64-

=== Full (Proof of Funds) ===

The [[#full-proof-of-funds|Proof of Funds]] variant extends the basic scheme: in addition to signing
The Proof of Funds variant extends the basic scheme: in addition to signing
Copy link
Copy Markdown
Member

@jonatack jonatack May 19, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Right, the link here no longer makes sense since this sentence was moved to the start of the section.

a message under a single address's key, the signer proves control over an arbitrary set of UTXOs.
This UTXO set is chosen freely by the signer and MAY be associated with the signing address
(the <code>message_challenge</code>). For example, it may consist of outputs paid to that address,
Expand Down Expand Up @@ -260,7 +260,7 @@ Validation consists of the following steps:
# Check the '''upgradeable rules'''
## The version of <code>to_sign</code> must be 0 or 2.
## The use of NOPs reserved for upgrades is forbidden.
## The use of Segwit versions greater than 1 are forbidden.
## The use of Segwit versions greater than 1 is forbidden.
## If any of the above steps failed, the validator should stop and output the ''inconclusive'' state.
# Let ''T'' be the nLockTime of <code>to_sign</code> and ''S'' be the nSequence of the first input of <code>to_sign</code>. Output the state ''valid at time T and age S''.

Expand Down Expand Up @@ -459,7 +459,7 @@ A '''transaction finalizer''' of a BIP322 PSBT must follow these steps:
This specification is backwards-compatible with the legacy signmessage/verifymessage specification
through the special case [[#legacy|as described above]].
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.

== Reference implementation ==

Expand Down Expand Up @@ -493,7 +493,7 @@ and many others for their feedback on the specification.
** 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
** Add new PSBT input field for PSBT-based signing
** Add new PSBT global field for PSBT-based signing
* '''0.0.1''' (2018-09-10):
** Proposed as draft

Expand Down