Antminer X9
Monero ASIC Miner
1000KH
HASHRATE
2.47W/KH
EFFICIENCY
2470W
POWER
£861.31
EST. MONTHLY
205
DAYS
EST. ROI
This guide explains BIP 86 Taproot key derivation 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 86 defines the deployed HD derivation convention for single-key pay-to-Taproot outputs. It uses purpose 86 in the familiar account hierarchy, derives an internal x-only key and applies a TapTweak commitment to an unspendable script path.
- Why it matters: BIP 86 gives single-key Taproot wallets a common recovery path, but correct recovery depends on the tweak, Bech32m encoding and branch history as well as the seed. Verify the final script, not just the derived key.
- Current position: BIP 86 is Deployed, Applications and Specification.
BIP 86 Taproot key derivation in simple English
BIP 86 Taproot key derivation: Encode the version-one witness program with Bech32m and the correct network prefix. Back up seed, network, account usage, derivation convention and highest-used indexes.
Simple example
A node operator is checking BIP 86 Taproot key derivation. This commits to an unspendable script path instead of using an untweaked key. Its path is m/86 hardened/coin type hardened/account hardened/change/address index.
Key terms in plain English
- BIP:
- Bitcoin Improvement Proposal: a document describing a proposed rule, standard or process. Its status must be checked separately.
- Taproot:
- A Bitcoin upgrade that added new signature and script options for spending outputs.
- Node:
- A computer running Bitcoin software that checks data and communicates with other peers.
Status and purpose
BIP 86 is Deployed, Applications and Specification. Its path is m/86 hardened/coin type hardened/account hardened/change/address index.
Branch semantics
Coin type and account follow the established BIP 44 model; change zero is external and one internal. Maintain independent issuance and gap tracking for both branches.
Internal key
The derived compressed public key is lifted to its x-only curve point P. Validate curve membership and parity handling exactly rather than slicing arbitrary key bytes.
Taproot tweak
With no intended script path, compute Q as P plus the TapTweak hash of P times G. This commits to an unspendable script path instead of using an untweaked key.
Output and witness
The scriptPubKey is witness version one followed by the 32-byte output key; scriptSig is empty and a key-path spend witness contains a Schnorr signature.
Address and recovery
Encode the version-one witness program with Bech32m and the correct network prefix. Back up seed, network, account usage, derivation convention and highest-used indexes.
Vectors
Reproduce the published mnemonic, account extended keys, receiving and change paths, internal keys, output keys, scripts and addresses. Include wrong-purpose, untweaked-key and Bech32 failures. Build a revision-pinned evidence pack on an isolated node, wallet or protocol harness.
Frequently asked questions
What is the main point of BIP 86 Taproot key derivation?
BIP 86 Taproot key derivation: Encode the version-one witness program with Bech32m and the correct network prefix.
For BIP 86 Taproot key derivation, what should a beginner know about status and purpose?
BIP 86 is Deployed, Applications and Specification. Its path is m/86 hardened/coin type hardened/account hardened/change/address index.
For BIP 86 Taproot key derivation, what should a beginner know about branch semantics?
Coin type and account follow the established BIP 44 model. Change zero is external and one internal.
For BIP 86 Taproot key derivation, what should a beginner know about internal key?
The derived compressed public key is lifted to its x-only curve point P.
Conclusion
BIP 86 gives single-key Taproot wallets a common recovery path, but correct recovery depends on the tweak, Bech32m encoding and branch history as well as the seed. Verify the final script, not just the derived 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.