save any private keys in a safe place

[SvenDowideit]

we have a create account function, but atm, the private key isn't saved - it used to be sent to the electron main process to be saved and passed back.

I hope we can talk to a wallet, and preferably client side, but for the electron app, that may not be possible yet.

• the best case would be https://github.com/solana-labs/wallet-adapter
  • but - they're currently only supporting testnet, devnet and mainnet-beta - https://github.com/solana-labs/wallet-adapter/blob/master/packages/core/base/src/types.ts
• there is https://docs.walletconnect.com/2.0/json-rpc/solana coming
• but, given zero-setup, and the restrictions on installing chrome extensions into an electron app, I'm guessing the 0.3.0 version will be to send the account info to the backend, and store them as we were doing before i broke it.
• and then later, our backend needs to be able to act as a wallet?
• however, that isn't going to work for the web-workbench, which I hope is a May/June thing.
• need a way to solana-keygen recover 'prompt://?key=0/0' -o file.json - ie, first use will be pre-wallet and live network accounts

Reading the code&examples, I get the strong feeling that we should not be doing account mutating transactions in the client directly - it should really use wallet-adapter, for which we should implement an electron ipc adapter, which then delegates the work - that way, the private keys would (initially) be handled only by the main app, and later by our out of GUI process daemon.

This then gives us a zero-steps ability to function, but giving the user the choice to use a real wallet.

[SvenDowideit]

I'm going to push the wallet stuff to 0.4.0

[SvenDowideit]

#129 starts towards this - by (just) sending and saving the private key to the electron main process.
Once wallet-adapter support is done, I'll work towards offloading all signing duties to the wallet.

[SvenDowideit]

this is functional, but will want later UX improvements