BIP32 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 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).

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?

  • Absolutely none of the HD wallets are compatible with any of the others. Check the 'mnemonic compatible' tab in this spreadsheet: onedrive.live.com/…
    – Chloe
    May 22 '17 at 14:27

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.

  • 1
    MultiBit is also planning to support them once other more pressing problems are out of the way.
    – Gary Rowe
    Oct 7 '12 at 11:18
  • 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. Oct 7 '12 at 11:39
  • The list is growing: Mycelium, Greenaddress.it, BitGo.com and of course Trezor now support BIP32. (Electrum 2.0 and Multibit HD are both in beta, but will also support BIP32 and Trezor) Feb 15 '15 at 3:27
  • Update: Electrum and MultibitHD are now using BIP32. Sep 17 '15 at 16:43

The Electroid: Electrum for Android - Native Edition[1] project will have BIP 0032 support, at least with a basic implementation, but intending to mirror Electrum (the desktop version) with its version.

As a side-effect of the Android development, a Java library will be developed to at least minimally support the Android client, but with the intention to stay independent and not mix ANY client/UI details... that way it can be used outside of the client and be easier to test without worrying about UI details.

1: http://e4a-ne.blogspot.com

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.