What account details mean in the BitBoxApp

Table of Contents

Account details overview Account format Account name Keypath Script type Root fingerprint Coin Extended public key Descriptor QR codes Verify on device FAQ Do I need to understand all account details to use the BitBoxApp? Can the root fingerprint be used to steal funds? Can the extended public key be used to spend funds? Why is the descriptor useful? Should I copy the extended public key or the descriptor? Why should I verify account details on the BitBox02?

The account details window in the BitBoxApp shows technical information about a specific account in your wallet.

This information can help you understand how the account is structured, which address format it uses, and how it can be imported into compatible external wallet software.

Most users do not need these details for everyday wallet use. They are mainly useful when you want to set up a watch-only wallet, check account compatibility, export account information, or verify technical account data directly on your BitBox02.

Account details overview

Each account shown in the left sidebar of the BitBoxApp has its own account details.

For example, one Bitcoin account can have separate account details for different formats, such as Native SegWit and Taproot. Each format has its own technical information, including its own extended public key and descriptor.

The account details window can show the following information:

Item	What it means	Why it matters
Account format	The address format currently displayed, such as Native SegWit or Taproot.	Helps you identify which Bitcoin account type you are viewing.
Account name	The name you assigned to the account in the BitBoxApp.	Helps you distinguish between different accounts.
Keypath	The derivation path used for this account.	Helps compatible wallets find the correct account structure.
Script type	The Bitcoin script type used by the account.	Determines how addresses are created and interpreted.
Root fingerprint	A short identifier of the wallet’s master key.	Helps identify which wallet the account belongs to.
Coin	The cryptocurrency or network used by the account.	Confirms which asset the account belongs to.
Extended public key	Public account information that can derive addresses for this account.	Useful for watch-only wallets, but privacy-sensitive.
Descriptor	A standardized description of the account structure.	Improves compatibility when importing account information into other wallets.
QR codes	QR codes for the extended public key and descriptor.	Make it easier to scan account information into compatible tools.

Account format

The account format shows which address format is currently displayed for the selected account.

For Bitcoin accounts, common formats include:

Native SegWit: Uses Bech32 addresses that usually start with bc1q. The related script type is commonly shown as P2WPKH or wpkh.
Taproot: Uses Bech32m addresses that usually start with bc1p. The related script type is commonly shown as P2TR or tr.
Wrapped SegWit: Uses addresses that usually start with 3. The related script type is commonly shown as P2SH-P2WPKH or sh(wpkh).

Native SegWit is the standard format for most Bitcoin users. Taproot is a newer account format that can be useful depending on the wallet or service you want to use. Wrapped SegWit exists mainly for compatibility with older wallets or services.

Account format
The account format affects which addresses are generated for the account. When importing account information into another wallet, the external wallet needs to understand the correct format.

Account name

The account name is the name you assigned to the account in the BitBoxApp.

This name is only used to help you identify the account more easily inside the BitBoxApp. It does not affect your wallet backup, receiving addresses, transactions, or funds.

Keypath

The keypath shows the derivation path used for the account.

A derivation path tells wallet software how to derive a specific account from your wallet backup. This is how one wallet backup can generate multiple accounts and addresses in a structured way.

The keypath depends on the account format and the account number. For example:

Native SegWit account 1: m/84'/0'/0'
Native SegWit account 2: m/84'/0'/1'
Native SegWit account 3: m/84'/0'/2'
Taproot account 1: m/86'/0'/0'

In these examples:

84' is commonly used for Native SegWit accounts.
86' is commonly used for Taproot accounts.
0' after that refers to Bitcoin mainnet.
The last number identifies the account index.

This means that different account formats and different accounts can have different keypaths.

Technical note
The keypath is mostly relevant for advanced users and external wallet compatibility. In normal BitBoxApp usage, you usually do not need to change or manually enter it.

Script type

The script type describes how Bitcoin addresses are created and interpreted for the selected account.

For example, a Native SegWit account uses a different script type than a Taproot account. This is why different account formats produce different address types.

Common examples are:

Native SegWit: P2WPKH or wpkh
Taproot: P2TR or tr
Wrapped SegWit: P2SH-P2WPKH or sh(wpkh)

The script type is important when another wallet or service needs to understand how to derive and monitor the correct addresses.

Root fingerprint

The root fingerprint is a short identifier derived from your wallet’s master key.

It helps wallet software recognize which wallet an account belongs to. This can be useful when working with external wallet software or when comparing account information.

The root fingerprint is not a private key and cannot be used to spend funds.

Coin

The coin field shows which cryptocurrency or network the account belongs to.

For example, a Bitcoin account shows Bitcoin (BTC). This helps confirm that you are viewing account details for the correct asset.

Extended public key

The extended public key is public account information that can be used to derive addresses for a specific account.

It can be useful when setting up a watch-only wallet or when importing account information into compatible external wallet software.

An extended public key does not contain private keys and cannot be used to spend your funds. However, it can reveal addresses and transaction activity for the related account.

Privacy note
Treat your extended public key as privacy-sensitive information. Anyone with access to it may be able to monitor addresses and transactions that belong to the related account.

For a more detailed explanation, see:
[Learn more about extended public keys in the BitBoxApp]([Placeholder: extended public key article URL])

Descriptor

A descriptor is a standardized description of the account structure.

Compared to an extended public key alone, a descriptor contains additional information, such as the script type and derivation path. This can make imports into compatible wallet software more reliable.

Descriptors are especially useful for Taproot accounts, because importing only the extended public key may cause compatibility issues in some external wallets.

Compatibility note
When another wallet supports descriptors, use the descriptor instead of copying only the extended public key. The descriptor contains more complete account information.

For a more detailed explanation, see:
[Learn more about wallet descriptors in the BitBoxApp]([Placeholder: descriptor article URL])

QR codes

The account details window can display QR codes for the extended public key and the descriptor.

These QR codes make it easier to transfer account information into compatible tools without manually copying long text strings.

Only scan these QR codes into wallet software or tools you trust.

Verify on device

The Verify on device button lets you verify the extended public key directly on your BitBox02.

This is useful because your BitBox02 has a trusted screen. Verifying the extended public key on the device helps you confirm that the information shown in the BitBoxApp matches the information provided by your hardware wallet.

At the moment, verification on the BitBox02 is available for the extended public key only. Other account details, such as the descriptor, cannot currently be verified directly on the device.

Verification reminder
If you use an extended public key for an important setup, verify it on your BitBox02 whenever possible.

FAQ

Do I need to understand all account details to use the BitBoxApp?

No. Most users do not need to understand every technical field for everyday wallet use. Account details are mainly useful for advanced setups, external wallet compatibility, and verification.

Can the root fingerprint be used to steal funds?

No. The root fingerprint is only a short identifier. It does not contain private keys and cannot be used to spend funds.

Can the extended public key be used to spend funds?

No. The extended public key cannot be used to spend funds. However, it can reveal account activity, so you should treat it as privacy-sensitive information.

Why is the descriptor useful?

The descriptor includes more complete account information than the extended public key alone. This can help compatible external wallets import the account with the correct format, keypath, and script type.

Should I copy the extended public key or the descriptor?

Use the descriptor when the external wallet supports it. Use the extended public key only when the external wallet specifically asks for it or does not support descriptors.

Why should I verify account details on the BitBox02?

Verifying the extended public key on your BitBox02 helps confirm that the extended public key shown in the BitBoxApp matches the information provided by your hardware wallet.