From: jan@uos.de
Date: Tue, 14 Jun 2011 21:45:30 +0200
To: bitcoin-development@lists.sourceforge.net
Message-ID: <20110614194530.GA3152@dax.lan.local>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.20 (2009-06-14)
Subject: [Bitcoin-development] Question about dust spam rule
Precedence: list

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