Set DEFAULT_LIMITFREERELAY = 0 kB/minute #9179

1. 
   MarcoFalke commented at 11:32 PM on November 17, 2016: member

   No description provided.

2. Set DEFAULT_LIMITFREERELAY = 0 kB/minute fa7cc5a508
3. MarcoFalke added this to the milestone 0.14.0 on Nov 17, 2016
4. MarcoFalke added the label TX fees and policy on Nov 17, 2016
5. 
   Mirobit commented at 3:39 AM on November 18, 2016: contributor

   ACK My nodes get flooded with these 2 year old spam transactions after every block: 27cdfec78b2e0e97762a8486d5440bfc02dac3c2cd278ac803b81062c7212332

6. 
   sdaftuar commented at 11:20 PM on November 19, 2016: member

   Concept ACK.

   Is it worth warning users of the parameter interaction if they are setting -relaypriority=0?

7. 
   MarcoFalke commented at 4:00 PM on November 20, 2016: member

   Is it worth warning users of the parameter interaction if they are setting -relaypriority=0?

   Suggestions welcome, but I am not sure if this is required. I understand the relaypriority setting is orthogonal to the limitfreerelay setting. If the user set -relaypriority=0 today, they'd still see their transaction rate limited (with 15 kB/min). So when they depend on free relay, they most likely adjusted their -limitfreerelay setting anyway.

8. in doc/release-notes.md:None in fa7cc5a508

     59 |    converted to the new format which is not readable by prior versions of the
     60 |    software.
     61 |  
     62 | +- The concept of "priority" transactions is planned to be removed in the next
     63 | +  major version. To prepare for this, the default for the rate limit of priority
     64 | +  transactions (`-limitfreerelay`) has been set to `0` kB/minute.
   

   ---

   ---

   

   luke-jr commented at 6:46 PM on November 20, 2016:

   NACK. There is no plan to remove priority transactions, only "smart priority" attempting to use it. Don't confuse priority with gratis txns... they are different.

9. 
   sipa commented at 7:00 PM on November 20, 2016: member

   @luke-jr Sorry, but we're planning to remove priority. It is no longer useful to maintain.

10. 
    laanwj commented at 2:27 PM on November 21, 2016: member

    utACK https://github.com/bitcoin/bitcoin/pull/9179/commits/fa7cc5a508921182a4ebf1f9ed296664e5044007

11. laanwj merged this on Nov 21, 2016
12. laanwj closed this on Nov 21, 2016

    ---

13. laanwj referenced this in commit b9a87b459d on Nov 21, 2016
14. MarcoFalke deleted the branch on Nov 21, 2016
15. 
    luke-jr commented at 6:39 AM on December 2, 2016: member

    @sipa It remains useful and used. NACK removing it from mining.

16. codablock referenced this in commit 726dd1f8a3 on Jan 15, 2018
17. andvgal referenced this in commit 77b4f64fe1 on Jan 6, 2019
18. CryptoCentric referenced this in commit 6121b5e5f7 on Feb 24, 2019
19. MarcoFalke locked this on Sep 8, 2021

Milestone
0.14.0