Hierarchical deterministic wallets (BIP32) are the standard way to handle wallets in eCash.
This allows users to take a seed derived from a mnemonic and derive the private key of a given path.
Depends on D17612.
Details
Details
Diff Detail
Diff Detail
- Repository
- rABC Bitcoin ABC
- Branch
- ecash-lib-hdwallet
- Lint
Lint Passed - Unit
No Test Coverage - Build Status
Buildable 32268 Build 64026: Build Diff ecash-agora-tests · ecash-agora-integration-tests · ecash-lib-tests · cashtab-tests · ecash-lib-integration-tests Build 64025: arc lint + arc unit
Event Timeline
Comment Actions
Similar question as with D17612
There's a good deal of empirical history with https://github.com/bitcoinjs/bip32/
Could you give a few sentences about the approach used here and how it differs from the legacy lib?
| modules/ecash-lib/src/io/bytes.ts | ||
|---|---|---|
| 12 ↗ | (On Diff #52451) | |
Comment Actions
This one is more of a 1-to-1 translation of bip32, compared to bip39 which I did a lot of improvements for.
The main differences are:
- Cleaner code (no usage of variables like I, IL, IR, __Q and __D)
- Re-uses our Ecc instance, so that no dependency like tiny-secp256k1 has to be installed, just a normal Ecc instance. This is significant because this way you only have to get one library to work (ecash-lib), which is tightly integrated and not two or more.