[bisq-network/bisq] Improve BSQ block requests (#3094)

Manfred Karrer notifications at github.com
Thu Aug 15 09:57:47 UTC 2019

Currently we request BSQ blocks from only one seed node. If it fails there is a rather long timeout until we try the next. In case a Bisq node does not receive a new block (after initial parsing is completed) there is currenttly no mechanism in place to request missing blocks and thr user has to restart. 
We should look into strategies how to get the initial block request more reliable and resiliant as well as to repeat requests in case we are not on the chaintip with our BSQ blocks.
Another open issue is that in case of a resync from genesis is triggered, the node only receives max. 6000 blocks as that is the limit a seednode provides (ddos protection). At the moment there is no mechanisma for repeating the call so that the missing blocks are requested again and to be able to get to the chain tip. A restart is atm required to get the rest of the blocks. We should add a request from another seednode for the missing blocks once the parsing of the first 6000 blocks is done.

The parsing must not be interrupted, so all those need some smart handling of parallel received data and handling of yhe data deltas.

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/20190815/60c33b57/attachment.html>

More information about the bisq-github mailing list