Topic: Dust threshold changed without any mention in 0.11.1 - page 4. (Read 6002 times)
The dust threshold is not hard coded. It is determined by the minrelaytxfee. The dust threshold changes with what is set as the minrelaytxfee, so you can set the minrelaytxfee in your own node to the original default of 0.00001 instead of the new default of 0.00005. That will change your dust threshold.
Thanks a lot bitcoin developers for screwing my application by changing the minimum output amount YET AGAIN. You should have at least mentioned it in the changelog or under the notable changes section:
https://bitcoin.org/en/release/v0.11.1
That's right, instead of 540 satoshis the bitcoin-core now won't allow outputs smaller than 2730 satoshis. This is starting to piss me off because every time you change it I must also change my program logic. If you have to do it then at least make it possible to request the current minimal dust threshold with an RPC.
Since this is such a bullshit change, I hereby spawn a parallel conversation: should developers not upgrade their bitcoin-core to 0.11.1 because of this? So that we could still make smaller output transactions? OR perhaps I should modify the source code of bitcoin-core to deliberately allow smaller amounts. It's up to miners anyway, so stop putting this crap into bitcoin-core if it can be so easily evaded.
https://bitcoin.org/en/release/v0.11.1
That's right, instead of 540 satoshis the bitcoin-core now won't allow outputs smaller than 2730 satoshis. This is starting to piss me off because every time you change it I must also change my program logic. If you have to do it then at least make it possible to request the current minimal dust threshold with an RPC.
Since this is such a bullshit change, I hereby spawn a parallel conversation: should developers not upgrade their bitcoin-core to 0.11.1 because of this? So that we could still make smaller output transactions? OR perhaps I should modify the source code of bitcoin-core to deliberately allow smaller amounts. It's up to miners anyway, so stop putting this crap into bitcoin-core if it can be so easily evaded.
Jump to: