Skip to main content
BIP-84, native segwit. Addresses begin bc1q.

​
Address type

Legacy and nested segwit are not used at all. Neither is Taproot, anywhere in Trustodian — wallets are P2WPKH and vaults are P2WSH. There is no second script type to look for.
The script type matters as much as the path. The same key produces a different address as legacy (1...), as nested segwit (3...) and as native segwit (bc1q...). Restoring with the wrong script type gives you a valid, empty wallet at the same derivation path.If your restored wallet shows addresses that do not begin bc1q, the script type is wrong.
A Bitcoin wallet you imported into Trustodian by private key may be any script type, because it was never derived here. It is also not recoverable from the phrase at all. See What the phrase does not cover.

​
The index

{index} is the address leaf, so every Trustodian Bitcoin wallet you have is an address under the single account m/84'/0'/0'. One restore finds all of them. A wallet that scans forward along the receive branch shows every one of your Bitcoin wallets, with their balances, in one place. This is unlike Solana and Cardano, where each wallet is a separate account.
If a wallet stops scanning before it reaches your highest index, raise its gap limit. Most wallets stop after 20 consecutive unused addresses, which only matters if your wallets are spread thinly across a wide index range.

​
How to recover it

Sparrow

Also the only tool here that imports a vault descriptor

Electrum

Needs its BIP-39 option turned on first

​
Verifying

Match the first receive address against your first Trustodian Bitcoin wallet before trusting any balance. If it does not match, the script type is the first thing to check, then the passphrase. See Troubleshooting.

​
Vaults

A Bitcoin vault is not covered by any of the above. Its configuration is not on the chain, only a hash of it is, so the vault needs its output descriptor from your Recovery Kit. See Bitcoin vaults.
Last modified on September 17, 2026