idea for syncnode selection #2822

issue Diapolo opened this issue on July 12, 2013
  1. Diapolo commented at 11:25 AM on July 12, 2013: none

    @sipa Just an idea, why not always switch to a node that announces more blocks than the current syncnode, if we are up-to-date with the current syncnode?

  2. laanwj commented at 10:22 AM on October 21, 2013: member

    Nodes can easily lie about the number of blocks, so this would be an easy way to introduce a DDoS attack. One could just pretend to have lots of blocks and everyone will switch to you and hold up the network.

  3. sipa commented at 10:55 AM on October 21, 2013: member

    Syncnode is going away anyway in headersfirst - we download from all peers that claim to have the block we're looking for (well, syncnode still exists, but it's just used to start the headers-sync process, which is really fast).

  4. Diapolo closed this on Nov 3, 2013

  5. DrahtBot locked this on Sep 8, 2021
Contributors

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-04-21 18:16 UTC

This site is hosted by @0xB10C
More mirrored repositories can be found on mirror.b10c.me