-
Notifications
You must be signed in to change notification settings - Fork 447
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
[devel] Implement a crawling mechanism for our new bandwidth accounting mechanism #5676
Comments
devos50
changed the title
[devel] Create a crawler for our new bandwidth accounting mechanism
[devel] Implement a crawling mechanism for our new bandwidth accounting mechanism
Oct 24, 2020
9 tasks
drew2a
modified the milestones:
7.6.0 November: Stability, usability, performance,
Next-next release
Nov 4, 2020
@devos50 should we add this issue to |
Sure, we can do that 👍 |
devos50
modified the milestones:
Next-next release,
7.6.0 November: Stability, usability, performance
Nov 13, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Now that #5626 has been merged, we require a mechanism for peers to construct the global work graph. Specifically, each peer should slowly explore the (latest) transactions of other peers, which acts as input for our upcoming reputation mechanism. #5626 does not implement the required primitives for requesting transactions from other peers. We also need this to deploy a crawler that monitors network health.
The approach
The mechanism relies on simple pull-based gossip. Peers send out
TransactionQuery
message to other peers of which it would like to request the latest, pairwise transactions. Peers send back individualTransaction
messages. Queries do not have an associated request cache, to keep the mechanism simple. In fact, our mechanism can deal with missing messages or peers that go offline quickly after receiving a query.For now, we will query the immediate neighbours in a round-robin fashion. We can later extend our approach to also query the transactions of two-hop/three-hop peers.
The text was updated successfully, but these errors were encountered: