I am running Parity in a Virtual Machine. I have copied VM and trying to run both Parity's parallel in both Virtual Machines. Since their enode is same on both VMs, I cannot run both Parity in parallel. I guess their connection into same node collide.

[Q] I want to update on going Parity's enode. How could I do that, do I need to clean all Parity's memory?

Is there any way to run Parity nodes having same enode-id in parallel?

Please note that: I observe that Parity nodes having same enode-id connected with different account cannot connect into same Ethereum enode node.

1 Answer 1


Changing or removing the network key changes the enode address:


You could increment the value by one or generate a new one or remove it and parity will take care of that.

  • Is there a way to manually change the key in order to generate a specific enode ID? I accidentally deleted the network key and need to restore my enode ID.
    – stone.212
    Jan 9, 2018 at 4:21
  • I think that's what the --identity flag does, try to play around with this. But you can also set the network key value to anything you like.
    – q9f
    Jan 16, 2018 at 8:55
  • I will look at --identity but are you suggesting that the network key is the same as the enode ID? Because I do not think that is correct. (I think the enode ID is maybe the public key?)
    – stone.212
    Jan 16, 2018 at 9:58
  • Exactly, the enode is somehow public, while the network key is private.
    – q9f
    Jan 16, 2018 at 10:12
  • How could I do same approach for geth node? Please see: ethereum.stackexchange.com/q/43356/4575 @Rando
    – alper
    Mar 20, 2018 at 17:47

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

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