A Bitcoin message signature cannot settle a dispute over who sent an earlier payment. BIP 322, the specification for generic signed messages, explicitly excludes that use. Its useful claim runs in the other direction: a signer can demonstrate an ability to satisfy the conditions attached to an address intended to receive funds. Treating that as a receipt for an old transfer asks the proof to establish something it does not establish.
| What you need to know |
|---|
| BIP 322 cannot prove that a signer sent a previous transaction. |
| A signed message does not provide lasting proof of control over funds. |
| Its virtual transaction includes an invalid input and cannot be spent on a real network. |
| Checking whether proof-of-funds inputs remain unspent requires current blockchain information. |
The distinction is written into the official BIP 322 specification. This is a guide to the limits of that document, rather than a report of a new Bitcoin release or a claim that every wallet implements it.
The message and the payment answer different questions
Verification starts with three inputs: an address, a message and a signature. The verifier checks the relationship between those inputs under the relevant script rules. A successful check therefore needs to be read alongside the actual message. It is not a general certificate covering the signer’s transaction history.
Consider a buyer who asks someone to sign a message after a disputed transfer. Even if that message names the disputed payment, BIP 322 does not turn the signature into proof that this person made it. The specification’s exclusion of prior transactions still applies. For this dispute, requesting a more emphatic message would not repair the missing evidence.
The document also gives two reasons to resist a broader claim of fund control. A signature can become obsolete immediately after creation. Someone with access to a secret key may also agree to sign a message on another person’s behalf while refusing to sign an actual transaction. Those are limits of what message signing can demonstrate, rather than problems that a different sentence in the message can remove.
A balance claim needs another check
BIP 322’s proof-of-funds variant adds a separate issue. The signer chooses a set of transaction outputs to include in the proof. That list is not a promise that every output associated with an address has been disclosed. Reading it as a complete balance would add a claim the specification expressly declines to make.
Whether those outputs remain unspent is a different check again. A verifier needs the current set of unspent transaction outputs to establish their blockchain state. An offline verifier can assess the cryptographic validity of the supplied input data, but cannot establish that current state from the signature alone. A valid offline result therefore should not be reported as a verified spendable balance.
For a payment dispute, start by stating the fact that needs establishing: who sent a past transfer, who can satisfy an address’s conditions, or whether selected outputs remain available. BIP 322 draws a boundary between these questions. Keeping the question attached to the result prevents a genuine signature from being used as the answer to the wrong one.






