To see the same Bitcoin activity in another wallet application, it must use the intended wallet, account and address format. The account's keypath helps select the right keys; the script type tells the application which Bitcoin addresses to construct from them.
Read Keypath and Script type in the intended account's BitBoxApp details. The account-details guide shows how to find the screen and select a format before copying information.
How account numbers appear in a keypath
Bitcoin account indexes start at zero. In the same wallet, these mainnet paths describe the first three Native SegWit accounts:
| Account position | Native SegWit account path |
|---|---|
| First | m/84'/0'/0' |
| Second | m/84'/0'/1' |
| Third | m/84'/0'/2' |
The last hardened value is the account index. The earlier 84' identifies Native SegWit and 0' identifies Bitcoin mainnet. Taproot uses 86' as its purpose, so the first Taproot account is m/86'/0'/0'. Renaming an account does not change these values; its displayed name is not a reliable way to infer its index.
One Bitcoin account in the BitBoxApp sidebar can contain both Native SegWit and Taproot. Its public information is specific to each format. Importing the Native SegWit information does not also include Taproot activity, and switching the displayed format does not move funds.
Use the path level the application requests
The account path shown in the BitBoxApp ends at the account index. A full address path continues with a receiving or change branch and an address index. For example, m/84'/0'/0'/0/0 reaches the first receiving address of the first mainnet Native SegWit account.
Use the displayed account path when the application asks for an account-level keypath. If it supports the complete public descriptor, that can carry the address-construction instructions together. The technical path reference explains the remaining levels.
The same path can exist in a different wallet
A keypath selects keys within a wallet; it does not identify the wallet itself. An optional passphrase changes the wallet derived from your recovery backup. Two such wallets can both use m/84'/0'/0' and produce different keys and addresses.
Use the external application's hardware-wallet connection flow with the intended wallet open on your BitBox. Never enter recovery words, private keys or an optional passphrase into an import form to resolve a mismatch.
If the addresses or balance differ
An unexpected or empty account can result from looking at a different wallet, account or format. It does not establish that funds have disappeared. Check:
- Wallet: the intended wallet is open, including the intended optional-passphrase wallet if you use one.
- Account and format: the external application's account path and script type match the configuration selected in the BitBoxApp.
- Import and synchronization: the application supports the information you supplied and has finished loading activity.
Selecting a different path does not move existing funds, but do not receive to an unexpected address or send a transaction to test an account you have not identified. If the difference remains unexplained, contact BitBox Support with the application names, versions and Bitcoin format. Never share recovery words, private keys, passwords, passphrases or wallet backups.