Currently, we are relying on the eth node's account to sign the transaction when called by web3. This works fine with Ganache but would make on-boarding to testnet/mainnet hard. As we would need a eth node and need to import the account information into that node. First, this means we couldn't use cloud service such as Infura. Secondly, despite the fact that Parity supports account, to send the transaction with the account inside Parity, you would need to click approve tx from UI (or you'll need to sign the transaction).
As a result, to on-board to testnet, we would need this code change.
Currently, we are relying on the eth node's account to sign the transaction when called by web3. This works fine with Ganache but would make on-boarding to testnet/mainnet hard. As we would need a eth node and need to import the account information into that node. First, this means we couldn't use cloud service such as Infura. Secondly, despite the fact that Parity supports account, to send the transaction with the account inside Parity, you would need to click approve tx from UI (or you'll need to sign the transaction).
As a result, to on-board to testnet, we would need this code change.