In the context of deploying a dApp testnet using Docker, I'm trying to run an openethereum container that unlocks specific accounts. I could not find much documentation about this, but I basically following this process: https://ico.readthedocs.io/en/latest/chain.html#parity-with-kovan-testnet. This means that I created accounts a priori using the openethereum cli, then I backed up their keys into a volume that mounts into: io.parity.ethereum/keys/kovan. Then, I use the unlock argument to give the account addresses and paths to password files. This works but it strikes me as too complicated to be right. Is there a way to just give openethereum a menmonic and account derivation paths to unlock accounts that weren't created in advance?
In the context of deploying a dApp testnet using Docker, I'm trying to run an openethereum container that unlocks specific accounts. I could not find much documentation about this, but I basically following this process: https://ico.readthedocs.io/en/latest/chain.html#parity-with-kovan-testnet. This means that I created accounts a priori using the openethereum cli, then I backed up their keys into a volume that mounts into:
io.parity.ethereum/keys/kovan
. Then, I use the unlock argument to give the account addresses and paths to password files. This works but it strikes me as too complicated to be right. Is there a way to just give openethereum a menmonic and account derivation paths to unlock accounts that weren't created in advance?