Client node is not added to the `reserved_peers` list

openethereum / parity-deploy

Parity deployment script.

Apache License 2.0

81 stars 52 forks source link

Client node is not added to the `reserved_peers` list #39

Closed 0x7CFE closed 6 years ago

0x7CFE commented 7 years ago

When client node is created using --enable-client looks like it is not added to the reserved_peers list. If --reserved-only option is passed it results in nodes not seeing each other.

I don't quite understand why client node is not set as reserved. Is there some reasoning for it?

ddorgan commented 6 years ago

@0x7CFE yes as the client only needs to connect to the authorities rather than needing the authorities connect to it. Agreed? Can this be closed?