Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
Already on GitHub? Sign in to your account
typo/misinfo regarding dust outputs #424
Comments
|
Correct, the fee is irrelevant. People should be directed to pay that extra value you would have paid in fees into the output to get it over the threshold. This reduces the problem of people creating outputs which are unspendable or uneconomical to spend and forever increasing the size of the UTXO set. |
|
@dbilitch Thanks for your report! I think 546 is the correct minimal value currently. Please see: bitcoin/bitcoin@6a4c196 However, based on that same patch linked above, it looks like the minimum fee is 1,000 satoshis (not 10k, as we say). We use the 10,000 number in another part of the doc, which I'll update. @gmaxwell If you have a moment, can you please confirm this is a correct statement regarding standard transactions for default Bitcoin Core? Once you confirm it, I'll push an update:
Thanks! |
|
@harding Correct! It doesn't matter what the fee is, it could be a bazillion bitcoins. If any of the outputs are below the dust threshold nodes running unmodified bitcoin core code will not relay or mine the transaction. |
harding
closed this
May 25, 2014
|
@harding Thanks! |
dbilitch commentedMay 24, 2014
Location: https://bitcoin.org/en/developer-guide#non-standard-transactions
I believe that 546 should read 5460. Also, I think the reference client will drop the transaction (not relay it) regardless of fees included in the transaction.