As an authenticated user, I can generate a new blockchain wallet.

[T-Dnzt]

We had 3 wallet systems in the eWallet. They need to be adjusted to work for the eWallet. First, here's an overview:

1. Internal wallets. Owned by accounts and users. They are used for internal transactions (that are stored in the local ledger). These will be disabled with internal_enabled set to false for the eWallet.

2. Hot / Cold wallets. The logic here was to act as blockchain wallets owned by the eWallet to provide funds for token deployments and withdrawals. Cold wallets would not have their private keys stored in the system, but would be referenced in the system to keep track of the total funds owned by the eWallet owner (and easily rebalance between hot and cold).

3. HD Wallet system. This is used to generate deposit wallets for each internal wallet (to know where to credit the funds).

---

The HD Wallet system can be repurposed to act as the blockchain wallet system we need for the eWallet (all users and accounts can have multiple hot wallets managed by the eWallet (to send or receive funds)). All transactions going to the eWallet need to be submitted to the OMG Network and funds should be kept in each individual user's wallet. Private key should be computed from the extended private key, the derivation path and the position in the tree in order to sign and submit transactions to the OMG Network.