-
Notifications
You must be signed in to change notification settings - Fork 251
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add basic peer discovery mechanism. #16
Comments
Okay, a mechanism is already present - RequestPeers by timeout. Very dumb of me not to know that. |
Requested manual verification that this mechanism works for fullnodes in #12. |
Works as per @vldm assertion for fullnodes' mutual discovery. |
This was referenced Apr 28, 2017
stanislav-tkach
pushed a commit
to stanislav-tkach/exonum
that referenced
this issue
Apr 4, 2018
used newer version of Exonum client
stanislav-tkach
pushed a commit
to stanislav-tkach/exonum
that referenced
this issue
Apr 23, 2018
fix wrong db connection
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It's a proposition to add logic of broadcasting a newer
Connect
, sent by aPublicKey
, to all existing peers inexonum::node::NodeHandler.handle_connect(&mut self, message: Connect)
.Resolution will allow to easily add new fullnodes on blockchain network.
This has to correlate with #14 and have a limit on allowed frequency of handling each new
Connect
message from the samePublicKey
.https://*************/projects/22/tasks/1307.
The text was updated successfully, but these errors were encountered: