diff options
author | Suhas Daftuar <sdaftuar@gmail.com> | 2022-01-26 18:29:56 -0500 |
---|---|---|
committer | Suhas Daftuar <sdaftuar@gmail.com> | 2022-02-22 11:34:05 -0500 |
commit | ef6dbe6863d92710fd2da7781e5b2aac87578751 (patch) | |
tree | c3e631f9c8a81987feba60d2f68394c6c0c2b672 /src/leveldb | |
parent | d0bf9bb6a539f151ec92725d20a2b6c22cb095a5 (diff) | |
download | bitcoin-ef6dbe6863d92710fd2da7781e5b2aac87578751.tar.xz |
Respond to getheaders if we have sufficient chainwork
Previously, we would check to see if we were in IBD and ignore getheaders
requests accordingly. However, the IBD criteria -- an optimization mostly
targeted at behavior when we have peers serving us many blocks we need to
download -- is difficult to reason about in edge-case scenarios, such as if the
network were to go a long time without any blocks found and nodes getting
restarted during that time.
To make things simpler to reason about, just use nMinimumChainWork as our
anti-DoS threshold; as long as our chain has that much work, it should be fine
to respond to a peer asking for our headers (and this should allow such a peer
to request blocks from us if needed).
Diffstat (limited to 'src/leveldb')
0 files changed, 0 insertions, 0 deletions