-
Notifications
You must be signed in to change notification settings - Fork 14
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
Broadcast latencies in the Filecoin network #17
Comments
Thanks for raising this - important topic indeed! Just a quick note to say that we've already started planning on this. It has been on our plan to carry out this study for a while now, but got de-prioritised over other items. @cortze and @leobago will be looking into this in the coming month or so. We'll ping you when we get started. |
Thanks! In the meantime, we've procured some historical data from sentinel (https://github.com/protocol/pldw/issues/146) but we're still trying to figure out how good it is -- and, due to the passive collection and no trusted source timing, it comes with certain structural limitations. Looking forward to working with you! |
Thanks @jsoares, for some reason the link is not working for me. |
Any chance you already have a timeline/estimate for the study? Trying to make sure I align our roadmap 🙏 |
@cortze do you have an estimate of when you'd be starting this study? I guess not before the end of October, given the paper deadline you have, but would be great to schedule it straight after, WDYT? |
Apologies for coming late to the thread @jsoares , It will be my next priority after the submission of a paper that we are working on. So I will be able to start working on it after the IPFS Camp 🚀 |
Hi,
We're working on analyzing the security of Filecoin's Consensus mechanism, which significantly relies on timing assumptions.
To define a model that best captures the reality it would be extremely helpful to know the current latencies in Filecoin's mainnet. In particular, the latencies associated with broadcasting.
Any information would be valuable! (Mean latency per sender/receiver, complete distribution of latencies, 95th percentile, etc.)
cc @yiannisbot @sa8 @jsoares
The text was updated successfully, but these errors were encountered: