From: jan@uos.de
To: bitcoin-development@lists.sourceforge.net
Subject: [Bitcoin-development] Question about dust spam rule
Date: Tue, 14 Jun 2011 21:45:30 +0200 [thread overview]
Message-ID: <20110614194530.GA3152@dax.lan.local> (raw)
Hi there!
As can been seen from this code block
// To limit dust spam, require MIN_TX_FEE/MIN_RELAY_TX_FEE if any output is less than 0.01
if (nMinFee < nBaseFee)
BOOST_FOREACH(const CTxOut& txout, vout)
if (txout.nValue < CENT)
nMinFee = nBaseFee;
a fee is required as soon as any output is less than CENT.
I was wondering: would it be possible to loosen this rule to something
like "if _all_ outputs are less than CENT" or maybe "if more than 50% of
all outputs are less than CENT"?
The reason is, that I'm currently working on a project, where I would
like to take a small cut on transactions passing through (probably not
an usual requirement) and a lot of those small cuts would probably bump
into this rule.
Isn't this rule mainly meant to prevent lots of transactions with small
coins? So "all small coins" should work as well as "any small coins" or
am I missing something? (things like creating large transactions should
already be caught by other rules, right?)
Regards!
Jan
reply other threads:[~2011-06-14 19:45 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=20110614194530.GA3152@dax.lan.local \
--to=jan@uos.de \
--cc=bitcoin-development@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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