Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.216.54 as permitted sender)
	client-ip=209.85.216.54; envelope-from=etotheipi@gmail.com;
	helo=mail-qa0-f54.google.com; 
Message-ID: <50BCC28A.4060503@gmail.com>
Date: Mon, 03 Dec 2012 10:17:30 -0500
From: Alan Reiner <etotheipi@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64;
	rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: bitcoin-development@lists.sourceforge.net
References: <80648682-E34A-455E-B34A-6BC24652C3EA@ceptacle.com>
	<CAPg+sBi25xP8R03y1VR=q4ZJaeT6FAuV=hXsq_7niSHycpnPuA@mail.gmail.com>
	<9CEDE4D4-3685-4F70-953E-15CC50A8AA3F@ceptacle.com>
	<CAAS2fgTL=s-vvGsubUu9ZBMidd0wzZdVPb6rEUg+eTMaiipRbA@mail.gmail.com>
In-Reply-To: <CAAS2fgTL=s-vvGsubUu9ZBMidd0wzZdVPb6rEUg+eTMaiipRbA@mail.gmail.com>
Content-Type: multipart/alternative;
	boundary="------------020109080207010107040606"
Subject: Re: [Bitcoin-development] Chain dust mitigation: Demurrage based
 Chain Vacuuming
Precedence: list

This is a multi-part message in MIME format.
--------------020109080207010107040606
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

On 12/03/2012 10:02 AM, Gregory Maxwell wrote:
> (1) Make client software aggressive about sweeping up dust inputs:
> "Any time a transaction is created that has change keep adding in
> extra inputs— smallest to largest— until an additional one would
> increase the cost of the transaction by 0.0001 BTC or more" — the only
> major complication is doing this without concurrently harming privacy
> which is why it's not done yet in the reference client.


FYI, Armory uses exactly this logic to try to clean up dust outputs in
the user's transactions.  However, there's enough conditions on it, that
I don't know how often it triggers.  Recommendations are welcome for how
to improve it.

Right now, if the transaction has less than 5 inputs, there exists dust
UTXOs from addresses already included in the transaction, and those
UTXOs are sufficiently small in priority, then the Armory will add them
to the input side and increase the change accordingly.  Looking it just
made me realize I lost the last condition of making sure the tx already
has a change output -- don't want to turn a free tx into a fee-needed tx
just to do this.  (reorganized the code
<https://github.com/etotheipi/BitcoinArmory/blob/master/armoryengine.py#L5279>
recently, and must have fell through the cracks).

Perhaps it could be improved by cleaning up dust from *any* address by
default (not just ones already included in the tx), with the option for
the user to disable that behavior.  After all, anonymity was never a
core feature of the network -- I think it makes sense that the logic
would reduce anonymity by default in exchange for a cleaner network,
with a clear option to "opt-out" of that logic if user cares.  I think
most users don't actually care...

-Alan

--------------020109080207010107040606
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">On 12/03/2012 10:02 AM, Gregory Maxwell
      wrote:<br>
    </div>
    <blockquote
cite="mid:CAAS2fgTL=s-vvGsubUu9ZBMidd0wzZdVPb6rEUg+eTMaiipRbA@mail.gmail.com"
      type="cite">(1) Make client software aggressive about sweeping up
      dust inputs:
      "Any time a transaction is created that has change keep adding in
      extra inputs— smallest to largest— until an additional one would
      increase the cost of the transaction by 0.0001 BTC or more" — the
      only major complication is doing this without concurrently harming
      privacy which is why it's not done yet in the reference client.
      <br>
    </blockquote>
    <br>
    <br>
    FYI, Armory uses exactly this logic to try to clean up dust outputs
    in the user's transactions.  However, there's enough conditions on
    it, that I don't know how often it triggers.  Recommendations are
    welcome for how to improve it.<br>
    <br>
    Right now, if the transaction has less than 5 inputs, there exists
    dust UTXOs from addresses already included in the transaction, and
    those UTXOs are sufficiently small in priority, then the Armory will
    add them to the input side and increase the change accordingly. 
    Looking it just made me realize I lost the last condition of making
    sure the tx already has a change output -- don't want to turn a free
    tx into a fee-needed tx just to do this.  (reorganized <a
href="https://github.com/etotheipi/BitcoinArmory/blob/master/armoryengine.py#L5279">the
      code</a> recently, and must have fell through the cracks).<br>
    <br>
    Perhaps it could be improved by cleaning up dust from <b>any</b>
    address by default (not just ones already included in the tx), with
    the option for the user to disable that behavior.  After all,
    anonymity was never a core feature of the network -- I think it
    makes sense that the logic would reduce anonymity by default in
    exchange for a cleaner network, with a clear option to "opt-out" of
    that logic if user cares.  I think most users don't actually care...<br>
    <br>
    -Alan<br>
  </body>
</html>

--------------020109080207010107040606--