[bisq-network/bisq] Startup problem on slow/degraded networks (the "3/4" problem) (#2547)

agb19 notifications at github.com
Thu Apr 11 08:06:03 UTC 2019

Thanks for the clarification, glad I was able to help. 

Yes, I realize that a bad seed may delay the startup for a client that uses the long timeout setting. I was just worrying whether this setting could potentially have a **wider** impact on the entire network (like a DoS vector) that I'm not aware of.
If not, and the impact is limited to the specific client, then it might make sense to implement the more tolerant timeout setting as an opt-in command-line option, and leave the choice to the user. 
Most users will never need to use this option, however, for a few edge cases like mine, it would offer a choice between (a) the risk of startup delay due to hitting a bad seed node and (b) the certainty of no-op. Simply put, it would make a world of difference. 

Agreed, a better approach would be to eliminate the bandwidth peaks by protocol design, but that sounds like a lot of work :)

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20190411/cfe49ae6/attachment.html>

More information about the bisq-github mailing list