Default -whitelistforcerelay to off #15193

pull sdaftuar wants to merge 1 commits into bitcoin:master from sdaftuar:2019-01-forcerelayoff changing 3 files +10 −2
  1. sdaftuar commented at 9:55 pm on January 17, 2019: member

    No one seems to use this “feature”, and at any rate the behavior of relaying transactions when they violate local policy is error-prone, if we ever consider changing the ban behavior of our software from one version to the next.

    Defaulting this to off means that users who use -whitelist won’t be unexpectedly surprised by this interaction. If anyone is still relying on this feature, it can still be explicitly turned on.

  2. sdaftuar commented at 9:55 pm on January 17, 2019: member
    ping @gmaxwell
  3. fanquake added the label Validation on Jan 17, 2019
  4. DrahtBot commented at 11:31 pm on January 17, 2019: member

    The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.

    Conflicts

    Reviewers, this pull request conflicts with the following ones:

    • #15169 (WIP: Parallelize CheckInputs() in AcceptToMemoryPool() by sdaftuar)

    If you consider this pull request important, please also help to review the conflicting pull requests. Ideally, start with the one that should be merged first.

  5. fanquake renamed this:
    Default -whitelistforcelay to off
    Default -whitelistforcrelay to off
    on Jan 18, 2019
  6. fanquake renamed this:
    Default -whitelistforcrelay to off
    Default -whitelistforcerelay to off
    on Jan 18, 2019
  7. laanwj commented at 5:58 pm on January 18, 2019: member

    Needs release note.

    No one seems to use this “feature”

    From what I vaguely remember bitonic.nl (Dutch exchange) uses, or at least used this.

  8. fanquake added the label Needs release note on Jan 19, 2019
  9. gmaxwell commented at 5:55 pm on January 19, 2019: contributor
    Concept ACK. If we think there is still use we could add a FORCETX network message that is functionally identical to a TX message, but triggers the forced behaviour (and the user gets to live with the consequences) and is only permitted for WLed peers. I’m not aware of any continued dependency on this behaviour but we can check more.
  10. laanwj commented at 4:28 pm on January 20, 2019: member

    utACK

    Concept ACK. If we think there is still use we could add a FORCETX network message

    Well this PR doesn’t remove the functionality it only disables it by default, so IMO there is no requirement to provide an alternative here even if it is still used.

    Just need to be clear about it in the release notes (could even add a line to contact someone of us if they’re still using this functionality)

  11. Default -whitelistforcerelay to off a36d97d866
  12. sdaftuar force-pushed on Jan 22, 2019
  13. sdaftuar commented at 5:21 pm on January 22, 2019: member
    Updated with a release note.
  14. Joukehofman commented at 1:24 pm on January 23, 2019: none

    From what I vaguely remember bitonic.nl (Dutch exchange) uses, or at least used this.

    We use bitcoin nodes as relay, but since we don’t want them to relay transactions that violate the standard rules, we don’t use this feature as default.

    Edit: oh, just heard that we did for a while to mitigate an other problem that has since been resolved.

  15. Sjors commented at 3:13 pm on January 23, 2019: member
    utACK a36d97d
  16. promag commented at 3:34 pm on January 23, 2019: member
    utACK a36d97d, previous behavior is still possible.
  17. laanwj merged this on Jan 24, 2019
  18. laanwj closed this on Jan 24, 2019

  19. laanwj referenced this in commit 72bd4ab867 on Jan 24, 2019
  20. fanquake removed the label Needs release note on Mar 20, 2019
  21. harding referenced this in commit 305d1d7bad on Apr 25, 2019
  22. harding referenced this in commit e0bb279999 on Apr 25, 2019
  23. MarcoFalke referenced this in commit 08788ce170 on May 8, 2019
  24. sidhujag referenced this in commit d8de072a42 on May 10, 2019
  25. MarcoFalke referenced this in commit eb85ee62b3 on May 17, 2019
  26. HashUnlimited referenced this in commit 0910ddd2e4 on Aug 23, 2019
  27. Bushstar referenced this in commit 39052662a8 on Aug 24, 2019
  28. mdfkbtc referenced this in commit 2c799aee0a on Jan 23, 2020
  29. jasonbcox referenced this in commit 3c35162fc4 on Oct 19, 2020
  30. PastaPastaPasta referenced this in commit df57172410 on Jun 27, 2021
  31. PastaPastaPasta referenced this in commit 7947fe3e80 on Jun 28, 2021
  32. PastaPastaPasta referenced this in commit 31a68eef71 on Jun 29, 2021
  33. PastaPastaPasta referenced this in commit cfc3eccf42 on Jul 1, 2021
  34. PastaPastaPasta referenced this in commit 1c53e32966 on Jul 1, 2021
  35. PastaPastaPasta referenced this in commit 6b2141b0e3 on Jul 8, 2021
  36. PastaPastaPasta referenced this in commit 29d70e65a5 on Jul 19, 2021
  37. PastaPastaPasta referenced this in commit 657fea79a3 on Jul 20, 2021
  38. PastaPastaPasta referenced this in commit 8d362a5710 on Sep 11, 2021
  39. PastaPastaPasta referenced this in commit 6526309781 on Sep 11, 2021
  40. PastaPastaPasta referenced this in commit 27b75fb1d5 on Sep 12, 2021
  41. DrahtBot locked this on Dec 16, 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: 2024-07-05 19:13 UTC

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