Closed zean00 closed 4 years ago
I've found the workaround, by including the node permission contract binary in the chain spec ( the contract should allow any connection by default) , hence the new node think that it allowed to connect to any nodes and try to connect to reserved peers or boot nodes. At least with this way, even though the new node isn't allowed to connect to anyone (based on the current state of the contract), it still try to connecting, and when it's finally allowed, it will sync up and update the contract state and I don't need to update the chain spec or restart the node
Seems you found solution
Before filing a new issue, please provide the following information.
If you think that your issue is an exploitable security vulnerability, please mail your bugreport to security@parity.io instead; your submission might be eligible for our Bug Bounty. You can find mode info on the reporting process in SECURITY.md
I've setup private network with aura consensus for 5 nodes, 3 nodes is validator nodes and 2 node is client node, I use this setup to test network permission contract
steps to reproduce
expected behavior
actual