-
Notifications
You must be signed in to change notification settings - Fork 284
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
Max Block Requests option #913
Comments
The limits are there for DOS and otherwise sanity limits. There's no reason for removing those limits, on the other hand nodes should NOT be sending over that limit. (Note: this is number of headers, not the actual blocks) What is your node version and what's the version of the peer (or ip if it's public) that is sending those blocks? It looks like you are using v6.x (Should work fine), but surprising that it starts complaining after 160k (which is checkpoint for v6) |
Okay, I think I found the issue. Currently you can use |
Thanks for the details, that was the main clue for the issue ! I will be releasing v7.0.1 with the fix. Alternatively, you can disable checkpoints as mentioned above and in the PR. |
They all are XD it kept connecting to multiple different nodes to get
headers, each one said it send too many
…On Fri, Dec 27, 2024, 4:00 AM Nodar Chkuaselidze ***@***.***> wrote:
The limits are there for DOS and otherwise sanity limits. There's no
reason for removing those limits, on the other hand nodes should NOT be
sending over that limit. (Note: this is number of headers, not the actual
blocks)
What is your node version and what's the version of the peer (or ip if
it's public) that is sending those blocks?
It looks like you are using v6.x (Should work fine), but surprising that
it starts complaining after 160k (which is checkpoint for v6)
—
Reply to this email directly, view it on GitHub
<#913 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BGA4U32PTLGEALKCTLMGYYT2HUQMPAVCNFSM6AAAAABUIAVWZ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRTGUZTAMJRGE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
It should be fixed now! You can upgrade to the latest version. (or disable checkpoints till 175k block) |
Whenever it reaches a height of 160,000 it will not accept a set of blocks from any peer for some odd reason. It keeps saying "peer advertised too many blocks" And I looked into it, and there's no option to increase this max block request limit for a given peer connection. I have attached an image about what i'm talking about.
The text was updated successfully, but these errors were encountered: