In bitcoin core, how to avoid the dust exception?

by Allen_Tsang   Last Updated August 10, 2018 01:27 AM

When I try to broadcast a transaction, my bitcoin core throw a "dust" exception.

amount: 0.00029
fee: 0.00001
bitcoin core version: v0.16.0

The same transaction can success in testnet, but fail in mainnet.

When I send 0.0003 BTC to an account in my bitcoin core, it can success. So, I think send 0.00029 BTC out of the node is still possible.

I set the fee to such a small number to lower the transaction cost, since there will be many transactions like this one. If this fee will not work, then what is the lowest fee?

I try to set the option "discardfee", but didn't make anything change.

Any advice is helpful, thanks in advance.

Tags : dust


Answers 1


The current dust limit fee rate is 3 satoshis/byte. If, at 3 satoshis per byte, an output would cost more in fees to spend that it has in value, then that output is considered dust. If you are sending to non-segwit addresses, this limit is 3 sat/byte * 148 bytes = 444 sats. If you are sending to P2SH-segwit addresses (the default address type in Bitcoin Core), then the fee limit is 3 sat/byte * 91 bytes = 273 sat. If you are sending to bech32 addresses, then the fee limit is 3 sat/byte * 68 bytes = 204 sat.

You can lower your dust limit by setting -dustrelayfee to something lower than 0.00003 BTC/kB (equivalent to 3 sat/byte). However I do not recommend that you change this as even though your node will accept transactions with outputs that are otherwise dust, other nodes will not and your transactions will not be relayed.

Furthermore, you should not set your transaction fee rate to be less than 0.00001 BTC/kB (equivalent to 1 sat/byte) as this is the default minimum relay fee and transactions that have a fee rate less than this will not be relayed. Just because your node accepts a transaction does not mean that other people's nodes will.

Andrew Chow
Andrew Chow
August 10, 2018 01:37 AM

Related Questions


Updated July 05, 2017 07:27 AM

Updated March 10, 2019 09:27 AM

Updated November 30, 2018 06:27 AM

Updated April 15, 2019 15:27 PM

Updated July 25, 2017 16:27 PM