A phone, laptop and signing device arranged as three different ways to use a Bitcoin wallet, editorial illustration
BIP 84 / ADDRESSES

Native SegWit accounts.

A derivation convention for single-key P2WPKH accounts, using purpose 84.

Read the explanation
← All standards

Why it exists

BIP 84 standardizes accounts for single-key native SegWit payments, also called P2WPKH. It connects an account derivation convention with a specific output type so that compatible wallets can reconstruct the same receiving and change addresses from a backup.

How it works

The path follows the familiar purpose, coin, account, branch and index structure, but purpose is 84'. The first mainnet receiving key is therefore m/84'/0'/0'/0/0. The public key is hashed into a version-zero witness program.

The resulting mainnet address uses Bech32 and begins bc1q. BIP 84 also specifies zpub and zprv extended-key serialization prefixes. A descriptor can express the script type directly with wpkh(), so a wallet may use ordinary xpub serialization together with explicit descriptor information.

PUT IT IN CONTEXT

A practical example

A recovery that searches m/44'/0'/0' looks in a different branch from m/84'/0'/0'. Selecting a native-SegWit account and the correct account number lets compatible software derive the receiving keys originally used by the BIP 84 wallet.

What to keep in mind

A bc1q prefix alone does not identify every detail of a wallet: other version-zero witness scripts also use Bech32. BIP 84 covers single-key P2WPKH accounts, not multisig P2WSH or Taproot. Account, script type and derivation information must agree.

Status & implementation

The official status is Deployed. Bitcoin Core supports the wpkh() descriptor expression for native-SegWit outputs; that is distinct from promising automatic import of every BIP 84 seed backup or zpub representation.

Specification status: Deployed · Sources checked 13 November 2026

Read the sources

Find your next answer.

Search the complete field guide · Esc to close