Antminer X9
Monero ASIC Miner
1000KH
HASHRATE
2.47W/KH
EFFICIENCY
2470W
POWER
£857.29
EST. MONTHLY
206
DAYS
EST. ROI
This guide explains BIP 178 Version Extended WIF 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 178 is a Draft applications-layer proposal assigned on 4 April 2018. It extends Wallet Import Format suffix information so a private key can indicate an intended P2PKH, native P2WPKH or nested P2WPKH-P2SH address form.
- Why it matters: BIP 178 proposes useful address-type metadata for WIF, but its Draft status and one-way compatibility demand explicit wallet support and recovery tests. The format never reduces the sensitivity of the private key.
- Current position: BIP 178 is a Draft applications-layer proposal assigned on 4 April 2018.
BIP 178 Version Extended WIF in simple English
BIP 178 Version Extended WIF: The suffix is not authenticated business intent beyond the checksummed WIF encoding and does not constrain what the private key can sign.
Simple example
A node operator is checking BIP 178 Version Extended WIF. Validate test vectors instead of inferring behaviour from displayed first characters. Preserve descriptors, derivation records, wallet version and script history alongside protected key material, then test recovery for every used form.
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.
Draft status and scope
Treat BIP 178 as a Draft wallet-interchange proposal, not a network activation or guarantee of common support. It changes how software interprets private-key export metadata. The same underlying key remains capable of deriving scripts beyond the indicated import preference.
Legacy suffixes
Traditional WIF stores a 256-bit private key with either no suffix for uncompressed P2PKH or 0x01 for a compressed public key with otherwise unknown address format. Under the proposal, legacy imports still require software to consider all relevant address forms.
Extended values
The proposal assigns 0x10 to compressed P2PKH, 0x11 to native P2WPKH and 0x12 to P2WPKH nested in P2SH. These bytes are key-export metadata, not script opcodes or address prefixes. Validate test vectors instead of inferring behaviour from displayed first characters.
Asymmetric compatibility
New software can understand old WIF and fall back to scanning possible forms. Older software may reject the new suffix values because it expects the compressed flag to be exactly 0x01. Never assume an extended export can be restored by an untested legacy wallet.
Recovery boundaries
An address-type hint can reduce discovery work but must not narrow disaster recovery so far that funds at other scripts are missed. Preserve descriptors, derivation records, wallet version and script history alongside protected key material, then test recovery for every used form.
Security meaning
The suffix is not authenticated business intent beyond the checksummed WIF encoding and does not constrain what the private key can sign. Anyone holding the WIF has the secret. Treat extended and traditional strings with identical custody, redaction and destruction controls.
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 178 Version Extended WIF?
BIP 178 Version Extended WIF: The suffix is not authenticated business intent beyond the checksummed WIF encoding and does not constrain what the private key can sign.
For BIP 178 Version Extended WIF, what should a beginner know about draft status and scope?
Treat BIP 178 as a Draft wallet-interchange proposal, not a network activation or guarantee of common support.
For BIP 178 Version Extended WIF, what should a beginner know about legacy suffixes?
Traditional WIF stores a 256-bit private key with either no suffix for uncompressed P2PKH or 0x01 for a compressed public key with otherwise unknown address format.
For BIP 178 Version Extended WIF, what should a beginner know about extended values?
The proposal assigns 0x10 to compressed P2PKH, 0x11 to native P2WPKH and 0x12 to P2WPKH nested in P2SH.
Conclusion
BIP 178 proposes useful address-type metadata for WIF, but its Draft status and one-way compatibility demand explicit wallet support and recovery tests. The format never reduces the sensitivity of the private key.
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.