Axel Chalon

interested in working on this!

I imagine this could also be fixed upstream in the node, i.e. emit latest value (if available) on pubsub subscription

Happens with `parity_exportAccount` as well: ``` index.js:1446 parity_exportAccount(["0x57297efbd2ac9eaebc328309739975bdcb192185","mypassword"]): -32023: Could not export account. ```

`parity_killAccount` needs to be added as well

FWIW we're using [craco](https://github.com/sharegate/craco) with CRA2 in fether

I think it's a good idea so long as users know what foundation/kovan mean, otherwise they might get confused ("send foundation ether?" = send ether to the foundation?)

Implementation-wise, this will be possible from Parity 2.4.1 onwards using the parity_setChain RPC (the changing of the chain kills all rpc connections though, so we'll probably want to do a...

Our next Fether release will only be compatible with Parity >= 2.4.1 (because of https://github.com/paritytech/fether/pull/394 / https://github.com/paritytech/fether/pull/458), so parity_setChain will always be available on the LC

Good point. If you import an account from Parity Signer, then Fether doesn't ask for the private key, as it is managed by Parity Signer. If managing the account with...

(hacky workaround) You can open the Electron/Chromium Developer Tools (Ctrl+shift+I) inside Fether, navigate to the Console tab, paste the following line (replace address and name as desired) and hit enter:...