1

In Parity, as explained in this tutorial for setting up a PoA, there are three methods for creating Ethereum accounts: Via RPC calls, via the UI, and via parity account new.

The UI obviously seems to wrapping the RPC calls, so we can discard the UI for the sake of this discussion. I've observed the following:

  • The RPC calls will deterministically create an ICAP address. I'm specifically running parity_newAccountFromPhrase and I seed this with a random phrase from parity parity_generateSecretPhrase.

  • The command line option parity account new does not seem to give me an ICAP address or the possibility of getting a recovery phrase.

So what's the rationale behind this? Is there a way for me to get a non-ICAP compatible address from the RPC calls? Is there a way for me to get a recovery phrase from the command line option?

I'm specifically asking with regard to private PoA chains.

EDIT: ICAP, not ICAN.

  • Why do you use Parity? A lot of people who were using it now lost all of their money. – Nulik Nov 21 '17 at 18:57
0

Only accounts generated from phrase result in an ICAP-compatible address, namely parity_newAccountFromPhrase.

Is there a way for me to get a non-ICAP compatible address from the RPC calls?

All other methods (CLI, RPC) do not yield such addresses. For RPC that is:

  • personal_newAccount
  • parity_newAccountFromSecret
  • parity_newAccountFromWallet

Is there a way for me to get a recovery phrase from the command line option?

No, but there is a rust crate: https://github.com/paritytech/wordlist

  • Ok! So the CLI parity account new and the RPC parity_newAccount are functionally equivalent? – Alistair Jones Nov 22 '17 at 4:16
  • personal_newAccount, but yes. – Waqar Lim Nov 23 '17 at 13:56

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.