Wallet descriptors are a standardized way to describe how a Bitcoin account is structured and how its addresses are derived.
In the BitBoxApp, descriptors are shown in the account details window together with the extended public key. They are mainly useful when you want to export account information, set up a watch-only wallet, or import account details into compatible external wallet software.
Compared to copying only the extended public key, a descriptor includes more complete account information. This can help other wallets understand the correct account format, derivation path, and address type.
Compatibility note
When another wallet supports descriptors, use the descriptor instead of copying only the extended public key. A descriptor includes additional information such as the script type and derivation path.
What is a wallet descriptor?
A wallet descriptor describes how a wallet or account derives and recognizes Bitcoin addresses.
A descriptor can include information such as:
- the extended public key
- the script type
- the derivation path
- the account structure
- checksum information
This makes descriptors more explicit than extended public keys alone.
For example, an extended public key can tell another wallet which public keys can be derived. A descriptor can also tell the wallet how those keys should be used to create the correct addresses.
For a more technical explanation, see this external guide:
Why descriptors are useful
Descriptors are especially helpful when importing Bitcoin account information into other wallet software.
They reduce the risk that another wallet imports the account with the wrong address format or script type. This is important because different Bitcoin account formats, such as Native SegWit and Taproot, use different address structures.
Descriptors are useful when you want to:
- set up a watch-only wallet
- monitor an account from another device
- import account information into compatible external wallet software
- avoid compatibility issues with Taproot accounts
- export account information in a standardized format
Descriptor or extended public key?
The BitBoxApp shows both the extended public key and the descriptor because some external wallets support descriptors, while others still ask for the extended public key.
| Option | What it contains | When to use it |
|---|---|---|
| Extended public key | Public account information that can derive addresses for one account | Use it when the external wallet specifically asks for an xpub, ypub, zpub, or similar extended public key |
| Descriptor | More complete account information, including details such as script type and derivation path | Use it when the external wallet supports wallet descriptors |
Privacy note
Both descriptors and extended public keys can reveal addresses and transaction activity for the related account. They cannot be used to spend your funds, but you should still treat them as privacy-sensitive information.
Example of a wallet descriptor
A descriptor shown in the BitBoxApp can look like this:
wpkh([56f89c3e/84'/0'/4']xpub6DS8bfs9fkUkkU6jann1aP9RPeoob46oiGZTgB6Ny67e5H2zz7FwKbGQ327JyGwv3YCLfgYor3FQCsUo5jk5s8T5J72ezGWD2BD8cW71n89/<0;1>/*)#c48k0cht
This may look technical at first, but each part has a specific meaning.
| Descriptor part | Meaning |
|---|---|
wpkh(...) |
Defines the address type. wpkh means Native SegWit, also known as P2WPKH. These addresses usually start with bc1q.
|
56f89c3e |
The root fingerprint. This helps identify which wallet or seed the account belongs to. |
84' |
The purpose field. 84' refers to Native SegWit according to BIP-84.
|
0' |
The coin type. 0' refers to Bitcoin mainnet.
|
4' |
The account index. Because account indexes start at 0, account 4' means this is the 5th Bitcoin account.
|
xpub... |
The extended public key for this account. It can derive public addresses for this account, but it cannot spend funds. |
<0;1> |
The address branch. 0 is used for receiving addresses and 1 is used for change addresses.
|
* |
The address index placeholder. It means that many addresses can be derived from this account. |
#c48k0cht |
The checksum. It helps compatible wallet software detect copying or formatting mistakes. |
In simple terms, this descriptor says:
This is a Native SegWit Bitcoin account, using the 5th Bitcoin account path, with an extended public key that can derive both receiving and change addresses.
Descriptor checksum
The checksum at the end of a descriptor helps compatible wallet software verify that the descriptor was copied correctly. If the descriptor is changed or copied incorrectly, the checksum may no longer match.
Why descriptors matter for Taproot accounts
Descriptors are especially useful for Taproot accounts.
Taproot accounts use a different address format than Native SegWit accounts. If you import only the raw extended public key into another wallet, the external wallet may not have enough information to determine the correct account structure.
This can lead to compatibility issues or to the wallet showing a different set of addresses than expected.
Taproot compatibility
For Taproot accounts, use the descriptor whenever the external wallet supports it. This helps the external wallet identify the correct account format and derivation path.
How to find your wallet descriptor in the BitBoxApp
- Open the BitBoxApp.
- Connect and unlock the BitBox02 that contains the wallet with the Bitcoin account you want to view.
Remember wallet
If Remember wallet is enabled for this specific wallet, the BitBoxApp can display account details without the BitBox02 being connected. If the wallet was not remembered, connect and unlock the BitBox02 that contains the wallet first.
- In the left sidebar, select the Bitcoin account for which you want to view the descriptor.
- Click Account info.
- Click View account details.
- Find the Descriptor section in the account details window.
- Copy the descriptor or scan the descriptor QR code.
Native SegWit, Taproot, Wrapped SegWit and Legacy
Bitcoin wallets can use different account and address formats. These formats define how addresses are created and how other wallet software recognizes the account.
In the BitBoxApp, each Bitcoin account format has its own account details, extended public key, and descriptor. This is important because the same wallet can have different Bitcoin account formats, such as Native SegWit and Taproot, but each format uses a different derivation path and address structure.
| Format | Address prefix | Standard | Typical derivation path | Status |
|---|---|---|---|---|
xpub |
1 |
Legacy (BIP44) | m/44'/0'/0' |
Old |
ypub |
3 |
Wrapped SegWit (BIP49) | m/49'/0'/0' |
Transitional |
zpub |
bc1q |
Native SegWit (BIP84) | m/84'/0'/0' |
Recommended |
| Taproot descriptor | bc1p |
Taproot (BIP86) | m/86'/0'/0' |
Newest |
Native SegWit is the recommended standard for most Bitcoin users. These addresses start with bc1q and are widely supported.
Taproot is the newest Bitcoin address format. These addresses start with bc1p. Taproot can be useful when supported by the wallet or service you want to use, but compatibility may still vary depending on the external wallet software.
Wrapped SegWit is an older transitional format. It was introduced to make SegWit compatible with services that did not yet support Native SegWit. Existing Wrapped SegWit accounts continue to work, but Native SegWit is usually preferred today.
Legacy is the oldest Bitcoin address format. It is still part of Bitcoin history and may still appear in older wallets, but it is generally not recommended for new accounts.
Outdated formats
Wrapped SegWit and Legacy accounts are no longer natively supported in the BitBoxApp for regular receiving and sending.
FAQ
Can a descriptor be used to spend my funds?
No. A descriptor does not contain private keys and cannot be used to spend funds. However, it can reveal addresses and transaction activity for the related account.
Is a descriptor more secure than an extended public key?
A descriptor is not “more secure” in the sense of protecting funds. It is more complete and can improve compatibility because it includes additional account information, such as script type and derivation path.
Should I use the descriptor or the extended public key?
Use the descriptor whenever the external wallet supports it. Use the extended public key only if the external wallet specifically asks for it.
Why does the BitBoxApp show a QR code for the descriptor?
The QR code makes it easier to transfer the descriptor into compatible wallet software without manually copying a long text string.
Why are descriptors useful for Taproot?
Taproot accounts require the correct account structure to be interpreted properly. A descriptor helps compatible wallets identify the correct format and derivation path.
Can I share my descriptor publicly?
No. You should not share your descriptor publicly. It cannot be used to spend funds, but it can reveal account activity and affect your privacy.