Currently, the master seed creates as many addresses as desired. However, these multiple addresses are not being used wisely since, in most cases, only one is being used.
The whole point of an HD wallet, however, is to manage multiple addresses with a master seed, so you can split your funds across your master wallet and create specific uses for some of those addresses.
For aliases and specific uses, a special section in the UI must be developed (Christian).
note: HD_WALLET_DERIVE, which is the library we are currently using, doesn't allow the creation of a specific child address by index, which means that if we want to use the address with index 103890, then we will have to create the whole chain of addresses from 0 to 103890, so we can have access to that address. We can find a way to use this in a simpler manner, or we can switch to another library.
I think we should just populate the wallet with child index 1, with an option to populate the next address in the index. This will give users the ability to roll their addresses at their choosing.
Currently, the master seed creates as many addresses as desired. However, these multiple addresses are not being used wisely since, in most cases, only one is being used.
The whole point of an HD wallet, however, is to manage multiple addresses with a master seed, so you can split your funds across your master wallet and create specific uses for some of those addresses.
For aliases and specific uses, a special section in the UI must be developed (Christian).
note: HD_WALLET_DERIVE, which is the library we are currently using, doesn't allow the creation of a specific child address by index, which means that if we want to use the address with index 103890, then we will have to create the whole chain of addresses from 0 to 103890, so we can have access to that address. We can find a way to use this in a simpler manner, or we can switch to another library.