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

Closed
dbilitch opened this Issue May 24, 2014 · 5 comments

Comments

Projects
None yet
4 participants

Location: https://bitcoin.org/en/developer-guide#non-standard-transactions

If any of the transaction’s outputs spend less than a minimal value (currently 546 satoshis), the transaction must pay a minimum transaction fee (currently 10,000 satoshis).

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.

Contributor

gmaxwell commented May 24, 2014

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.

Contributor

harding commented May 24, 2014

@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:

The transaction must not include any outputs which receive fewer than the defined minimum number of satoshis, currently 546.

Thanks!

Contributor

gmaxwell commented May 25, 2014

@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.

Contributor

harding commented May 25, 2014

Misinformation fixed in f022b19. Thanks @dbilitch and @gmaxwell ! Closing this issue.

@harding harding closed this May 25, 2014

Contributor

saivann commented May 25, 2014

@harding Thanks!

@harding harding added the Dev Docs label Dec 13, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment