BIP-322: Generic Signed Message

Definition: BIP-322 is a Bitcoin specification for signing and verifying messages against Bitcoin addresses by evaluating the address’s spending conditions. It extends message signing beyond legacy P2PKH addresses, but a valid signature does not identify a real-world person or prove that the address still holds bitcoin.1

BIP number BIP 322
Layer Applications
Type and status Specification; listed as Complete in the BIP repository.1
Assigned September 10, 2018.1
Official specification Open BIP-322 specification
Directories Bitcoin Technology & Infrastructure

In-Depth Explanation

Bitcoin message signing lets a wallet produce a cryptographic proof tied to a message and an address without sending a payment. Earlier message-signing conventions were limited to legacy Pay-to-Public-Key-Hash (P2PKH) addresses. BIP-322 generalizes the process by expressing the proof through Bitcoin’s transaction and script rules, so it can accommodate a wider range of spending conditions in principle.1

How the proof is checked

A BIP-322 verifier receives an address, a message, and a signature. The format commits to a tagged hash of the message, then models the address’s script as a challenge in a pair of virtual transactions. The first transaction associates the message with the address script; the second contains the witness or transaction data that must satisfy that script. The construction is for verification and does not transfer bitcoin or create a normal payment to broadcast.1 The tagged-hash construction uses the BIP-340 signing framework, while Taproot addresses bring BIP-341 and BIP-342 spending rules into scope.34

Signature formats

Format What it contains Important scope
Legacy A compact signature using the older message-signing convention. BIP-322 limits this legacy format to P2PKH addresses; new proofs should use the newer formats where supported.1
Simple A base64-encoded witness stack. Specified for native SegWit P2WPKH, P2WSH, and P2TR scripts, subject to the BIP’s stated limitations, including time-lock scripts.1
Full A serialized virtual transaction with the signature data. Can represent more complex script conditions and optional transaction fields, but the verifier still needs to understand the relevant script rules.1
Proof of Funds A finalized Partially Signed Bitcoin Transaction (PSBT) containing selected UTXOs. Can demonstrate control of the included outputs; it does not prove the list is complete or that the outputs remain unspent. A verifier must check their status on-chain.12

The formats differ in how much data is carried and which scripts they can express. A wallet’s support for BIP-322 may cover only some formats or address types, so users should check compatibility with the signer and verifier before relying on a proof. The repository’s “Complete” status describes the specification’s state; it is not a guarantee that every wallet has implemented every variant.1

What a signature does—and does not—show

A valid proof shows that the provided signing data satisfies the script associated with the stated address for the signed message, according to the verifier’s implementation. It is not a proof of a person’s legal identity, an endorsement of the message, or evidence that the address currently controls funds. A key holder could also sign on someone else’s behalf. The Proof-of-Funds variant has a separate limitation: the signer chooses which UTXOs to include, and the proof does not claim to list every output associated with an address or establish that listed outputs are still unspent.1

History

  • March 14, 2018: The original discussion for BIP-322 was opened on the Bitcoin development mailing list.1
  • September 10, 2018: BIP-322 was assigned and published as a draft specification.1
  • April 15, 2026: The BIP changelog records version 1.0.0 and marks the specification Complete.1
  • October 23, 2026: Version 2.1.0 updated the specification’s handling of Taproot upgrade mechanisms during verification.1

Limitations and Criticisms

BIP-322 improves the range of Bitcoin scripts that a message proof can represent, but it does not make message signing equivalent to a payment or a live balance check. The proof is time-specific, depends on the verifier implementing the same format correctly, and cannot establish who is behind a signing key. Proof-of-Funds can also be misleading if readers mistake a chosen set of outputs for the signer’s complete holdings. For high-stakes claims, verify the message, address, signature format, and any on-chain output data independently.1

Last updated: November 12, 2026.

Related Terms

Related Articles

See Also

Crypto Tools – A curated list by CryptoGloss

Sources

  1. Bitcoin Improvement Proposals. “BIP 322: Generic Signed Message Format.” Version 2.1.0, October 23, 2026. Accessed November 12, 2026. https://github.com/bitcoin/bips/blob/master/bip-0322.mediawiki.
  2. Bitcoin Improvement Proposals. “BIP 174: Partially Signed Bitcoin Transaction Format.” Accessed November 12, 2026. https://github.com/bitcoin/bips/blob/master/bip-0174.mediawiki.
  3. Bitcoin Improvement Proposals. “BIP 340: Schnorr Signatures for secp256k1.” Accessed November 12, 2026. https://github.com/bitcoin/bips/blob/master/bip-0340.mediawiki.
  4. Bitcoin Improvement Proposals. “BIP 341: Taproot: SegWit Version 1 Spending Rules.” Accessed November 12, 2026. https://github.com/bitcoin/bips/blob/master/bip-0341.mediawiki.