Parallel compact blocks bandwidth reduction or improvements #27740

issue instagibbs opened this issue on May 24, 2023
  1. instagibbs commented at 2:29 PM on May 24, 2023: member

    Opening a tracking issue post #25258

    To summarize a few potential strategies:

    1. It may be beneficial to reduce/eliminate concurrent block fetches from high-bandwidth outbound peers. That's at tension with the potential block relay speedup for non-listening peers, but at least non-listening peers aren't as vulnerable to sybil nodes.
    2. Could reduce number of concurrent to 2, instead of 3, for non-listening only, or both modes, to reduce worst-case overhead/funneling to listening nodes
    3. Could enable low-bandwidth compact outbound nodes instead by initiating a compact block fetch when a low-bandwidth outbound peer offers a header
    4. Could add timers/schedules to give every announce attempt a "fair chance" before issuing another getblocktxn without unduly slowing down block relay.

    A number of these would benefit greatly from a "blockrequests.cpp" style refactor to make this all more understandable.

  2. instagibbs cross-referenced this on May 24, 2023 from issue Parallel compact block download by ajtowns
  3. fanquake added the label P2P on May 24, 2023
  4. Sjors cross-referenced this on May 24, 2023 from issue Parallel compact block downloads, take 3 by instagibbs

github-metadata-mirror

This is a metadata mirror of the GitHub repository bitcoin/bitcoin. This site is not affiliated with GitHub. Content is generated from a GitHub metadata backup.
generated: 2026-05-19 06:52 UTC