Antminer X9
Monero ASIC Miner
1000KH
HASHRATE
2.47W/KH
EFFICIENCY
2470W
POWER
£861.72
EST. MONTHLY
205
DAYS
EST. ROI
This guide explains BIP 84 native SegWit accounts 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 84 is the Deployed application-layer derivation convention for native SegWit P2WPKH accounts. It uses the BIP 32 path m/84’/coin_type’/account’/change/address_index, creates BIP 141 version-zero witness programs and normally displays BIP 173 Bech32 addresses.
- Why it matters: BIP 84 standardises native SegWit account derivation, but reliable recovery still requires more than a seed phrase. Preserve the derivation context, validate Bech32 scripts and prove discovery across receiving and change branches with independent software.
- Current position: BIP 84 is the Deployed application-layer derivation convention for native SegWit P2WPKH accounts.
BIP 84 native SegWit accounts in simple English
BIP 84 native SegWit accounts: The hardened purpose level is 84, followed by hardened coin type and account, then unhardened change and address index.
Simple example
A node operator is checking BIP 84 native SegWit accounts. The distinct purpose prevents an incompatible wallet from silently treating native SegWit activity as BIP 44 legacy or BIP 49 wrapped SegWit.
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.
Purpose-separated accounts
The hardened purpose level is 84, followed by hardened coin type and account, then unhardened change and address index. The distinct purpose prevents an incompatible wallet from silently treating native SegWit activity as BIP 44 legacy or BIP 49 wrapped SegWit. A wallet that scans only another purpose can show zero balance even though the seed is correct.
Native P2WPKH script
For a derived compressed public key, the output is a version-zero witness program containing the 20-byte key hash. The scriptSig is empty when spending, and the witness carries signature and public key. Address text is an encoding of that script and network, not the key itself. Validate the decoded witness version and program length before accepting a destination.
Bech32 address handling
Mainnet native version-zero addresses use the bc human-readable part, while test networks use their defined prefix. Mixed case, invalid checksums and unsupported network prefixes must be rejected. Later witness versions use Bech32m under BIP 350, so an implementation should not apply the version-zero checksum rule blindly to every bc1 address.
Extended key prefixes
BIP 84 registers zpub and zprv mainnet serialisations plus vpub and vprv for testnet. These version bytes communicate intended script context to supporting tools but do not cryptographically restrict derivation. Exporting an account public key reveals its entire non-hardened branch, while exporting a private extended key exposes spending capability and must be treated as a secret.
Discovery and gap limits
Recovery software must scan external and internal branches for every used account until its documented gap rule is satisfied. Change-only history, addresses issued but not yet used and large merchant gaps can defeat a simplistic scan. Preserve account numbers and wallet policy with the seed, then compare recovered scripts and transaction history against an independently indexed node.
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.
Deployed status and backup boundary
BIP 84 is widely deployed, but individual wallets differ in account discovery, extended-key display and descriptor export. A mnemonic alone may omit passphrase, network, derivation path, birthday and multisystem context. Perform a full recovery drill on an offline machine before relying on a wallet for mining payouts or customer deposits.
Frequently asked questions
What is the main point of BIP 84 native SegWit accounts?
BIP 84 native SegWit accounts: The hardened purpose level is 84, followed by hardened coin type and account, then unhardened change and address index.
For BIP 84 native SegWit accounts, what should a beginner know about purpose-separated accounts?
The hardened purpose level is 84, followed by hardened coin type and account, then unhardened change and address index.
For BIP 84 native SegWit accounts, what should a beginner know about native P2WPKH script?
For a derived compressed public key, the output is a version-zero witness program containing the 20-byte key hash.
For BIP 84 native SegWit accounts, what should a beginner know about bech32 address handling?
Mainnet native version-zero addresses use the bc human-readable part, while test networks use their defined prefix.
Conclusion
BIP 84 standardises native SegWit account derivation, but reliable recovery still requires more than a seed phrase. Preserve the derivation context, validate Bech32 scripts and prove discovery across receiving and change branches with independent software.
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.