Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
	helo=mx.sourceforge.net)
	by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <mh.in.england@gmail.com>) id 1TfXef-0008OX-4H
	for bitcoin-development@lists.sourceforge.net;
	Mon, 03 Dec 2012 15:09:57 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.219.47 as permitted sender)
	client-ip=209.85.219.47; envelope-from=mh.in.england@gmail.com;
	helo=mail-oa0-f47.google.com; 
Received: from mail-oa0-f47.google.com ([209.85.219.47])
	by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1TfXeZ-0003Xv-Nc
	for bitcoin-development@lists.sourceforge.net;
	Mon, 03 Dec 2012 15:09:57 +0000
Received: by mail-oa0-f47.google.com with SMTP id h1so2865233oag.34
	for <bitcoin-development@lists.sourceforge.net>;
	Mon, 03 Dec 2012 07:09:46 -0800 (PST)
MIME-Version: 1.0
Received: by 10.60.29.70 with SMTP id i6mr8747437oeh.38.1354547386431; Mon, 03
	Dec 2012 07:09:46 -0800 (PST)
Sender: mh.in.england@gmail.com
Received: by 10.76.128.139 with HTTP; Mon, 3 Dec 2012 07:09:46 -0800 (PST)
In-Reply-To: <CAAS2fgRQhEKnVqOFVohQtNswzrwopmPaz_2UaGjvMdOEQH5PRA@mail.gmail.com>
References: <80648682-E34A-455E-B34A-6BC24652C3EA@ceptacle.com>
	<CANEZrP1TCXh61oED=ytY2Es2coZZv0ZjBuQ5mTQjHL7t6r3E4Q@mail.gmail.com>
	<CAAS2fgRQhEKnVqOFVohQtNswzrwopmPaz_2UaGjvMdOEQH5PRA@mail.gmail.com>
Date: Mon, 3 Dec 2012 16:09:46 +0100
X-Google-Sender-Auth: mjKHbABs1n0evi9BGfh3PnpDeVs
Message-ID: <CANEZrP31F7mUDrJs8sCPTyOiaeoOrvQ3qtzG5pkMQef_8H22tw@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Gregory Maxwell <gmaxwell@gmail.com>
Content-Type: text/plain; charset=UTF-8
X-Spam-Score: -1.5 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
	sender-domain
	0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
	(mh.in.england[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	0.1 DKIM_SIGNED            Message has a DKIM or DK signature,
	not necessarily valid
	-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1TfXeZ-0003Xv-Nc
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>,
	Michael Gronager <gronager@ceptacle.com>
Subject: Re: [Bitcoin-development] Chain dust mitigation: Demurrage based
 Chain Vacuuming
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Mon, 03 Dec 2012 15:09:57 -0000

> It's part of their messaging system. Every losing play results in a
> new 1e-8 output being created.

Every losing play? That's ... not excellent.

Well, this why the payment protocol spec has a way for merchants to
reply to customers with text instead of outputs.