Account details help you identify the account you have selected in the BitBoxApp and understand how it is configured. For Bitcoin, the screen also provides public account information that compatible software can use to follow its addresses and transactions.

You might need these details when another wallet asks for a keypath, an extended public key or a descriptor. You do not need to understand every field to send or receive funds in the BitBoxApp. To find the screen, follow How to view account details in the BitBoxApp.

What the account details window shows

The fields depend on the cryptocurrency and, for Bitcoin, the address format you are viewing. The examples below cover Bitcoin, Ethereum and tokens. Use this overview to find a field's meaning and purpose.

Account name and Coin or Token

Account name is the label you use to recognize the account. Renaming it does not change its keys or addresses, create another account or move funds.

Coin identifies the cryptocurrency, such as Bitcoin (BTC) or Ethereum (ETH). For a token account, Token shows its name and symbol instead. Token details have no separate Account name field, so the selected account in the sidebar provides that context.

Keypath: where the account comes from

The Keypath, also called a derivation path, describes how the account's keys are derived within your wallet. Think of it as directions to a particular account: another wallet application may ask for this path so it can open the same account.

For example, m/84'/0'/0' describes the first Native SegWit Bitcoin account on mainnet:

The apostrophe marks a hardened derivation step, which cannot be performed from an extended public key alone. The BitBoxApp handles derivation automatically; normal use does not require you to enter or change a path.

Paths can end at different levels. A Bitcoin account path stops at the account; an Ethereum path such as m/44'/60'/0'/0/0 continues to an individual address. Use the value displayed for your account rather than copying an example. A path is neither a key nor a wallet backup, and the same path in a different wallet produces different keys and addresses. The derivation-path reference explains the levels across cryptocurrencies.

Script type and Bitcoin address format

Script type identifies the Bitcoin address format whose details you are viewing. It helps you match the account configuration when using another wallet:

One Bitcoin account in the sidebar can contain both formats. Each has its own keypath and public account information. Switching the displayed format shows that other configuration; it does not convert or move existing funds. For example, a Native SegWit export lets another wallet follow the Native SegWit activity, but does not also include that account's Taproot activity.

Ethereum and token details do not have this Bitcoin Script type field or the Native SegWit/Taproot selector.

Root fingerprint: a short wallet identifier

The Root fingerprint helps you recognize a wallet when comparing account configurations. Accounts derived from the same wallet share it, even when their cryptocurrencies, account numbers or Bitcoin address formats differ.

It is an eight-character hexadecimal value derived from the wallet's master public key. Because it is short, different wallets can have the same fingerprint. A match is a useful reference, but cannot conclusively prove that you opened or restored the intended wallet. The fingerprint cannot authorize spending or restore a wallet.

Extended public key: follow many addresses

A Bitcoin Extended public key lets compatible software derive public keys and, with the correct address-format settings, the account's receiving and change addresses. This makes it useful for a watch-only wallet or accounting tool. Anyone you share it with can potentially monitor those addresses and their activity, including future activity.

The key covers the selected account and format, rather than every account in your wallet. It contains no private keys, cannot authorize spending and cannot replace your wallet backup. A value beginning with xpub or zpub is an extended-public-key encoding, not a receiving address. See What is a Bitcoin extended public key (xpub)? for its scope, privacy implications and encoding differences.

Descriptor: the key and the instructions for using it

A Bitcoin Descriptor combines a public key with instructions for constructing the intended addresses. It adds information that a key alone may leave to the receiving software, such as the script type, where the key came from and which address branches to follow. These public exports can reveal addresses and activity, including future activity, without giving spending access. They are not wallet backups.

Use the complete descriptor when another wallet supports it. Taking only the key inside it removes part of those instructions. For example, wpkh(...) tells the software to construct Native SegWit addresses, while tr(...) identifies Taproot. The descriptor explanation breaks down the components and their compatibility limits.

For Taproot, the BitBoxApp provides a descriptor and its QR code, with no separate Extended public key field or Bitcoin Verify on device button. The status line may refer to a P2TR extended public key, but the value offered for copying is the complete descriptor.

QR codes and account privacy

A QR code contains the value named beside it: the extended public key or descriptor. Scanning it transfers that information to compatible software. These account-export codes are not payment requests.

Balance and contract address for Ethereum and tokens

Ethereum and token details show the keypath, root fingerprint and Coin or Token, without the Bitcoin public-key exports above. They can also show Balance: the available amount reported by the BitBoxApp, in that coin or token's own unit.

For supported tokens, Contract address identifies the smart contract defining the token. It is useful when comparing tokens with similar names or checking which contract a service refers to. The same name or symbol alone does not establish token identity; compare the contract on the intended network. The link beside the field opens the contract in a block explorer.

What the verification buttons check

For Bitcoin formats with a separate extended-public-key field, Verify on device lets you compare that key with the value shown on your BitBox. It does not verify the complete descriptor or every account field. If the keys differ, do not use the export until the discrepancy is resolved.

Ethereum and token details offer Verify address securely, which opens receiving-address verification. It does not verify the token contract address. Follow the account-details guide for the Bitcoin comparison and copying steps.