Skip to content
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

Many "peer sent us block transactions for a block we weren't expecting" errors #9031

Closed
rebroad opened this issue Oct 27, 2016 · 3 comments
Closed
Labels

Comments

@rebroad
Copy link
Contributor

rebroad commented Oct 27, 2016

Currently when a peer received blocks from another peer before a full compact block is received, we get this error when the compact block blocktxns finally arrive. This is because when the block is received MarkBlockAsReceived() is called which removes the mapping of the block being in flight, thereby triggering this error when the blocktxns do arrive, which we requested.

@TheBlueMatt
Copy link
Contributor

No peer should be providing an unsolicited block, so the error isnt in compact blocks, its on the peer that gave you the full blocks' side.

@rebroad
Copy link
Contributor Author

rebroad commented Oct 29, 2016

@TheBlueMatt No peer should ever do DoS - does this mean we shouldn't have DoS protection code?

Anyway, I think you are incorrect, as, as far as I know, the relay networks provide unsolicited blocks, as do miners.

@gmaxwell
Copy link
Contributor

No node should be sending an unsolicited block, it is a horrific waste of bandwidth. We should be banning on that, unless whitelisted. (for the relay network client, that is a local connection -- not remote peers.)

@laanwj laanwj closed this as completed Nov 21, 2016
@bitcoin bitcoin locked as resolved and limited conversation to collaborators Sep 8, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants