From: Jeff Garzik <jgarzik@exmulti•com>
To: Bitcoin Development <bitcoin-development@lists•sourceforge.net>
Subject: [Bitcoin-development] RFC: Updating dust output definition, and default fees
Date: Wed, 12 Dec 2012 16:37:28 -0500 [thread overview]
Message-ID: <CA+8xBpdDmxgW=fAN5QxrpVJS8xUxw_5-Zv4z+4qNcLpLQ8d9=w@mail.gmail.com> (raw)
URL: https://github.com/bitcoin/bitcoin/pull/2100
1) Create COIN_DUST constant, to represent the dust spam limit used.
2) Decrease COIN_DUST to 0.001 BTC
Rationale: With the increase in bitcoin value (US$13.67 as of this
writing), it seems reasonable to reduce the value level of which we
consider "dust spam."
3) Update TX miner and relay fee defaults to 0.001 / 0.0005 BTC respectively
Rationale: Reflects growth of dust spam in unspent transaction output dataset.
Review of impact:
a) Definition of COIN_DUST reduced from 0.01 to 0.001.
b) Miners who mine with this code will require a fee >= 0.001 to
include TX's with outputs <= COIN_DUST
c) Normal clients will require a fee >= 0.0005 to relay TX's with
outputs <= COIN_DUST
--
Jeff Garzik
exMULTI, Inc.
jgarzik@exmulti•com
reply other threads:[~2012-12-12 22:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CA+8xBpdDmxgW=fAN5QxrpVJS8xUxw_5-Zv4z+4qNcLpLQ8d9=w@mail.gmail.com' \
--to=jgarzik@exmulti$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox