don't trickle messages for whitelisted nodes #5942

pull rubensayshi wants to merge 1 commits into bitcoin:master from blocktrail:dont-trickle-whitelisted changing 2 files +7 −2
  1. rubensayshi commented at 1:53 PM on March 24, 2015: contributor

    I think we don't have to protect our privacy to whitelisted nodes so there's no need to trickle message and we can always send the data.

    I also added a comment to the param, it was unclear to me that fSendTrickle=true meant sending out the previously trickled data instead of meaning that is should send data trickled ;)

  2. don't trickle for whitelisted nodes fc720207e0
  3. laanwj commented at 1:59 PM on March 24, 2015: member

    utACK - For any use of whitelisted node I can imagine, it'd either be advantageous or harmless to get all invs instantly instead of tricking.

  4. laanwj added the label P2P on Mar 24, 2015
  5. sipa commented at 2:09 PM on March 24, 2015: member

    utACK

  6. ghost commented at 10:04 PM on March 24, 2015: none

    utACK. The recent whitelist PRs, including #5288, beg the question of what's running those server farms.

  7. fanquake commented at 2:58 AM on March 26, 2015: member

    utACK

  8. laanwj merged this on Mar 26, 2015
  9. laanwj closed this on Mar 26, 2015

  10. laanwj referenced this in commit 6a1fbc4921 on Mar 26, 2015
  11. laanwj referenced this in commit 78f64ef0b2 on Mar 26, 2015
  12. reddink referenced this in commit 3d118da6e3 on May 27, 2020
  13. MarcoFalke locked this on Sep 8, 2021

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-22 03:15 UTC

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