<p>Trezor follows (and helped design) <a href="https://github.com/bitcoin/bips/blob/master/bip-0044.mediawiki" rel="nofollow noreferrer">BIP44</a>.</p>

<p>BIP44 details how a single mnemonic may be used to create individual keychains for different blockchains, and how multiple accounts may work within those keychains.</p>

<p>This is not a foolproof system - if you deviate from the expectations of BIP 44 (such as using addresses beyond the 20 address gap limit) automated recovery software will not be able to locate all of the used addresses - This makes it somewhat unfit for commercial uses, since most companies and exchanges need to give out addresses without assuming they will be used sequentially.</p>

<p>For individual wallets, this is a safe assumption, and one that Trezor makes.</p>

CC BY-SA 4.0
2019-06-21T12:14:36.897Z
2019-06-21T12:14:36.897Z
Raghav Sood
<p>I understand that the Trezor is a HD wallet, meaning private-public keys are generated through a deterministic, hierarchical expansion of the root seed. However, when I am in a process of recovering my wallet with a seed, how does it figure out which private-public key pairs map to which accounts on which blockchain? Is it just some sort of brute-force expand and check (see of Bitcoin blockchain has the following address or no) algorithm?</p>

<wallet-recovery><bip32-hd-wallets><trezor>
How does Trezor recover all public keys from different blockchains?
spacemonkey
# How does Trezor recover all public keys from different blockchains?

(Asked by: username_0 on 2019-06-21)

I understand that the Trezor is a HD wallet, meaning private-public keys are generated through a deterministic, hierarchical expansion of the root seed. However, when I am in a process of recovering my wallet with a seed, how does it figure out which private-public key pairs map to which accounts on which blockchain? Is it just some sort of brute-force expand and check (see of Bitcoin blockchain has the following address or no) algorithm?

**Tags:** wallet-recovery, bip32-hd-wallets, trezor


---

## 1 answers

### Answer by username_1 on 2019-06-21. Score: 0 | Accepted answer

Trezor follows (and helped design) [BIP44](https://github.com/bitcoin/bips/blob/master/bip-0044.mediawiki).

BIP44 details how a single mnemonic may be used to create individual keychains for different blockchains, and how multiple accounts may work within those keychains.

This is not a foolproof system - if you deviate from the expectations of BIP 44 (such as using addresses beyond the 20 address gap limit) automated recovery software will not be able to locate all of the used addresses - This makes it somewhat unfit for commercial uses, since most companies and exchanges need to give out addresses without assuming they will be used sequentially.

For individual wallets, this is a safe assumption, and one that Trezor makes.


---

