I don't think this still makes sense:
We could just remove the recommendation, or base it on some constant in the bitcoin source, but it should not be hardcoded in a message.
Qt: Hardcoded transaction fee recommendation in message #2576
issue laanwj opened this issue on April 26, 2013-
laanwj commented at 11:55 AM on April 26, 2013: member
- laanwj cross-referenced this on Apr 26, 2013 from issue Treat dust outputs as non-standard, un-hardcode TX_FEE constants by gavinandresen
-
gavinandresen commented at 3:41 PM on April 26, 2013: contributor
Good idea. I vote for just removing it for now. The longer-term plan is to teach the code how to figure out a reasonable fee, based on behavior of transactions going in/out of the memory pool.
-
laanwj commented at 8:59 AM on April 27, 2013: member
Indeed, I saw @TheBlueMatt s proposal on figuring out the fee from the mempool, and thought it was pretty neat.
But yeah, going to remove the recommendation for now. It's much too large and we can't manually change it every release based on the current trading price.
- laanwj referenced this in commit dffb535ead on Apr 27, 2013
- laanwj cross-referenced this on Apr 27, 2013 from issue qt: remove fee recommendation in settings by laanwj
- laanwj closed this on Apr 27, 2013
- kyledrake referenced this in commit 341535082d on Jul 25, 2013
- laudney referenced this in commit 84c5be3844 on Mar 19, 2014
- bitcoin locked this on Sep 8, 2021
