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
Desynced node does not sends block invs #8797
Comments
Anyway, your node is not downloading from your proxy node as your proxy node is still in Initial Block Download so won't serve blocks until it has caught up with the chain. There was an issue (#6971) raised for this, but it got closed in December 2015 for some bizarre reason. A solution would be to make make your local node whitelisted to your proxy node, then it will continue to serve blocks to it, however, since it's running Classic 1.1.1, I don't think this is currently a feature it can do. |
This is indeed a good case for using whitelisting.
Yes, if all nodes are tricked into thinking they are behind, bad things will happen. But you will have some trouble doing this. Here is the logic for This tricking would involve either:
In addition to this, all nodes would have to restart: after the IsInitialBlockDownload call returns I (and I think most others too) have lways been slightly uncomfortable with having many things depending on this heuristic, but these measures exist to prevent bandwidth waste (fetching transactions during IBD) as well as IIRC to prevent some fingerprinting attacks. |
Closing the issue as it is more of a question, and the "Desynced node does not sends block invs" behavior is intended. |
I have two nodes bound to loopback interface address 127.0.0.1, one node is configured to only connect to other one. Unfortunately it is unable to download any blocks from other node.
-debug=net
on both reveals a bunch of details.Client node debug.log (duplicate entries dropped):
Host (proxy) node debug.log:
Doesn't that means if all nodes are tricked into desynced or initial sync state bitcoin network might halt completely?
The text was updated successfully, but these errors were encountered: