Why it exists
BIP 86 gives single-key Taproot wallets a predictable derivation convention. It addresses recovery from a seed when an account uses Taproot outputs without a spendable script tree. It is a wallet convention built on Taproot, not the Taproot consensus change itself.
How it works
The account hierarchy uses purpose 86'. For Bitcoin mainnet, the first receiving key is m/86'/0'/0'/0/0. This derived key becomes an internal Taproot key rather than being inserted unchanged into the output.
The wallet applies the Taproot tweak for the construction without a spendable script path. The resulting output key is committed to a version-one witness program. Mainnet addresses for those outputs use Bech32m and begin bc1p; spending ordinarily supplies a Schnorr signature.
A practical example
Two compatible wallets given the same seed, account number and BIP 86 convention derive the same internal key and apply the same tweak. A wallet that instead searches only purpose 84' will find native-SegWit keys, not this Taproot account.
What to keep in mind
BIP 86 does not preserve arbitrary Taproot recovery branches or multisig policies. For a custom script tree, retain the full descriptor and other recovery information. Address decoding, receiving, signing and restoring a BIP 86 account are separate capabilities to verify.
Status & implementation
The specification is Deployed. Core documents Taproot validation and Bech32m support, while BIP 86 describes the account arrangement above those rules. Its status should not be treated as evidence that every wallet recognizes purpose 86'.
Specification status: Deployed · Sources checked 13 November 2026
