Skip to content
BIP ATLAS

BIPs 0044 · 0084 · 0086

Where in the tree do wallet keys live?

A seed gives a wallet a tree of keys. Shared path conventions tell it where to look, and output conventions tell it which coins those keys can spend.

BIP 32 derives a master key and a tree of child keys from a seed. Two wallets can restore the same seed but search different parts of that tree. Each may then miss the other’s coins. They need a shared path convention. BIP 84’s author identifies this compatibility between wallets as the aim.123

BIP 44, assigned in 2014, is that agreement. It is an application-layer convention on top of BIP 32 and BIP 43, not a change to the derivation itself. BIP 84 (2017) and BIP 86 (2021) reuse its structure for SegWit and Taproot. All three are recorded as deployed.14

Source revision
bitcoin/bips @ 3a10b5b
Source checked
1 October 2026
Review state
Awaiting review
Source details

This chapter is an independent explanation, not the proposal itself. Preamble fields are shown as the pinned files record them, without author e-mail addresses. Status is the proposal’s own field. It is not an endorsement or a sign of consensus.

BIP 44: Multi-Account Hierarchy for Deterministic Wallets

BIP
44
Layer
Applications
Title
Multi-Account Hierarchy for Deterministic Wallets
Authors
Marek Palatinus
Pavol Rusnak
Comments-Summary
Mixed review (one person)
Comments-URI
https://github.com/bitcoin/bips/wiki/Comments:BIP-0044
Status
Deployed
Type
Specification
Assigned
2014-04-24
Requires
32, 43

Pinned source · Reader view on bips.dev
SHA-256 6a541c79f94077ac529941a8cbd373ce077a5d6e97b6dd8209b45ac10f737eaf
Git blob a94efba2ec6f8479c7a16d5dded12572be066c28

BIP 84: Derivation scheme for P2WPKH based accounts

BIP
84
Layer
Applications
Title
Derivation scheme for P2WPKH based accounts
Authors
Pavol Rusnak
Comments-Summary
No comments yet.
Comments-URI
https://github.com/bitcoin/bips/wiki/Comments:BIP-0084
Status
Deployed
Type
Specification
Assigned
2017-12-28
License
CC0-1.0

Pinned source · Reader view on bips.dev
SHA-256 1900feec6cafca65b8c09906ca0658d2d742b4c9b44cb15678996985b6bfe627
Git blob f266a1455317e3cfb69e477f24fe9f23577a5433

BIP 86: Key Derivation for Single Key P2TR Outputs

BIP
86
Layer
Applications
Title
Key Derivation for Single Key P2TR Outputs
Authors
Ava Chow
Status
Deployed
Type
Specification
Assigned
2021-06-22
License
BSD-2-Clause

Pinned source · Reader view on bips.dev
SHA-256 d8d01dee331da07c2562615bc1f064c1868ec3fce61184973da76d1196c7f5b0
Git blob 43c692a56e68913827a99b99964c35814cce121c

Fig. A12.1 Five levels below the master key

Five levels below the master keyBIP 44's path m / 44′ / 0′ / 0′ / 0 / 0: the master key m, then purpose 44′, coin type 0′, account 0′, change 0, address index 0. The first 3 levels below m are hardened and need the parent's private key; the last 2 use public derivation, so the account's extended public key reaches them. BIP 44's examples table reads this path as Bitcoin, first account, external chain, first address.HARDENEDPUBLIC DERIVATIONm44′0′0′00ACCOUNT LINEMASTERPURPOSECOIN TYPEACCOUNTCHANGEADDRESS INDEXBIP 44 LINE 174: BITCOIN, FIRST ACCOUNT,EXTERNAL CHAIN, FIRST ADDRESSHARDENED
BIP 44’s first example path. Three hardened levels pick a convention, a coin and an account; below the account line, two public levels number the addresses.5678910

Five levels, each with a job

BIP 44 fixes five levels below the master key: purpose, coin type, account, change and address index. An apostrophe after a number marks hardened derivation, and the first three levels are hardened. The author’s aim was a hierarchy that handles many coins, many accounts, separate receiving and change chains, and millions of addresses per chain.25

The purpose is a constant, 44′, which tells software that everything below follows this specification. The coin type gives each coin its own subtree, avoiding address reuse across coins. It is 0′ for Bitcoin and 1′ for Bitcoin testnet, with a longer list kept outside the BIP in SLIP-0044.67

Accounts separate keys into independent identities, numbered from 0. A wallet following BIP 44 does not mix coins between accounts. The BIP compares them to bank accounts for donations, savings or shared expenses.8

The change level uses 0 for the external chain and 1 for the internal chain. External addresses are intended for use outside the wallet, such as receiving payments. Internal addresses receive transaction change. Each chain numbers its addresses from 0.910

Account discovery starts with account 0 and searches its external chain for transactions. If it finds transactions, it continues with the next account. It stops at the first account with no transaction history. This works because software should not create a new account while the previous one has no history.811

BIP 44 gave the gap limit as 20: scanning a chain stops after 20 consecutive unused addresses. Wallet software should warn before a user gives out an address beyond that limit.12

BIP 44 scans only external chains, reasoning that internal chains receive only coins that come from the associated external chains. This identifies which accounts have been used. Recovering their funds also requires finding their internal/change outputs.111213

Fig. A12.2 Finding the accounts again

  1. Finding the accounts again, step 1 of 3Illustration: the external chain of account 0′, addresses 0, 1, 2, 3 checked in order; in this made-up history addresses 0, 1 and 3 have transactions.ACCOUNT 0′ · EXTERNAL CHAIN…HAS TRANSACTIONS (ILLUSTRATIVE)HISTORY, NOT BALANCE, IS WHAT COUNTS

    Derive account 0′ and its external chain, then check its addresses for transactions, one index at a time.

  2. Finding the accounts again, step 2 of 3The scan continues past the last used address, 3, until 20 unused addresses in a row have been checked, then stops. BIP 44 gives the gap limit as 20 (line 124).ACCOUNT 0′ · EXTERNAL CHAIN20 UNUSED IN A ROWGAP LIMIT 20, AS BIP 44 GAVE IT · LINE 124STOP

    BIP 44 gave the gap limit as 20: after 20 unused addresses in a row, it stops scanning that chain.

  3. Finding the accounts again, step 3 of 3Because account 0′ has transactions, account 1′ is derived and its external chain scanned. In this illustration it has no transactions, so discovery stops; no account 2′ is tried.ACCOUNT 0′ · HAS HISTORY → NEXT…ACCOUNT 1′ · NO HISTORY → STOP…ACCOUNT 2′ IS NEVER TRIED

    Account 0′ had transactions, so try account 1′. Its external chain has none: discovery stops there.

How a restored wallet finds its accounts, as BIP 44 describes it. Which addresses are used is made up for the drawing; the gap limit is BIP 44’s.81112
Two paths from BIP 44’s example table

BIP 44’s own examples make the pattern concrete. Its table lists 16 paths: the first and second address on the external and change chains, for the first and second account, on Bitcoin and on testnet. The first Bitcoin receiving address of the first account is m/44′/0′/0′/0/0; its first change address is m/44′/0′/0′/1/0.914

Walking a published path

Follow the same seed down the published BIP 84 and BIP 86 paths. Step from the account to a receiving key, then switch to a change key. Watch where the route changes and how the final key becomes an output.51516

Fig. A12.3 One level at a time

Static view: BIP 84 · P2WPKH, first receiving address, every level walked. With JavaScript you can switch scheme, switch between receiving and change, and step down one level at a time.

One level at a timeThe path m/84'/0'/0'/0/0 as a stack of six plates: m, purpose 84′ (hardened), coin type 0′ (hardened), account 0′ (hardened), change 0 (public derivation), address index 0 (public derivation). The account's extended public key reaches the two public levels below it. Beside the stack, the current level; at the last step, the address. The status line below names the step.0ADDRESS INDEX0CHANGE0′ACCOUNT · HARDENED0′COIN TYPE · HARDENED84′PURPOSE · HARDENEDmm · MASTERACCOUNT XPUBREACHES BELOWSTEP 0 OF 6 · MASTER KEYmFrom the seed. Everything belowis derived from it.public key 03d902f3…STEP 1 OF 6 · PURPOSE84′Which convention the subtreefollows: 44′, 84′ or 86′.HARDENED: NEEDS THE PARENT’S PRIVATE KEYpublic key 03c098a6…parent fingerprint 73c5da0aSTEP 2 OF 6 · COIN TYPE0′One subtree per coin: 0′ forBitcoin, 1′ for testnet.HARDENED: NEEDS THE PARENT’S PRIVATE KEYpublic key 023f6221…parent fingerprint 7ead67a7STEP 3 OF 6 · ACCOUNT0′Independent identities, likebank accounts. From 0.HARDENED: NEEDS THE PARENT’S PRIVATE KEYpublic key 02707a62…parent fingerprint 7ef32bdbaccount xpub zpub6rFR7y4Q…PUBLISHED IN BIP 84 (LINE 75)STEP 4 OF 6 · CHANGE00: external chain (receiving).1: internal chain (change).PUBLIC: THE PARENT’S XPUB IS ENOUGHpublic key 02360e9e…parent fingerprint fd13aac9STEP 5 OF 6 · ADDRESS INDEX0Addresses numbered from 0along the chain.PUBLIC: THE PARENT’S XPUB IS ENOUGHpublic key 0330d54f…parent fingerprint 3b0373d4STEP 6 OF 6 · THE ADDRESSkey 0330d54f… 33 BHASH160 c0cebcd6… 20 Bscript 0014 ‖ hashbech32 bc1qcr8te4kr60…P2WPKH · BIP 84
One level at a timeThe path m/84'/0'/0'/0/0 as a stack of six plates: m, purpose 84′ (hardened), coin type 0′ (hardened), account 0′ (hardened), change 0 (public derivation), address index 0 (public derivation). The account's extended public key reaches the two public levels below it. Beside the stack, the current level; at the last step, the address. The status line below names the step.0ADDRESS INDEX0CHANGE0′ACCOUNT · HARDENED0′COIN TYPE · HARDENED84′PURPOSE · HARDENEDmm · MASTERACCOUNT XPUB REACHES EVERYTHING BELOW THE LINESTEP 0 OF 6 · MASTER KEYmFrom the seed. Everything belowis derived from it.public key 03d902f3…STEP 1 OF 6 · PURPOSE84′Which convention the subtreefollows: 44′, 84′ or 86′.HARDENED: NEEDS THE PARENT’S PRIVATE KEYpublic key 03c098a6…parent fingerprint 73c5da0aSTEP 2 OF 6 · COIN TYPE0′One subtree per coin: 0′ forBitcoin, 1′ for testnet.HARDENED: NEEDS THE PARENT’S PRIVATE KEYpublic key 023f6221…parent fingerprint 7ead67a7STEP 3 OF 6 · ACCOUNT0′Independent identities, likebank accounts. From 0.HARDENED: NEEDS THE PARENT’S PRIVATE KEYpublic key 02707a62…parent fingerprint 7ef32bdbaccount xpub zpub6rFR7y4Q…PUBLISHED IN BIP 84 (LINE 75)STEP 4 OF 6 · CHANGE00: external chain (receiving).1: internal chain (change).PUBLIC: THE PARENT’S XPUB IS ENOUGHpublic key 02360e9e…parent fingerprint fd13aac9STEP 5 OF 6 · ADDRESS INDEX0Addresses numbered from 0along the chain.PUBLIC: THE PARENT’S XPUB IS ENOUGHpublic key 0330d54f…parent fingerprint 3b0373d4STEP 6 OF 6 · THE ADDRESSkey 0330d54f… 33 BHASH160 c0cebcd6… 20 Bscript 0014 ‖ hashbech32 bc1qcr8te4kr60…P2WPKH · BIP 84
One level at a timeThe path m/84'/0'/0'/0/1 as a stack of six plates: m, purpose 84′ (hardened), coin type 0′ (hardened), account 0′ (hardened), change 0 (public derivation), address index 1 (public derivation). The account's extended public key reaches the two public levels below it. Beside the stack, the current level; at the last step, the address. The status line below names the step.1ADDRESS INDEX0CHANGE0′ACCOUNT · HARDENED0′COIN TYPE · HARDENED84′PURPOSE · HARDENEDmm · MASTERACCOUNT XPUBREACHES BELOWSTEP 0 OF 6 · MASTER KEYmFrom the seed. Everything belowis derived from it.public key 03d902f3…STEP 1 OF 6 · PURPOSE84′Which convention the subtreefollows: 44′, 84′ or 86′.HARDENED: NEEDS THE PARENT’S PRIVATE KEYpublic key 03c098a6…parent fingerprint 73c5da0aSTEP 2 OF 6 · COIN TYPE0′One subtree per coin: 0′ forBitcoin, 1′ for testnet.HARDENED: NEEDS THE PARENT’S PRIVATE KEYpublic key 023f6221…parent fingerprint 7ead67a7STEP 3 OF 6 · ACCOUNT0′Independent identities, likebank accounts. From 0.HARDENED: NEEDS THE PARENT’S PRIVATE KEYpublic key 02707a62…parent fingerprint 7ef32bdbaccount xpub zpub6rFR7y4Q…PUBLISHED IN BIP 84 (LINE 75)STEP 4 OF 6 · CHANGE00: external chain (receiving).1: internal chain (change).PUBLIC: THE PARENT’S XPUB IS ENOUGHpublic key 02360e9e…parent fingerprint fd13aac9STEP 5 OF 6 · ADDRESS INDEX1Addresses numbered from 0along the chain.PUBLIC: THE PARENT’S XPUB IS ENOUGHpublic key 03e775fd…parent fingerprint 3b0373d4STEP 6 OF 6 · THE ADDRESSkey 03e775fd… 33 BHASH160 9c90f934… 20 Bscript 0014 ‖ hashbech32 bc1qnjg0jd8228…P2WPKH · BIP 84
One level at a timeThe path m/84'/0'/0'/0/1 as a stack of six plates: m, purpose 84′ (hardened), coin type 0′ (hardened), account 0′ (hardened), change 0 (public derivation), address index 1 (public derivation). The account's extended public key reaches the two public levels below it. Beside the stack, the current level; at the last step, the address. The status line below names the step.1ADDRESS INDEX0CHANGE0′ACCOUNT · HARDENED0′COIN TYPE · HARDENED84′PURPOSE · HARDENEDmm · MASTERACCOUNT XPUB REACHES EVERYTHING BELOW THE LINESTEP 0 OF 6 · MASTER KEYmFrom the seed. Everything belowis derived from it.public key 03d902f3…STEP 1 OF 6 · PURPOSE84′Which convention the subtreefollows: 44′, 84′ or 86′.HARDENED: NEEDS THE PARENT’S PRIVATE KEYpublic key 03c098a6…parent fingerprint 73c5da0aSTEP 2 OF 6 · COIN TYPE0′One subtree per coin: 0′ forBitcoin, 1′ for testnet.HARDENED: NEEDS THE PARENT’S PRIVATE KEYpublic key 023f6221…parent fingerprint 7ead67a7STEP 3 OF 6 · ACCOUNT0′Independent identities, likebank accounts. From 0.HARDENED: NEEDS THE PARENT’S PRIVATE KEYpublic key 02707a62…parent fingerprint 7ef32bdbaccount xpub zpub6rFR7y4Q…PUBLISHED IN BIP 84 (LINE 75)STEP 4 OF 6 · CHANGE00: external chain (receiving).1: internal chain (change).PUBLIC: THE PARENT’S XPUB IS ENOUGHpublic key 02360e9e…parent fingerprint fd13aac9STEP 5 OF 6 · ADDRESS INDEX1Addresses numbered from 0along the chain.PUBLIC: THE PARENT’S XPUB IS ENOUGHpublic key 03e775fd…parent fingerprint 3b0373d4STEP 6 OF 6 · THE ADDRESSkey 03e775fd… 33 BHASH160 9c90f934… 20 Bscript 0014 ‖ hashbech32 bc1qnjg0jd8228…P2WPKH · BIP 84
One level at a timeThe path m/84'/0'/0'/1/0 as a stack of six plates: m, purpose 84′ (hardened), coin type 0′ (hardened), account 0′ (hardened), change 1 (public derivation), address index 0 (public derivation). The account's extended public key reaches the two public levels below it. Beside the stack, the current level; at the last step, the address. The status line below names the step.0ADDRESS INDEX1CHANGE0′ACCOUNT · HARDENED0′COIN TYPE · HARDENED84′PURPOSE · HARDENEDmm · MASTERACCOUNT XPUBREACHES BELOWSTEP 0 OF 6 · MASTER KEYmFrom the seed. Everything belowis derived from it.public key 03d902f3…STEP 1 OF 6 · PURPOSE84′Which convention the subtreefollows: 44′, 84′ or 86′.HARDENED: NEEDS THE PARENT’S PRIVATE KEYpublic key 03c098a6…parent fingerprint 73c5da0aSTEP 2 OF 6 · COIN TYPE0′One subtree per coin: 0′ forBitcoin, 1′ for testnet.HARDENED: NEEDS THE PARENT’S PRIVATE KEYpublic key 023f6221…parent fingerprint 7ead67a7STEP 3 OF 6 · ACCOUNT0′Independent identities, likebank accounts. From 0.HARDENED: NEEDS THE PARENT’S PRIVATE KEYpublic key 02707a62…parent fingerprint 7ef32bdbaccount xpub zpub6rFR7y4Q…PUBLISHED IN BIP 84 (LINE 75)STEP 4 OF 6 · CHANGE10: external chain (receiving).1: internal chain (change).PUBLIC: THE PARENT’S XPUB IS ENOUGHpublic key 03a9b41d…parent fingerprint fd13aac9STEP 5 OF 6 · ADDRESS INDEX0Addresses numbered from 0along the chain.PUBLIC: THE PARENT’S XPUB IS ENOUGHpublic key 03025324…parent fingerprint a5293563STEP 6 OF 6 · THE ADDRESSkey 03025324… 33 BHASH160 3e34985d… 20 Bscript 0014 ‖ hashbech32 bc1q8c6fshw2dl…P2WPKH · BIP 84
One level at a timeThe path m/84'/0'/0'/1/0 as a stack of six plates: m, purpose 84′ (hardened), coin type 0′ (hardened), account 0′ (hardened), change 1 (public derivation), address index 0 (public derivation). The account's extended public key reaches the two public levels below it. Beside the stack, the current level; at the last step, the address. The status line below names the step.0ADDRESS INDEX1CHANGE0′ACCOUNT · HARDENED0′COIN TYPE · HARDENED84′PURPOSE · HARDENEDmm · MASTERACCOUNT XPUB REACHES EVERYTHING BELOW THE LINESTEP 0 OF 6 · MASTER KEYmFrom the seed. Everything belowis derived from it.public key 03d902f3…STEP 1 OF 6 · PURPOSE84′Which convention the subtreefollows: 44′, 84′ or 86′.HARDENED: NEEDS THE PARENT’S PRIVATE KEYpublic key 03c098a6…parent fingerprint 73c5da0aSTEP 2 OF 6 · COIN TYPE0′One subtree per coin: 0′ forBitcoin, 1′ for testnet.HARDENED: NEEDS THE PARENT’S PRIVATE KEYpublic key 023f6221…parent fingerprint 7ead67a7STEP 3 OF 6 · ACCOUNT0′Independent identities, likebank accounts. From 0.HARDENED: NEEDS THE PARENT’S PRIVATE KEYpublic key 02707a62…parent fingerprint 7ef32bdbaccount xpub zpub6rFR7y4Q…PUBLISHED IN BIP 84 (LINE 75)STEP 4 OF 6 · CHANGE10: external chain (receiving).1: internal chain (change).PUBLIC: THE PARENT’S XPUB IS ENOUGHpublic key 03a9b41d…parent fingerprint fd13aac9STEP 5 OF 6 · ADDRESS INDEX0Addresses numbered from 0along the chain.PUBLIC: THE PARENT’S XPUB IS ENOUGHpublic key 03025324…parent fingerprint a5293563STEP 6 OF 6 · THE ADDRESSkey 03025324… 33 BHASH160 3e34985d… 20 Bscript 0014 ‖ hashbech32 bc1q8c6fshw2dl…P2WPKH · BIP 84
One level at a timeThe path m/86'/0'/0'/0/0 as a stack of six plates: m, purpose 86′ (hardened), coin type 0′ (hardened), account 0′ (hardened), change 0 (public derivation), address index 0 (public derivation). The account's extended public key reaches the two public levels below it. Beside the stack, the current level; at the last step, the address. The status line below names the step.0ADDRESS INDEX0CHANGE0′ACCOUNT · HARDENED0′COIN TYPE · HARDENED86′PURPOSE · HARDENEDmm · MASTERACCOUNT XPUBREACHES BELOWSTEP 0 OF 6 · MASTER KEYmFrom the seed. Everything belowis derived from it.public key 03d902f3…STEP 1 OF 6 · PURPOSE86′Which convention the subtreefollows: 44′, 84′ or 86′.HARDENED: NEEDS THE PARENT’S PRIVATE KEYpublic key 029d1bd8…parent fingerprint 73c5da0aSTEP 2 OF 6 · COIN TYPE0′One subtree per coin: 0′ forBitcoin, 1′ for testnet.HARDENED: NEEDS THE PARENT’S PRIVATE KEYpublic key 02b4d5ea…parent fingerprint 4e83b613STEP 3 OF 6 · ACCOUNT0′Independent identities, likebank accounts. From 0.HARDENED: NEEDS THE PARENT’S PRIVATE KEYpublic key 03418278…parent fingerprint 035270daaccount xpub xpub6BgBgses…PUBLISHED IN BIP 86 (LINE 92)STEP 4 OF 6 · CHANGE00: external chain (receiving).1: internal chain (change).PUBLIC: THE PARENT’S XPUB IS ENOUGHpublic key 0280acdd…parent fingerprint a7bea80dSTEP 5 OF 6 · ADDRESS INDEX0Addresses numbered from 0along the chain.PUBLIC: THE PARENT’S XPUB IS ENOUGHpublic key 03cc8a4b…parent fingerprint dd94e1d0STEP 6 OF 6 · THE ADDRESSkey 03cc8a4b… 33 Binternal key P = lift_x(x) cc8a4b…TapTweak of P alone t 2ca01e…output key Q = P + t·G a60869…5120 ‖ Q · bech32m bc1p5cyxnu…P2TR KEY PATH · BIP 86
One level at a timeThe path m/86'/0'/0'/0/0 as a stack of six plates: m, purpose 86′ (hardened), coin type 0′ (hardened), account 0′ (hardened), change 0 (public derivation), address index 0 (public derivation). The account's extended public key reaches the two public levels below it. Beside the stack, the current level; at the last step, the address. The status line below names the step.0ADDRESS INDEX0CHANGE0′ACCOUNT · HARDENED0′COIN TYPE · HARDENED86′PURPOSE · HARDENEDmm · MASTERACCOUNT XPUB REACHES EVERYTHING BELOW THE LINESTEP 0 OF 6 · MASTER KEYmFrom the seed. Everything belowis derived from it.public key 03d902f3…STEP 1 OF 6 · PURPOSE86′Which convention the subtreefollows: 44′, 84′ or 86′.HARDENED: NEEDS THE PARENT’S PRIVATE KEYpublic key 029d1bd8…parent fingerprint 73c5da0aSTEP 2 OF 6 · COIN TYPE0′One subtree per coin: 0′ forBitcoin, 1′ for testnet.HARDENED: NEEDS THE PARENT’S PRIVATE KEYpublic key 02b4d5ea…parent fingerprint 4e83b613STEP 3 OF 6 · ACCOUNT0′Independent identities, likebank accounts. From 0.HARDENED: NEEDS THE PARENT’S PRIVATE KEYpublic key 03418278…parent fingerprint 035270daaccount xpub xpub6BgBgses…PUBLISHED IN BIP 86 (LINE 92)STEP 4 OF 6 · CHANGE00: external chain (receiving).1: internal chain (change).PUBLIC: THE PARENT’S XPUB IS ENOUGHpublic key 0280acdd…parent fingerprint a7bea80dSTEP 5 OF 6 · ADDRESS INDEX0Addresses numbered from 0along the chain.PUBLIC: THE PARENT’S XPUB IS ENOUGHpublic key 03cc8a4b…parent fingerprint dd94e1d0STEP 6 OF 6 · THE ADDRESSkey 03cc8a4b… 33 Binternal key P = lift_x(x) cc8a4b…TapTweak of P alone t 2ca01e…output key Q = P + t·G a60869…5120 ‖ Q · bech32m bc1p5cyxnu…P2TR KEY PATH · BIP 86
One level at a timeThe path m/86'/0'/0'/0/1 as a stack of six plates: m, purpose 86′ (hardened), coin type 0′ (hardened), account 0′ (hardened), change 0 (public derivation), address index 1 (public derivation). The account's extended public key reaches the two public levels below it. Beside the stack, the current level; at the last step, the address. The status line below names the step.1ADDRESS INDEX0CHANGE0′ACCOUNT · HARDENED0′COIN TYPE · HARDENED86′PURPOSE · HARDENEDmm · MASTERACCOUNT XPUBREACHES BELOWSTEP 0 OF 6 · MASTER KEYmFrom the seed. Everything belowis derived from it.public key 03d902f3…STEP 1 OF 6 · PURPOSE86′Which convention the subtreefollows: 44′, 84′ or 86′.HARDENED: NEEDS THE PARENT’S PRIVATE KEYpublic key 029d1bd8…parent fingerprint 73c5da0aSTEP 2 OF 6 · COIN TYPE0′One subtree per coin: 0′ forBitcoin, 1′ for testnet.HARDENED: NEEDS THE PARENT’S PRIVATE KEYpublic key 02b4d5ea…parent fingerprint 4e83b613STEP 3 OF 6 · ACCOUNT0′Independent identities, likebank accounts. From 0.HARDENED: NEEDS THE PARENT’S PRIVATE KEYpublic key 03418278…parent fingerprint 035270daaccount xpub xpub6BgBgses…PUBLISHED IN BIP 86 (LINE 92)STEP 4 OF 6 · CHANGE00: external chain (receiving).1: internal chain (change).PUBLIC: THE PARENT’S XPUB IS ENOUGHpublic key 0280acdd…parent fingerprint a7bea80dSTEP 5 OF 6 · ADDRESS INDEX1Addresses numbered from 0along the chain.PUBLIC: THE PARENT’S XPUB IS ENOUGHpublic key 0283dfe8…parent fingerprint dd94e1d0STEP 6 OF 6 · THE ADDRESSkey 0283dfe8… 33 Binternal key P = lift_x(x) 83dfe8…TapTweak of P alone t 84a88d…output key Q = P + t·G a82f29…5120 ‖ Q · bech32m bc1p4qhjn9…P2TR KEY PATH · BIP 86
One level at a timeThe path m/86'/0'/0'/0/1 as a stack of six plates: m, purpose 86′ (hardened), coin type 0′ (hardened), account 0′ (hardened), change 0 (public derivation), address index 1 (public derivation). The account's extended public key reaches the two public levels below it. Beside the stack, the current level; at the last step, the address. The status line below names the step.1ADDRESS INDEX0CHANGE0′ACCOUNT · HARDENED0′COIN TYPE · HARDENED86′PURPOSE · HARDENEDmm · MASTERACCOUNT XPUB REACHES EVERYTHING BELOW THE LINESTEP 0 OF 6 · MASTER KEYmFrom the seed. Everything belowis derived from it.public key 03d902f3…STEP 1 OF 6 · PURPOSE86′Which convention the subtreefollows: 44′, 84′ or 86′.HARDENED: NEEDS THE PARENT’S PRIVATE KEYpublic key 029d1bd8…parent fingerprint 73c5da0aSTEP 2 OF 6 · COIN TYPE0′One subtree per coin: 0′ forBitcoin, 1′ for testnet.HARDENED: NEEDS THE PARENT’S PRIVATE KEYpublic key 02b4d5ea…parent fingerprint 4e83b613STEP 3 OF 6 · ACCOUNT0′Independent identities, likebank accounts. From 0.HARDENED: NEEDS THE PARENT’S PRIVATE KEYpublic key 03418278…parent fingerprint 035270daaccount xpub xpub6BgBgses…PUBLISHED IN BIP 86 (LINE 92)STEP 4 OF 6 · CHANGE00: external chain (receiving).1: internal chain (change).PUBLIC: THE PARENT’S XPUB IS ENOUGHpublic key 0280acdd…parent fingerprint a7bea80dSTEP 5 OF 6 · ADDRESS INDEX1Addresses numbered from 0along the chain.PUBLIC: THE PARENT’S XPUB IS ENOUGHpublic key 0283dfe8…parent fingerprint dd94e1d0STEP 6 OF 6 · THE ADDRESSkey 0283dfe8… 33 Binternal key P = lift_x(x) 83dfe8…TapTweak of P alone t 84a88d…output key Q = P + t·G a82f29…5120 ‖ Q · bech32m bc1p4qhjn9…P2TR KEY PATH · BIP 86
One level at a timeThe path m/86'/0'/0'/1/0 as a stack of six plates: m, purpose 86′ (hardened), coin type 0′ (hardened), account 0′ (hardened), change 1 (public derivation), address index 0 (public derivation). The account's extended public key reaches the two public levels below it. Beside the stack, the current level; at the last step, the address. The status line below names the step.0ADDRESS INDEX1CHANGE0′ACCOUNT · HARDENED0′COIN TYPE · HARDENED86′PURPOSE · HARDENEDmm · MASTERACCOUNT XPUBREACHES BELOWSTEP 0 OF 6 · MASTER KEYmFrom the seed. Everything belowis derived from it.public key 03d902f3…STEP 1 OF 6 · PURPOSE86′Which convention the subtreefollows: 44′, 84′ or 86′.HARDENED: NEEDS THE PARENT’S PRIVATE KEYpublic key 029d1bd8…parent fingerprint 73c5da0aSTEP 2 OF 6 · COIN TYPE0′One subtree per coin: 0′ forBitcoin, 1′ for testnet.HARDENED: NEEDS THE PARENT’S PRIVATE KEYpublic key 02b4d5ea…parent fingerprint 4e83b613STEP 3 OF 6 · ACCOUNT0′Independent identities, likebank accounts. From 0.HARDENED: NEEDS THE PARENT’S PRIVATE KEYpublic key 03418278…parent fingerprint 035270daaccount xpub xpub6BgBgses…PUBLISHED IN BIP 86 (LINE 92)STEP 4 OF 6 · CHANGE10: external chain (receiving).1: internal chain (change).PUBLIC: THE PARENT’S XPUB IS ENOUGHpublic key 02bf10eb…parent fingerprint a7bea80dSTEP 5 OF 6 · ADDRESS INDEX0Addresses numbered from 0along the chain.PUBLIC: THE PARENT’S XPUB IS ENOUGHpublic key 02399f1b…parent fingerprint 7c883574STEP 6 OF 6 · THE ADDRESSkey 02399f1b… 33 Binternal key P = lift_x(x) 399f1b…TapTweak of P alone t 563b7c…output key Q = P + t·G 882d74…5120 ‖ Q · bech32m bc1p3qkhfe…P2TR KEY PATH · BIP 86
One level at a timeThe path m/86'/0'/0'/1/0 as a stack of six plates: m, purpose 86′ (hardened), coin type 0′ (hardened), account 0′ (hardened), change 1 (public derivation), address index 0 (public derivation). The account's extended public key reaches the two public levels below it. Beside the stack, the current level; at the last step, the address. The status line below names the step.0ADDRESS INDEX1CHANGE0′ACCOUNT · HARDENED0′COIN TYPE · HARDENED86′PURPOSE · HARDENEDmm · MASTERACCOUNT XPUB REACHES EVERYTHING BELOW THE LINESTEP 0 OF 6 · MASTER KEYmFrom the seed. Everything belowis derived from it.public key 03d902f3…STEP 1 OF 6 · PURPOSE86′Which convention the subtreefollows: 44′, 84′ or 86′.HARDENED: NEEDS THE PARENT’S PRIVATE KEYpublic key 029d1bd8…parent fingerprint 73c5da0aSTEP 2 OF 6 · COIN TYPE0′One subtree per coin: 0′ forBitcoin, 1′ for testnet.HARDENED: NEEDS THE PARENT’S PRIVATE KEYpublic key 02b4d5ea…parent fingerprint 4e83b613STEP 3 OF 6 · ACCOUNT0′Independent identities, likebank accounts. From 0.HARDENED: NEEDS THE PARENT’S PRIVATE KEYpublic key 03418278…parent fingerprint 035270daaccount xpub xpub6BgBgses…PUBLISHED IN BIP 86 (LINE 92)STEP 4 OF 6 · CHANGE10: external chain (receiving).1: internal chain (change).PUBLIC: THE PARENT’S XPUB IS ENOUGHpublic key 02bf10eb…parent fingerprint a7bea80dSTEP 5 OF 6 · ADDRESS INDEX0Addresses numbered from 0along the chain.PUBLIC: THE PARENT’S XPUB IS ENOUGHpublic key 02399f1b…parent fingerprint 7c883574STEP 6 OF 6 · THE ADDRESSkey 02399f1b… 33 Binternal key P = lift_x(x) 399f1b…TapTweak of P alone t 563b7c…output key Q = P + t·G 882d74…5120 ‖ Q · bech32m bc1p3qkhfe…P2TR KEY PATH · BIP 86
One level at a timeThe path m/44'/0'/0'/0/0 as a stack of six plates: m, purpose 44′ (hardened), coin type 0′ (hardened), account 0′ (hardened), change 0 (public derivation), address index 0 (public derivation). The account's extended public key reaches the two public levels below it. Beside the stack, the current level; at the last step, the address. The status line below names the step.0ADDRESS INDEX0CHANGE0′ACCOUNT · HARDENED0′COIN TYPE · HARDENED44′PURPOSE · HARDENEDmm · MASTERACCOUNT XPUBREACHES BELOWSTEP 0 OF 6 · MASTER KEYmFrom the seed. Everything belowis derived from it.public key 03d902f3…KEYS: BIP 84'S MNEMONIC · BIP 44 PUBLISHES NONESTEP 1 OF 6 · PURPOSE44′Which convention the subtreefollows: 44′, 84′ or 86′.HARDENED: NEEDS THE PARENT’S PRIVATE KEYpublic key 03428a2d…parent fingerprint 73c5da0aKEYS: BIP 84'S MNEMONIC · BIP 44 PUBLISHES NONESTEP 2 OF 6 · COIN TYPE0′One subtree per coin: 0′ forBitcoin, 1′ for testnet.HARDENED: NEEDS THE PARENT’S PRIVATE KEYpublic key 03f72f0e…parent fingerprint 88b3582bKEYS: BIP 84'S MNEMONIC · BIP 44 PUBLISHES NONESTEP 3 OF 6 · ACCOUNT0′Independent identities, likebank accounts. From 0.HARDENED: NEEDS THE PARENT’S PRIVATE KEYpublic key 03774c91…parent fingerprint 155bca59account xpub xpub6BosfCni…COMPUTED: BIP 44 PUBLISHES NO KEYSSTEP 4 OF 6 · CHANGE00: external chain (receiving).1: internal chain (change).PUBLIC: THE PARENT’S XPUB IS ENOUGHpublic key 0386b865…parent fingerprint 6cc9f252KEYS: BIP 84'S MNEMONIC · BIP 44 PUBLISHES NONESTEP 5 OF 6 · ADDRESS INDEX0Addresses numbered from 0along the chain.PUBLIC: THE PARENT’S XPUB IS ENOUGHpublic key 03aaeb52…parent fingerprint 1962ab58KEYS: BIP 84'S MNEMONIC · BIP 44 PUBLISHES NONESTEP 6 OF 6 · THE ADDRESSkey 03aaeb52… 33 BBIP 44 NAMES NO SCRIPT TYPEAND NO ADDRESS FORMATKEY FROM BIP 84'S MNEMONIC · BIP 44 PUBLISHES NONE
One level at a timeThe path m/44'/0'/0'/0/0 as a stack of six plates: m, purpose 44′ (hardened), coin type 0′ (hardened), account 0′ (hardened), change 0 (public derivation), address index 0 (public derivation). The account's extended public key reaches the two public levels below it. Beside the stack, the current level; at the last step, the address. The status line below names the step.0ADDRESS INDEX0CHANGE0′ACCOUNT · HARDENED0′COIN TYPE · HARDENED44′PURPOSE · HARDENEDmm · MASTERACCOUNT XPUB REACHES EVERYTHING BELOW THE LINESTEP 0 OF 6 · MASTER KEYmFrom the seed. Everything belowis derived from it.public key 03d902f3…KEYS: BIP 84'S MNEMONIC · BIP 44 PUBLISHES NONESTEP 1 OF 6 · PURPOSE44′Which convention the subtreefollows: 44′, 84′ or 86′.HARDENED: NEEDS THE PARENT’S PRIVATE KEYpublic key 03428a2d…parent fingerprint 73c5da0aKEYS: BIP 84'S MNEMONIC · BIP 44 PUBLISHES NONESTEP 2 OF 6 · COIN TYPE0′One subtree per coin: 0′ forBitcoin, 1′ for testnet.HARDENED: NEEDS THE PARENT’S PRIVATE KEYpublic key 03f72f0e…parent fingerprint 88b3582bKEYS: BIP 84'S MNEMONIC · BIP 44 PUBLISHES NONESTEP 3 OF 6 · ACCOUNT0′Independent identities, likebank accounts. From 0.HARDENED: NEEDS THE PARENT’S PRIVATE KEYpublic key 03774c91…parent fingerprint 155bca59account xpub xpub6BosfCni…COMPUTED: BIP 44 PUBLISHES NO KEYSSTEP 4 OF 6 · CHANGE00: external chain (receiving).1: internal chain (change).PUBLIC: THE PARENT’S XPUB IS ENOUGHpublic key 0386b865…parent fingerprint 6cc9f252KEYS: BIP 84'S MNEMONIC · BIP 44 PUBLISHES NONESTEP 5 OF 6 · ADDRESS INDEX0Addresses numbered from 0along the chain.PUBLIC: THE PARENT’S XPUB IS ENOUGHpublic key 03aaeb52…parent fingerprint 1962ab58KEYS: BIP 84'S MNEMONIC · BIP 44 PUBLISHES NONESTEP 6 OF 6 · THE ADDRESSkey 03aaeb52… 33 BBIP 44 NAMES NO SCRIPT TYPEAND NO ADDRESS FORMATKEY FROM BIP 84'S MNEMONIC · BIP 44 PUBLISHES NONE
One level at a timeThe path m/44'/0'/0'/0/1 as a stack of six plates: m, purpose 44′ (hardened), coin type 0′ (hardened), account 0′ (hardened), change 0 (public derivation), address index 1 (public derivation). The account's extended public key reaches the two public levels below it. Beside the stack, the current level; at the last step, the address. The status line below names the step.1ADDRESS INDEX0CHANGE0′ACCOUNT · HARDENED0′COIN TYPE · HARDENED44′PURPOSE · HARDENEDmm · MASTERACCOUNT XPUBREACHES BELOWSTEP 0 OF 6 · MASTER KEYmFrom the seed. Everything belowis derived from it.public key 03d902f3…KEYS: BIP 84'S MNEMONIC · BIP 44 PUBLISHES NONESTEP 1 OF 6 · PURPOSE44′Which convention the subtreefollows: 44′, 84′ or 86′.HARDENED: NEEDS THE PARENT’S PRIVATE KEYpublic key 03428a2d…parent fingerprint 73c5da0aKEYS: BIP 84'S MNEMONIC · BIP 44 PUBLISHES NONESTEP 2 OF 6 · COIN TYPE0′One subtree per coin: 0′ forBitcoin, 1′ for testnet.HARDENED: NEEDS THE PARENT’S PRIVATE KEYpublic key 03f72f0e…parent fingerprint 88b3582bKEYS: BIP 84'S MNEMONIC · BIP 44 PUBLISHES NONESTEP 3 OF 6 · ACCOUNT0′Independent identities, likebank accounts. From 0.HARDENED: NEEDS THE PARENT’S PRIVATE KEYpublic key 03774c91…parent fingerprint 155bca59account xpub xpub6BosfCni…COMPUTED: BIP 44 PUBLISHES NO KEYSSTEP 4 OF 6 · CHANGE00: external chain (receiving).1: internal chain (change).PUBLIC: THE PARENT’S XPUB IS ENOUGHpublic key 0386b865…parent fingerprint 6cc9f252KEYS: BIP 84'S MNEMONIC · BIP 44 PUBLISHES NONESTEP 5 OF 6 · ADDRESS INDEX1Addresses numbered from 0along the chain.PUBLIC: THE PARENT’S XPUB IS ENOUGHpublic key 02dfcaec…parent fingerprint 1962ab58KEYS: BIP 84'S MNEMONIC · BIP 44 PUBLISHES NONESTEP 6 OF 6 · THE ADDRESSkey 02dfcaec… 33 BBIP 44 NAMES NO SCRIPT TYPEAND NO ADDRESS FORMATKEY FROM BIP 84'S MNEMONIC · BIP 44 PUBLISHES NONE
One level at a timeThe path m/44'/0'/0'/0/1 as a stack of six plates: m, purpose 44′ (hardened), coin type 0′ (hardened), account 0′ (hardened), change 0 (public derivation), address index 1 (public derivation). The account's extended public key reaches the two public levels below it. Beside the stack, the current level; at the last step, the address. The status line below names the step.1ADDRESS INDEX0CHANGE0′ACCOUNT · HARDENED0′COIN TYPE · HARDENED44′PURPOSE · HARDENEDmm · MASTERACCOUNT XPUB REACHES EVERYTHING BELOW THE LINESTEP 0 OF 6 · MASTER KEYmFrom the seed. Everything belowis derived from it.public key 03d902f3…KEYS: BIP 84'S MNEMONIC · BIP 44 PUBLISHES NONESTEP 1 OF 6 · PURPOSE44′Which convention the subtreefollows: 44′, 84′ or 86′.HARDENED: NEEDS THE PARENT’S PRIVATE KEYpublic key 03428a2d…parent fingerprint 73c5da0aKEYS: BIP 84'S MNEMONIC · BIP 44 PUBLISHES NONESTEP 2 OF 6 · COIN TYPE0′One subtree per coin: 0′ forBitcoin, 1′ for testnet.HARDENED: NEEDS THE PARENT’S PRIVATE KEYpublic key 03f72f0e…parent fingerprint 88b3582bKEYS: BIP 84'S MNEMONIC · BIP 44 PUBLISHES NONESTEP 3 OF 6 · ACCOUNT0′Independent identities, likebank accounts. From 0.HARDENED: NEEDS THE PARENT’S PRIVATE KEYpublic key 03774c91…parent fingerprint 155bca59account xpub xpub6BosfCni…COMPUTED: BIP 44 PUBLISHES NO KEYSSTEP 4 OF 6 · CHANGE00: external chain (receiving).1: internal chain (change).PUBLIC: THE PARENT’S XPUB IS ENOUGHpublic key 0386b865…parent fingerprint 6cc9f252KEYS: BIP 84'S MNEMONIC · BIP 44 PUBLISHES NONESTEP 5 OF 6 · ADDRESS INDEX1Addresses numbered from 0along the chain.PUBLIC: THE PARENT’S XPUB IS ENOUGHpublic key 02dfcaec…parent fingerprint 1962ab58KEYS: BIP 84'S MNEMONIC · BIP 44 PUBLISHES NONESTEP 6 OF 6 · THE ADDRESSkey 02dfcaec… 33 BBIP 44 NAMES NO SCRIPT TYPEAND NO ADDRESS FORMATKEY FROM BIP 84'S MNEMONIC · BIP 44 PUBLISHES NONE
One level at a timeThe path m/44'/0'/0'/1/0 as a stack of six plates: m, purpose 44′ (hardened), coin type 0′ (hardened), account 0′ (hardened), change 1 (public derivation), address index 0 (public derivation). The account's extended public key reaches the two public levels below it. Beside the stack, the current level; at the last step, the address. The status line below names the step.0ADDRESS INDEX1CHANGE0′ACCOUNT · HARDENED0′COIN TYPE · HARDENED44′PURPOSE · HARDENEDmm · MASTERACCOUNT XPUBREACHES BELOWSTEP 0 OF 6 · MASTER KEYmFrom the seed. Everything belowis derived from it.public key 03d902f3…KEYS: BIP 84'S MNEMONIC · BIP 44 PUBLISHES NONESTEP 1 OF 6 · PURPOSE44′Which convention the subtreefollows: 44′, 84′ or 86′.HARDENED: NEEDS THE PARENT’S PRIVATE KEYpublic key 03428a2d…parent fingerprint 73c5da0aKEYS: BIP 84'S MNEMONIC · BIP 44 PUBLISHES NONESTEP 2 OF 6 · COIN TYPE0′One subtree per coin: 0′ forBitcoin, 1′ for testnet.HARDENED: NEEDS THE PARENT’S PRIVATE KEYpublic key 03f72f0e…parent fingerprint 88b3582bKEYS: BIP 84'S MNEMONIC · BIP 44 PUBLISHES NONESTEP 3 OF 6 · ACCOUNT0′Independent identities, likebank accounts. From 0.HARDENED: NEEDS THE PARENT’S PRIVATE KEYpublic key 03774c91…parent fingerprint 155bca59account xpub xpub6BosfCni…COMPUTED: BIP 44 PUBLISHES NO KEYSSTEP 4 OF 6 · CHANGE10: external chain (receiving).1: internal chain (change).PUBLIC: THE PARENT’S XPUB IS ENOUGHpublic key 02460c85…parent fingerprint 6cc9f252KEYS: BIP 84'S MNEMONIC · BIP 44 PUBLISHES NONESTEP 5 OF 6 · ADDRESS INDEX0Addresses numbered from 0along the chain.PUBLIC: THE PARENT’S XPUB IS ENOUGHpublic key 03498b3a…parent fingerprint 8c7306cdKEYS: BIP 84'S MNEMONIC · BIP 44 PUBLISHES NONESTEP 6 OF 6 · THE ADDRESSkey 03498b3a… 33 BBIP 44 NAMES NO SCRIPT TYPEAND NO ADDRESS FORMATKEY FROM BIP 84'S MNEMONIC · BIP 44 PUBLISHES NONE
One level at a timeThe path m/44'/0'/0'/1/0 as a stack of six plates: m, purpose 44′ (hardened), coin type 0′ (hardened), account 0′ (hardened), change 1 (public derivation), address index 0 (public derivation). The account's extended public key reaches the two public levels below it. Beside the stack, the current level; at the last step, the address. The status line below names the step.0ADDRESS INDEX1CHANGE0′ACCOUNT · HARDENED0′COIN TYPE · HARDENED44′PURPOSE · HARDENEDmm · MASTERACCOUNT XPUB REACHES EVERYTHING BELOW THE LINESTEP 0 OF 6 · MASTER KEYmFrom the seed. Everything belowis derived from it.public key 03d902f3…KEYS: BIP 84'S MNEMONIC · BIP 44 PUBLISHES NONESTEP 1 OF 6 · PURPOSE44′Which convention the subtreefollows: 44′, 84′ or 86′.HARDENED: NEEDS THE PARENT’S PRIVATE KEYpublic key 03428a2d…parent fingerprint 73c5da0aKEYS: BIP 84'S MNEMONIC · BIP 44 PUBLISHES NONESTEP 2 OF 6 · COIN TYPE0′One subtree per coin: 0′ forBitcoin, 1′ for testnet.HARDENED: NEEDS THE PARENT’S PRIVATE KEYpublic key 03f72f0e…parent fingerprint 88b3582bKEYS: BIP 84'S MNEMONIC · BIP 44 PUBLISHES NONESTEP 3 OF 6 · ACCOUNT0′Independent identities, likebank accounts. From 0.HARDENED: NEEDS THE PARENT’S PRIVATE KEYpublic key 03774c91…parent fingerprint 155bca59account xpub xpub6BosfCni…COMPUTED: BIP 44 PUBLISHES NO KEYSSTEP 4 OF 6 · CHANGE10: external chain (receiving).1: internal chain (change).PUBLIC: THE PARENT’S XPUB IS ENOUGHpublic key 02460c85…parent fingerprint 6cc9f252KEYS: BIP 84'S MNEMONIC · BIP 44 PUBLISHES NONESTEP 5 OF 6 · ADDRESS INDEX0Addresses numbered from 0along the chain.PUBLIC: THE PARENT’S XPUB IS ENOUGHpublic key 03498b3a…parent fingerprint 8c7306cdKEYS: BIP 84'S MNEMONIC · BIP 44 PUBLISHES NONESTEP 6 OF 6 · THE ADDRESSkey 03498b3a… 33 BBIP 44 NAMES NO SCRIPT TYPEAND NO ADDRESS FORMATKEY FROM BIP 84'S MNEMONIC · BIP 44 PUBLISHES NONE

BIP 84 · P2WPKH, first receiving: HASH160 of the key goes into 0014 ‖ hash; the bech32 address is bc1qcr8te4kr609gcawutmrza0j4xv80jy8z306fyu.

Exact values for this path
Path
m/84'/0'/0'/0/0
Public key at the master key
03d902f35f560e0470c63313c7369168d9d7df2d49bf295fd9fb7cb109ccee0494
Public key at purpose 84′
03c098a6743927554712f1cbc240ef73190db1b7633b08d54ff853899439c102b5
Public key at coin type 0′
023f6221a9fcbd1eed48d8d6a538fd04688aa6adbd9bb6733996e7a7e1636f7fd4
Public key at account 0′
02707a62fdacc26ea9b63b1c197906f56ee0180d0bcf1966e1a2da34f5f3a09a9b
Public key at change 0
02360e9ef11126e1a27808ce81206c264de9326f8fa5a4d2c63bf20f235ecf650b
Public key at address index 0
0330d54fd0dd420a6e5f8d3624f5f3482cae350f79d5f0753bf5beef9c2d91af3c
Account extended public key (BIP 84 line 75)
zpub6rFR7y4Q2AijBEqTUquhVz398htDFrtymD9xYYfG1m4wAcvPhXNfE3EfH1r1ADqtfSdVCToUG868RvUUkgDKf31mGDtKsAYz2oz2AGutZYs
HASH160
c0cebcd6c3d3ca8c75dc5ec62ebe55330ef910e2
scriptPubKey
0014c0cebcd6c3d3ca8c75dc5ec62ebe55330ef910e2
Address (checked against lines 79, 80)
bc1qcr8te4kr609gcawutmrza0j4xv80jy8z306fyu

BIP 84 and BIP 86 test vectors from the “abandon … about” mnemonic; every key and address was derived by the tested model and checked against the vectors at build time. BIP 44 publishes paths but no keys: its keys come from the same mnemonic. Public test material; never use it for funds.

Published paths from BIPs 84, 86 and 44, stepped from the master key down to the address. A black tab marks a hardened level.5151617

The line between the third and fourth levels matters most. Above it, each step is hardened and needs the parent’s private key. Below it, change and index use public derivation, which anyone holding the parent’s extended public key can do.5910

An account’s extended public key can derive every receiving and change address in that account. The model demonstrates this with the published account public keys: it re-derives every published address below them. Sharing an account xpub therefore reveals the account’s address history and future addresses. The xpub alone does not let its holder spend funds.17

Fig. A12.4 What one account xpub reaches

What one account xpub reachesThe account extended public key of m/84'/0'/0' (zpub6rFR7y4Q2AijBEqTUquhVz398htDFrtymD9xYYfG1m4wAcvPhXNfE3EfH1r1ADqtfSdVCToUG868RvUUkgDKf31mGDtKsAYz2oz2AGutZYs) and the two public levels below it. Chain 0 (receiving): index 0, bc1qcr8te4kr609gcawutmrza0j4xv80jy8z306fyu, re-derived from the xpub alone and equal to BIP 84 line 80; index 1, bc1qnjg0jd8228aq7egyzacy8cys3knf9xvrerkf9g, re-derived from the xpub alone and equal to BIP 84 line 85, and every later index. Chain 1 (change): index 0, bc1q8c6fshw2dlwun7ekn9qwf37cu2rn755upcp6el, re-derived from the xpub alone and equal to BIP 84 line 90, and every later index. The xpub reveals all of them but cannot spend.ACCOUNT XPUB (ZPUB) · m/84′/0′/0′zpub6rFR7y4Q2Aij…PUBLISHED, BIP 84 LINE 750EXTERNAL · RECEIVING0bc1qcr8te4kr609g…= LINE 801bc1qnjg0jd8228aq…= LINE 85… AND EVERY LATER INDEX1INTERNAL · CHANGE0bc1q8c6fshw2dlwu…= LINE 90… AND EVERY LATER INDEXALL RE-DERIVED FROM THE XPUB ALONE · IT CANNOT SPEND
Exact values
Account extended public key
zpub6rFR7y4Q2AijBEqTUquhVz398htDFrtymD9xYYfG1m4wAcvPhXNfE3EfH1r1ADqtfSdVCToUG868RvUUkgDKf31mGDtKsAYz2oz2AGutZYs
m/84'/0'/0'/0/0
bc1qcr8te4kr609gcawutmrza0j4xv80jy8z306fyu
m/84'/0'/0'/0/1
bc1qnjg0jd8228aq7egyzacy8cys3knf9xvrerkf9g
m/84'/0'/0'/1/0
bc1q8c6fshw2dlwun7ekn9qwf37cu2rn755upcp6el
BIP 84’s account extended public key and every address its test vectors publish below it, receiving and change, each re-derived from the xpub alone.1517

For BIP 84’s first receiving address, derivation produces a compressed public key. Its hash supplies the 20 bytes in the output, which the address encodes with Bech32. In BIP 86, the derived key’s x coordinate identifies the internal key. A tweak produces the output key encoded in the address.151819

The spending witnesses differ too. BIP 84 expects a signature and public key. BIP 86 expects a signature alone. Both leave the scriptSig empty.20

Fig. A12.5 What a spend carries

What a spend carriesSpending a BIP 84 output: the scriptSig is empty, and the witness holds two items, a signature and then the public key. Spending a BIP 86 output: the scriptSig is empty, and the witness holds one item, a signature.BIP 84 · P2WPKHscriptSig: emptyWITNESSsignaturepublic keyBIP 86 · P2TR KEY PATHscriptSig: emptyWITNESSsignature
What a spend carriesSpending a BIP 84 output: the scriptSig is empty, and the witness holds two items, a signature and then the public key. Spending a BIP 86 output: the scriptSig is empty, and the witness holds one item, a signature.BIP 84 · P2WPKHscriptSig: emptyWITNESSsignaturepublic keyBIP 86 · P2TR KEY PATHscriptSig: emptyWITNESSsignature
Both outputs are spent with an empty scriptSig. BIP 84’s witness carries a signature and the public key; BIP 86’s carries only a signature.20
Caveat

An account extended public key is not a single address. It exposes every receiving and change address of that account, which is why sharing it is a privacy decision.91017

Published values behind the explorer

BIP 84 and BIP 86 each publish test vectors from the same well-known mnemonic: the root keys, the first account’s keys, and three addresses, two receiving and one change. Step down their paths in Fig. A12.3 above. Every value is derived by this site’s tested BIP 32 code. The account keys and every published leaf value are checked against the vectors when the site is built, and the intermediate values are implied by them.15

What the purpose decides

BIP 44 stops at the key. It defines the path and nothing about the script that key should be used in, nor the address format. Later BIPs treat the purpose value as what signals the script type.516

BIP 84 specifies the output type for SegWit version 0. It keeps BIP 44’s path structure and changes only the purpose, 84′. Each key produces a pay-to-witness-public-key-hash output: 0x0014 followed by the key’s 20-byte hash. The address encodes this with Bech32. BIP 84 also assigns different version bytes to extended keys, so they print as zpub and zprv instead of xpub and xprv.1821

The author’s reason was compatibility in one direction: dedicated SegWit accounts mean only wallets that implement the scheme will find them. BIP 84 is deliberately not backwards compatible, and a wallet that does not know it will not discover the accounts at all.322

Fig. A12.6 One seed, three different destinations

One seed, three different destinationsm/44'/0'/0'/0/0 gives public key 03aaeb52dd7494c361049de67cc680e83ebcbbbdbeb13637d92cd845f70308af5e. BIP 44 does not specify an output script; this key is computed from BIP 84's public test mnemonic. m/84'/0'/0'/0/0 gives public key 0330d54fd0dd420a6e5f8d3624f5f3482cae350f79d5f0753bf5beef9c2d91af3c. P2WPKH, address bc1qcr8te4kr609gcawutmrza0j4xv80jy8z306fyu. m/86'/0'/0'/0/0 gives public key 03cc8a4bc64d897bddc5fbc2f670f7a8ba0b386779106cf1223c6fc5d7cd6fc115. P2TR KEY PATH, address bc1p5cyxnuxmeuwuvkwfem96lqzszd02n6xdcjrs20cac6yqjjwudpxqkedrcr.SAME TEST SEED · DIFFERENT HARDENED PURPOSESm/44'/0'/0'/0/0SCRIPT NOT SPECIFIEDkey 03aaeb…output chosen separatelyversion bytes not specifiedm/84'/0'/0'/0/0P2WPKHkey 0330d5…bc1qcr8te4kr6…zpub / zprvm/86'/0'/0'/0/0P2TR KEY PATHkey 03cc8a…bc1p5cyxnuxme…xpub / xprvBIP 44 KEY: COMPUTED FROM BIP 84'S TEST MNEMONIC
Exact first receiving keys and addresses
m/44'/0'/0'/0/0
03aaeb52dd7494c361049de67cc680e83ebcbbbdbeb13637d92cd845f70308af5e
m/84'/0'/0'/0/0
0330d54fd0dd420a6e5f8d3624f5f3482cae350f79d5f0753bf5beef9c2d91af3c
bc1qcr8te4kr609gcawutmrza0j4xv80jy8z306fyu
m/86'/0'/0'/0/0
03cc8a4bc64d897bddc5fbc2f670f7a8ba0b386779106cf1223c6fc5d7cd6fc115
bc1p5cyxnuxmeuwuvkwfem96lqzszd02n6xdcjrs20cac6yqjjwudpxqkedrcr
Changing the hardened purpose changes every key below it. BIP 84 and BIP 86 also specify how to turn their keys into output scripts; BIP 44 itself does not.151618192123

BIP 86 specifies the output type for Taproot. Purpose 86′ marks keys used as the internal key of a single-key P2TR output. The wallet derives a tweak by hashing the internal key without a script-tree root, then applies it to obtain the output key. This commits to an unspendable script path, as BIP 341 recommends.19

The wallet puts the result into a version 1 output: 0x5120 followed by the 32-byte output key. BIP 86 defines no alternate version bytes. Its test vectors print as xprv and xpub.1519

A seed gives the wallet its tree of keys. A path convention tells it where to look, and an output convention tells it what to look for. Restoring the keys and finding their coins are related, but separate, jobs.16232425

Evidence

Each numbered marker in the text points here, and the ↩ links lead back to the text. Quotes are verbatim from the BIP files at commit 3a10b5b, wiki markup included. Links open the exact lines. Labels say what kind of statement each entry is: a rule, the author’s rationale, history, a test vector, or our own inference.

  1. ↩ a b Rule BIP 44 defines a logical hierarchy on top of BIP 32's derivation algorithm and BIP 43's purpose scheme; it is a particular application of BIP 43.

    Quoted source text (1)

    This BIP defines a logical hierarchy for deterministic wallets based on an algorithm described in BIP-0032 (BIP32 from now on) and purpose scheme described in BIP-0043 (BIP43 from now on). This BIP is a particular application of BIP43.

    BIP 44, lines 17–21
  2. ↩ a b Author’s rationale BIP 44's hierarchy is meant to handle multiple coins, multiple accounts, external and internal chains per account, and millions of addresses per chain.

    Quoted source text (1)

    It allows the handling of multiple coins, multiple accounts, external and internal chains per account and millions of addresses per chain.

    BIP 44, lines 25–27
  3. ↩ a b Author’s rationale BIP 84's motivation: a common scheme lets different wallets share a seed, and dedicated SegWit accounts mean only compatible wallets detect them.

    Quoted source text (1)

    With the usage of P2WPKH transactions it is necessary to have a common derivation scheme. It allows the user to use different HD wallets with the same masterseed and/or a single account seamlessly. Thus the user needs to create dedicated segregated witness accounts, which ensures that only wallets compatible with this BIP will detect the accounts and handle them appropriately.

    BIP 84, lines 20–23
  4. ↩ History BIP 44 (Palatinus, Rusnak; assigned 2014; requires BIPs 32 and 43), BIP 84 (Rusnak; 2017) and BIP 86 (Chow; 2021) are application-layer specifications, all recorded as Deployed.

    Quoted source text (5)

    Layer: Applications Title: Multi-Account Hierarchy for Deterministic Wallets Authors: Marek Palatinus <slush@satoshilabs.com> Pavol Rusnak <stick@satoshilabs.com>

    BIP 44, lines 3–12

    Status: Deployed Type: Specification Assigned: 2014-04-24 Requires: 32, 43

    BIP 44, lines 9–12

    Layer: Applications Title: Derivation scheme for P2WPKH based accounts Authors: Pavol Rusnak <stick@satoshilabs.com>

    BIP 84, lines 3–10

    Status: Deployed Type: Specification Assigned: 2017-12-28

    BIP 84, lines 8–10

    Layer: Applications Title: Key Derivation for Single Key P2TR Outputs Authors: Ava Chow <me@achow101.com> Status: Deployed Type: Specification Assigned: 2021-06-22

    BIP 86, lines 3–8
  5. ↩ a b c d e f Rule BIP 44 defines five levels below m: purpose', coin_type', account', change and address_index; an apostrophe marks hardened derivation.

    Quoted source text (1)

    We define the following 5 levels in BIP32 path: <pre> m / purpose' / coin_type' / account' / change / address_index </pre> Apostrophe in the path indicates that BIP32 hardened derivation is used.

    BIP 44, lines 31–37
  6. ↩ a b Rule Purpose is the constant 44' (0x8000002C), following BIP 43, and marks the subtree as following this specification; it is hardened.

    Quoted source text (1)

    Purpose is a constant set to 44' (or 0x8000002C) following the BIP43 recommendation. It indicates that the subtree of this node is used according to this specification. Hardened derivation is used at this level.

    BIP 44, lines 43–46
  7. ↩ a b Rule Coin type gives each coin its own hardened subtree, avoiding address reuse across coins; BIP 44 lists 0' for Bitcoin and 1' for Bitcoin testnet and points to SLIP-0044 for the full list.

    Quoted source text (4)

    This level creates a separate subtree for every cryptocoin, avoiding reusing addresses across cryptocoins and improving privacy issues.

    BIP 44, lines 54–55

    |0 |0x80000000 |Bitcoin |- |1 |0x80000001 |Bitcoin Testnet

    BIP 44, lines 144–150

    This BIP is not a central directory for the registered coin types, please visit SatoshiLabs that maintains the full list:

    BIP 44, lines 153–154

    [[https://github.com/satoshilabs/slips/blob/master/slip-0044.md|SLIP-0044 : Registered coin types for BIP-0044]]

    BIP 44, line 156
  8. ↩ a b c d Rule Accounts split the key space into independent user identities so coins are never mixed; they are numbered from 0, use hardened derivation, and software should not create an account while the previous one has no transaction history. BIP 44 likens them to bank accounts: one for donations, one for savings, one for common expenses.

    Quoted source text (3)

    This level splits the key space into independent user identities, so the wallet never mixes the coins across different accounts.

    BIP 44, lines 67–68

    Accounts are numbered from index 0 in sequentially increasing manner. This number is used as child index in BIP32 derivation. Hardened derivation is used at this level. Software should prevent a creation of an account if a previous account does not have a transaction history

    BIP 44, lines 75–81

    Users can use these accounts to organize the funds in the same fashion as bank accounts; for donation purposes (where all addresses are considered public), for saving purposes, for common expenses etc.

    BIP 44, lines 70–73
  9. ↩ a b c d e Rule Change is 0 for the external chain (addresses shown outside the wallet, for receiving) and 1 for the internal chain (change); it uses public derivation.

    Quoted source text (1)

    Constant 0 is used for external chain and constant 1 for internal chain (also known as change addresses). External chain is used for addresses that are meant to be visible outside of the wallet (e.g. for receiving payments). Internal chain is used for addresses which are not meant to be visible outside of the wallet and is used for return transaction change. Public derivation is used at this level.

    BIP 44, lines 88–94
  10. ↩ a b c d Rule Addresses are numbered from 0 along each chain, with public derivation.

    Quoted source text (1)

    Addresses are numbered from index 0 in sequentially increasing manner. This number is used as child index in BIP32 derivation. Public derivation is used at this level.

    BIP 44, lines 98–101
  11. ↩ a b c Rule After importing a seed, software discovers accounts in order, scanning each account's external chain and stopping at the first account with no transactions; it works on transaction history, not balances.

    Quoted source text (2)

    # derive the first account's node (index = 0) # derive the external chain node of this account # scan addresses of the external chain; respect the gap limit described below # if no transactions are found on the external chain, stop discovery # if there are some transactions, increase the account index and go to step 1

    BIP 44, lines 108–112

    Please note that the algorithm works with the transaction history, not account balances

    BIP 44, lines 118–120
  12. ↩ a b c History BIP 44 gives the address gap limit as 20 at the time of writing: after 20 unused addresses in a row, software stops scanning that chain. For account discovery, it scans only external chains, reasoning that internal chains receive only coins that come from the associated external chains, and wallet software should warn a user who tries to exceed the limit.

    Quoted source text (2)

    Address gap limit is currently set to 20. If the software hits 20 unused addresses in a row, it expects there are no used addresses beyond this point and stops searching the address chain. We scan just the external chains, because internal chains receive only coins that come from the associated external chains.

    BIP 44, lines 124–127

    Wallet software should warn when the user is trying to exceed the gap limit on an external chain by generating a new address.

    BIP 44, lines 129–130
  13. ↩ Editorial inference External-chain history determines which accounts BIP 44 discovers; recovering those accounts’ funds must also include their internal/change outputs. The recovery distinction is an inference from the account-discovery procedure and the internal chain’s stated use for returning change.

    Quoted source text (2)

    Constant 0 is used for external chain and constant 1 for internal chain (also known as change addresses). External chain is used for addresses that are meant to be visible outside of the wallet (e.g. for receiving payments). Internal chain is used for addresses which are not meant to be visible outside of the wallet and is used for return transaction change. Public derivation is used at this level.

    BIP 44, lines 88–94

    # derive the first account's node (index = 0) # derive the external chain node of this account # scan addresses of the external chain; respect the gap limit described below # if no transactions are found on the external chain, stop discovery # if there are some transactions, increase the account index and go to step 1

    BIP 44, lines 108–112
  14. ↩ Test vector BIP 44's examples table lists 16 paths: the first and second address of the external and change chains, for the first and second account, for Bitcoin and for Bitcoin testnet.

    Quoted source text (2)

    |Bitcoin |first |external |first |m / 44' / 0' / 0' / 0 / 0

    BIP 44, lines 170–174

    |Bitcoin Testnet |second |change |second |m / 44' / 1' / 1' / 1 / 1

    BIP 44, lines 260–264
  15. ↩ a b c d e f g Test vector This site's model, starting from BIP 84's and BIP 86's published mnemonic, reproduces every published root, account and address value in both BIPs' test vectors (zprv/zpub for BIP 84; xprv/xpub, internal key, output key, scriptPubKey and address for BIP 86); the build fails otherwise. Intermediate values (node keys, fingerprints, key hashes, tweaks) are derived by the same tested model and implied by the published leaves, but not published themselves. BIP 86 defines no alternate version bytes, and its vectors print as xprv/xpub.

    Quoted source text (2)

    mnemonic = abandon abandon abandon abandon abandon abandon abandon abandon abandon abandon abandon about rootpriv = zprvAWgYBBk7JR8Gjrh4UJQ2uJdG1r3WNRRfURiABBE3RvMXYSrRJL62XuezvGdPvG6GFBZduosCc1YP5wixPox7zhZLfiUm8aunE96BBa4Kei5

    BIP 84, lines 69–71

    mnemonic = abandon abandon abandon abandon abandon abandon abandon abandon abandon abandon abandon about rootpriv = xprv9s21ZrQH143K3GJpoapnV8SFfukcVBSfeCficPSGfubmSFDxo1kuHnLisriDvSnRRuL2Qrg5ggqHKNVpxR86QEC8w35uxmGoggxtQTPvfUu

    BIP 86, lines 86–87
  16. ↩ a b c d e Editorial inference BIP 44 itself names no script type or address format; BIPs 84 and 86 treat the purpose value as what signals the script type or serialization, and tie one to each purpose.

    Quoted source text (2)

    but only uses a different purpose value to indicate the different transaction serialization method.

    BIP 84, line 35

    To derive a public key from the root account, this BIP uses the same account-structure as defined in BIPs [[bip-0044.mediawiki|44]], [[bip-0049.mediawiki|49]], and [[bip-0084.mediawiki|84]], but with a different purpose value for the script type.

    BIP 86, lines 37–39
  17. ↩ a b c d Test vector From an account's extended public key alone, the model re-derives every published receiving and change address of that account, because the two levels below the account use public derivation. On its own such a key cannot spend.

    Quoted source text (3)

    Public derivation is used at this level.

    BIP 44, line 94

    xpub = zpub6rFR7y4Q2AijBEqTUquhVz398htDFrtymD9xYYfG1m4wAcvPhXNfE3EfH1r1ADqtfSdVCToUG868RvUUkgDKf31mGDtKsAYz2oz2AGutZYs

    BIP 84, line 75

    xpub = xpub6BgBgsespWvERF3LHQu6CnqdvfEvtMcQjYrcRzx53QJjSxarj2afYWcLteoGVky7D3UKDP9QyrLprQ3VCECoY49yfdDEHGCtMMj92pReUsQ

    BIP 86, line 92
  18. ↩ a b c Rule BIP 84 keeps BIP 44's account structure and changes only the purpose, 84', to indicate the P2WPKH serialization (the BIP 173 format), building addresses with BIP 141's P2WPKH encapsulation.

    Quoted source text (4)

    This BIP defines the derivation scheme for HD wallets using the P2WPKH ([[bip-0173.mediawiki|BIP 173]]) serialization format for segregated witness transactions.

    BIP 84, line 16

    this BIP uses the same account-structure as defined in [[bip-0044.mediawiki|BIP 44]] and [[bip-0049.mediawiki|BIP 49]], but only uses a different purpose value to indicate the different transaction serialization method.

    BIP 84, line 35

    For the <code>purpose</code>-path level it uses <code>84'</code>.

    BIP 84, line 41

    witness: <signature> <pubkey> scriptSig: (empty) scriptPubKey: 0 <20-byte-key-hash> (0x0014{20-byte-key-hash})

    BIP 84, lines 49–52
  19. ↩ a b c d Rule BIP 86 uses purpose 86' for keys used as the internal key of single-key P2TR outputs: the internal key is lift_x(derived key), tweaked with a hash of the key alone so that, as BIP 341 recommends, the output commits to an unspendable script path rather than none, in a version 1 output 0x5120{output key}.

    Quoted source text (5)

    This document suggests a derivation scheme for HD wallets whose keys are involved in single key P2TR ([[bip-0341.mediawiki|BIP 341]]) outputs as the Taproot internal key.

    BIP 86, lines 14–15

    For the <tt>purpose</tt>-path level it uses <tt>86'</tt>.

    BIP 86, line 45

    internal_key: lift_x(derived_key) 32_byte_output_key: internal_key + int(HashTapTweak(bytes(internal_key)))G

    BIP 86, lines 60–61

    scriptPubKey: 1 <32_byte_output_key> (0x5120{32_byte_output_key})

    BIP 86, lines 70–71

    If the spending conditions do not require a script path, the output key should commit to an unspendable script path instead of having no script path.

    BIP 86, lines 54–57
  20. ↩ a b Rule BIP 84's outputs are spent with an empty scriptSig and a witness of a signature and the public key; BIP 86's with an empty scriptSig and a witness holding only a signature.

    Quoted source text (2)

    witness: <signature> <pubkey> scriptSig: (empty)

    BIP 84, lines 49–51

    witness: <signature> scriptSig: (empty)

    BIP 86, lines 68–69
  21. ↩ a b Rule BIP 84 serializes extended keys with alternate version bytes: 0x04b24746 (zpub) and 0x04b2430c (zprv), with vpub/vprv on testnet.

    Quoted source text (1)

    Extended public keys use <code>0x04b24746</code> to produce a "zpub" prefix, and private keys use <code>0x04b2430c</code> to produce a "zprv" prefix. Testnet uses <code>0x045f1cf6</code> "vpub" and <code>0x045f18bc</code> "vprv."

    BIP 84, line 57
  22. ↩ Rule BIPs 84 and 86 are not backwards compatible by design: a wallet that does not implement them will not discover the accounts at all.

    Quoted source text (2)

    This BIP is not backwards compatible by design as described under [[#considerations|considerations]]. An incompatible wallet will not discover accounts at all and the user will notice that something is wrong.

    BIP 84, line 64

    This BIP is not backwards compatible by design. An incompatible wallet will not discover these accounts at all and the user will notice that something is wrong.

    BIP 86, lines 76–78
  23. ↩ a b Test vector The same mnemonic gives unrelated keys under purposes 44', 84' and 86' (and the schemes use different output types).

    Quoted source text (2)

    // Account 0, first receiving address = m/84'/0'/0'/0/0

    BIP 84, lines 77–80

    // Account 0, first receiving address = m/86'/0'/0'/0/0

    BIP 86, line 94
  24. ↩ Author’s rationale BIP 86's motivation: many wallets and hardware signers still use seed backups without derivation path or script information, so a fixed path makes single-key Taproot outputs likely to be recoverable; although there are now solutions that avoid fixed paths, it largely reuses the approach of BIPs 49 and 84 for ease of implementation.

    Quoted source text (1)

    it is useful to have a common derivation scheme so that HD wallets that only have a backup of the HD seed can be likely to recover single key Taproot outputs. Although there are now solutions which obviate the need for fixed derivation paths for specific script types, many software wallets and hardware signers still use seed backups which lack derivation path and script information. Thus we largely use the same approach used in BIPs [[bip-0049.mediawiki|49]] and [[bip-0084.mediawiki|84]] for ease of implementation.

    BIP 86, lines 23–28
  25. ↩ Author’s rationale BIP 86 notes that because it uses the same method as BIPs 44, 49 and 84 it should not be difficult to implement; BIP 84 points to SLIP-0132 for further registered version bytes.

    Quoted source text (2)

    However this BIP uses the same method used in BIPs 44, 49, and 84, so it should not be difficult to implement.

    BIP 86, lines 80–81

    Additional registered version bytes are listed in [[https://github.com/satoshilabs/slips/blob/master/slip-0132.md|SLIP-0132]].

    BIP 84, line 59