TERM_DEF // UPGRADES_BIPS / BIP_322_GENERIC_SIGNED_MESSAGE_FORMAT
BIP 322 (GENERIC
SIGNED MESSAGE FORMAT)
SIGNED MESSAGE FORMAT)
BIP 322 (Generic Signed Message Format). Signing arbitrary messages by constructing a virtual transaction for any script.
This page sits in the Upgrades & BIPs section — The proposal process and the major upgrades that shaped Bitcoin. Read on for what it is, why it exists, how it works under the hood, and what to watch out for.
This page sits in the Upgrades & BIPs section — The proposal process and the major upgrades that shaped Bitcoin. Read on for what it is, why it exists, how it works under the hood, and what to watch out for.
WHAT_BIP_322_GENERIC_SIGNED_MESSAGE_FORMAT_IS
BIP 322 (Generic Signed Message Format) — at a glance
UPGRADES
BIP 322 — "Generic Signed Message Format" is a proposal in the Signatures family, first published in 2018 with status active. Signing arbitrary messages by constructing a virtual transaction for any script. Its technical mechanism: virtual tx commitment + sighash + witness; works for legacy, SegWit, Taproot. replaces the legacy "Bitcoin Signed Message:" prefix that only worked for P2PKH
Why it exists
DESIGN
BIP 322 (Generic Signed Message Format) exists to solve a specific problem: a generic signed-message format for any output type, not just P2PKH. Without a written, numbered spec, every wallet and node implementer would interpret the requirement differently — and Bitcoin's value depends on every implementation agreeing exactly. BIP-322 is the single source of truth for this concern, so any new client built today can match the behaviour of every client built since 2018.
HOW_IT_WORKS
Mechanism
HOW IT WORKS
Mechanically, BIP-322 virtual tx commitment + sighash + witness; works for legacy, SegWit, Taproot. Adoption today: replaces the legacy "Bitcoin Signed Message:" prefix that only worked for P2PKH.
1. Author drafts BIP-322 against the BIP-2 template — abstract, motivation, specification, rationale.
2. The text + a reference implementation are posted on the bitcoin-dev list and as a PR to bitcoin/bips.
3. Reviewers tear it apart: ambiguities, security concerns, edge cases, interaction with prior BIPs.
4. Once stable, the BIP editor merges it; it gets a number (BIP-322) and the status "draft" or "proposed".
5. Implementations land in Bitcoin Core / wallets / other clients. For consensus changes: activation parameters chosen.
6. After deployment + adoption, BIP-322 is promoted to "final"; deprecated proposals get "replaced" or "withdrawn".
WORKED_EXAMPLE
BIP-322 — quick reference card
EXAMPLE
BIP number : 322
Title : Generic Signed Message Format
Area : Signatures
First published: 2018
Status : active
Fork class : no
Motivation : a generic signed-message format for any output type, not just P2PKH.
Mechanism : virtual tx commitment + sighash + witness; works for legacy, SegWit, Taproot.
Where it shows up : replaces the legacy "Bitcoin Signed Message:" prefix that only worked for P2PKH.
Read the spec : https://github.com/bitcoin/bips/blob/master/bip-0322.mediawiki
KEY_PROPERTIES
OPT-IN
No authority can force a BIP on anyone. Adoption depends entirely on whether the change is genuinely useful.
NUMBERED
Stable numeric reference — BIP-322 means the same thing across every wallet, miner, and node that has read this spec.
NON-CONSENSUS
BIP-322 is not a consensus rule — clients can implement it without coordinating with the network at large.
DEPLOYED
Implementations of BIP-322 are in production. The behaviour is observable on mainnet today.
COMMON_PITFALLS
Things that catch people out
PITFALLS
- Don't confuse "draft" / "proposed" / "final" status — read the BIP header before relying on it in production.
- The BIP number is just an editorial counter — it doesn't imply correctness or stability. Always cross-reference with the latest bitcoin/bips repo.
RELATED_CONCEPTS
Other terms from Upgrades & BIPs — click any to read its page:
TERMINOLOGY_INDEX
TERMINOLOGY
BIP 322 (Generic Signed Message Format)
Signing arbitrary messages by constructing a virtual transaction for any script.
Segregated Witness (SegWit, BIP 141)
The 2017 upgrade separating witness data, fixing tx malleability, and introducing weight units.
Taproot (BIP 341)
The 2021 upgrade introducing key-aggregable schnorr-signatures/">Schnorr signatures and Merkleized script trees.
Tapscript (BIP 342)
Script-language updates accompanying Taproot — new opcodes, removed limits.
Schnorr (BIP 340)
The Schnorr signature spec adopted by Taproot.
BIP Process
The community workflow for proposing, discussing, and tracking changes to Bitcoin.
Soft Fork Activation
MASF (Miner-Activated Soft Fork)
Activation triggered by miner signaling in block versions.