<p>I started implementing BIP32 for the reference client myself, but as there were more urgent matters to deal with, I have temporarily stopped working on it. I certainly plan to complete this, but I can't give any target date or version right now.</p>

<p>As far as I know from Alan Reiner (Armory's developer), he plans to switch to BIP32 as soon as the reference client implements them as well.</p>

CC BY-SA 3.0
2015-02-15T03:27:57.660Z
The list is growing: Mycelium, Greenaddress.it, BitGo.com and of course Trezor now support BIP32. ([Electrum 2.0](https://electrum.org/beta/) and [Multibit HD](https://beta.multibit.org/) are both in beta, but will also support BIP32 and Trezor)
Jonathan Cross
CC BY-SA 3.0
2015-09-17T16:43:19.803Z
Update: Electrum and MultibitHD are now using BIP32.
Jonathan Cross
CC BY-SA 3.0
2012-10-07T11:18:29.737Z
MultiBit is also planning to support them once other more pressing problems are out of the way.
Gary
CC BY-SA 3.0
2012-10-07T11:39:29.883Z
Great to hear, Gary. I'll try to get at least some test vectors in the specification soon, so implementations don't need to wait for each other to be sure to be compatible.
Pieter Wuille
CC BY-SA 3.0
2012-10-06T18:40:23.163Z
2012-10-06T18:40:23.163Z
Pieter Wuille
<p><a href="https://en.bitcoin.it/wiki/BIP_0032">BIP32</a> specifies hierarchical deterministic wallets, where a master seed fully determines a whole tree of keypairs that can be arbitrarily branched. It also introduces the notions of internal and external keypair chains that can be used independently to generate public or private keys.</p>

<p>Now I know that for example <a href="http://bitcoinarmory.com">Armory</a> uses deterministic wallets, but I cannot seem to find any implementation of the branching feature as described in BIP32. In particular, I want to generate a chain of linked addresses which are spendable using only one of the keys from my wallet as seed of a new branch (roughly the use case described in <a href="https://en.bitcoin.it/wiki/BIP_0032#Recurrant_business-to-business_transactions%3a_M.2Fi.2F0">Recurrent business-to-business transactions</a>).</p>

<p>Are there any other implementations of BIP 32 I am not aware of? Are there any plans to (fully) implement BIP 32 in Armory or any other client?</p>

CC BY-SA 3.0
2017-05-22T14:27:51.787Z
Absolutely none of the HD wallets are compatible with any of the others. Check the 'mnemonic compatible' tab in this spreadsheet: https://onedrive.live.com/view.aspx?resid=584F122BA17116EE!313&app=Excel
Chloe
<wallet><private-key><armory><bip32-hd-wallets>
What is the status of hierarchical deterministic wallets (BIP32)
Noah
# What is the status of hierarchical deterministic wallets (BIP32)

(Asked by: username_0 on 2012-10-06)

[BIP32](https://en.bitcoin.it/wiki/BIP_0032) specifies hierarchical deterministic wallets, where a master seed fully determines a whole tree of keypairs that can be arbitrarily branched. It also introduces the notions of internal and external keypair chains that can be used independently to generate public or private keys.

Now I know that for example [Armory](http://bitcoinarmory.com) uses deterministic wallets, but I cannot seem to find any implementation of the branching feature as described in BIP32. In particular, I want to generate a chain of linked addresses which are spendable using only one of the keys from my wallet as seed of a new branch (roughly the use case described in [Recurrent business-to-business transactions](https://en.bitcoin.it/wiki/BIP_0032#Recurrant_business-to-business_transactions%3a_M.2Fi.2F0)).

Are there any other implementations of BIP 32 I am not aware of? Are there any plans to (fully) implement BIP 32 in Armory or any other client?

**Tags:** wallet, private-key, armory, bip32-hd-wallets

> **Comments:**
> **username_1**: Absolutely none of the HD wallets are compatible with any of the others. Check the 'mnemonic compatible' tab in this spreadsheet: https://onedrive.live.com/view.aspx?resid=584F122BA17116EE!313&app=Excel  

---

## 1 answers

### Answer by username_2 on 2012-10-06. Score: 14 | Accepted answer

I started implementing BIP32 for the reference client myself, but as there were more urgent matters to deal with, I have temporarily stopped working on it. I certainly plan to complete this, but I can't give any target date or version right now.

As far as I know from Alan Reiner (Armory's developer), he plans to switch to BIP32 as soon as the reference client implements them as well.

> **Comments:**
> **username_4**: MultiBit is also planning to support them once other more pressing problems are out of the way.  
> **username_2**: Great to hear, username_4. I'll try to get at least some test vectors in the specification soon, so implementations don't need to wait for each other to be sure to be compatible.  
> **username_3**: The list is growing: Mycelium, Greenaddress.it, BitGo.com and of course Trezor now support BIP32. ([Electrum 2.0](https://electrum.org/beta/) and [Multibit HD](https://beta.multibit.org/) are both in beta, but will also support BIP32 and Trezor)  
> **username_3**: Update: Electrum and MultibitHD are now using BIP32.  

---

