Title: Questions about BIP32 path design Post by: weex on November 25, 2016, 07:48:38 PM Hey all,
We're looking at adding address generation and BIP32 support to Rein, a decentralized freelance project. The way identities work in Rein is that each user signs a kind of root document called their enrollment with an ECDSA (Bitcoin-style) key which we call their master address. As part of the enrollment, they sign that another key will be used to sign their day to day documents. The private key for this "delegate" address is stored in the client, whereas the master private key should be kept offline. The setup process for this is not terribly difficult but we're looking to simplify it. First, we want to generate the master key in the software from a BIP39 mnemonic, have the user type it back into the software to confirm that they've written it down, then store only a key for a BIP32 branch in the software. Goals:
I'm sure I'm missing something in this description so looking forward to any questions. Thanks, weex |