Antminer X9
Monero ASIC Miner
1000KH
HASHRATE
2.47W/KH
EFFICIENCY
2470W
POWER
£861.54
EST. MONTHLY
205
DAYS
EST. ROI
This guide explains BIP 137 message signatures in plain English. It covers the problem behind the BIP, why it matters and whether the proposal is part of Bitcoin today.
TL;DR
- What it is: BIP 137 documents the deployed compact message-signature convention across uncompressed and compressed P2PKH, wrapped SegWit and native version-zero SegWit addresses. A 65-byte recoverable ECDSA signature carries a header plus fixed-width r and s values.
- Why it matters: BIP 137 made legacy compact signatures interoperable across several address forms. Use it only with byte-exact verification, narrow claims and an explicit path toward BIP 322.
- Current position: BIP 137 is Deployed and documents existing conventions.
BIP 137 message signatures in simple English
BIP 137 message signatures: Verification show that a corresponding private key produced the signature. It does not prove legal identity, current balance, exclusive control, transaction consent or freshness.
Simple example
A node operator is checking BIP 137 message signatures. BIP 137 is Deployed and documents existing conventions. Its own text points to BIP 322 as the newer format with broader capabilities.
Key terms in plain English
- BIP:
- Bitcoin Improvement Proposal: a document describing a proposed rule, standard or process. Its status must be checked separately.
- Node:
- A computer running Bitcoin software that checks data and communicates with other peers.
Status and successor
BIP 137 is Deployed and documents existing conventions. Its own text points to BIP 322 as the newer format with broader capabilities; compatibility needs explicit negotiation.
Encoding
The compact signature is one header byte followed by 32-byte r and 32-byte s values, commonly transported as base64. Decode strictly and reject truncation or trailing data.
Header ranges
Values 27-30 identify uncompressed P2PKH, 31-34 compressed P2PKH, 35-38 P2SH-P2WPKH and 39-42 native P2WPKH. Older software may reject newer ranges.
How specialists test it
Developers test the proposal with made-up data on an isolated test network. They check normal cases and deliberately invalid cases. Different implementations should reach the same result before anyone relies on the proposal.
Exact message bytes
Display, encode and preserve the precise bytes, prefix and network context. Whitespace, line endings, Unicode normalisation and hidden characters can change the signed statement.
Security meaning
Verification show that a corresponding private key produced the signature. It does not prove legal identity, current balance, exclusive control, transaction consent or freshness.
How specialists test it
Developers test the proposal with made-up data on an isolated test network. They check normal cases and deliberately invalid cases. Different implementations should reach the same result before anyone relies on the proposal.
Frequently asked questions
What is the main point of BIP 137 message signatures?
BIP 137 message signatures: Verification show that a corresponding private key produced the signature. It does not prove legal identity, current balance, exclusive control, transaction consent or freshness.
For BIP 137 message signatures, what should a beginner know about status and successor?
BIP 137 is Deployed and documents existing conventions. Its own text points to BIP 322 as the newer format with broader capabilities.
For BIP 137 message signatures, what should a beginner know about encoding?
The compact signature is one header byte followed by 32-byte r and 32-byte s values, commonly transported as base64.
For BIP 137 message signatures, what should a beginner know about header ranges?
Values 27-30 identify uncompressed P2PKH, 31-34 compressed P2PKH, 35-38 P2SH-P2WPKH and 39-42 native P2WPKH.
Conclusion
BIP 137 made legacy compact signatures interoperable across several address forms. Use it only with byte-exact verification, narrow claims and an explicit path toward BIP 322.
Primary sources
Check the current specification status and the documentation for the exact implementation you operate before moving production funds or changing a mining node.
Join the ASIC Mining Discussion
Members can read and join the discussion
Log in to read comments from other miners. Create a free account if you would like to ask a question or share your experience.
Membership helps us protect the discussion from spam and keep answers useful.