Categories
- 17.3K All Categories
- 9.5K Mining
- 574 Pool Discussion
- 378 Promotional
- 1.4K General Project Discussion (non-technical)
- 485 Education
- 811 Protocol and Client discussion
- 170 web3-js
- 29 Whisper
- 16 Swarm
- 3 RLP
- 303 IoT & Hardware
- 1.2K Smart Contracts and Dapps
- 28 Serpent
- 359 Solidity
- 664 Projects
- 1.2K Reference clients code and builds
- 249 Eth & AlethZero- Cpp Implementation
- 471 Geth - Go Implementation
- 242 Mist
- 15 Node.js Implementation
- 36 Python Implementation
- 49 Mix
- 36 Other Implementations
- 170 Meetups
- 40 Other Events
- 226 Jobs & Skills
- 281 Press and Articles
- 75 Audio/Video
- 296 Ether Sale
- 1.2K Other Languages
- 96 Chinese
- 255 German
- 33 Italian
- 111 French
- 3 Hebrew
- 42 Japanese
- 75 Portugese
- 46 Romanian
- 185 Russian
- 231 Spanish
- 47 Turkish
- 125 Watercooler
Plans to implement hierachical deterministic (HD) wallet functionality?
chaser
Member Posts: 2 ✭
There are immense benefits of being able to generate addresses deterministically and to back up the wallet seed.
I read that there's even an existing code base which has BIP44 (deterministic address generation) and BIP32 (mnemonic seed) tailored to Ethereum: https://github.com/trapp/ethereum-bip44
Are there plans to establish such standards for Ethereum and implement it in the core clients? Why or why not? And if so, where should one look in the future?
I read that there's even an existing code base which has BIP44 (deterministic address generation) and BIP32 (mnemonic seed) tailored to Ethereum: https://github.com/trapp/ethereum-bip44
Are there plans to establish such standards for Ethereum and implement it in the core clients? Why or why not? And if so, where should one look in the future?