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.
--identityflag does, try to play around with this. But you can also set the network key value to anything you like. – q9f Jan 16 '18 at 08:55gethnode? Please see: https://ethereum.stackexchange.com/q/43356/4575 @Rando – alper Mar 20 '18 at 17:47