Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1UPcoW-0004Hk-Ej for bitcoin-development@lists.sourceforge.net; Tue, 09 Apr 2013 17:58:36 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of petertodd.org designates 62.13.148.108 as permitted sender) client-ip=62.13.148.108; envelope-from=pete@petertodd.org; helo=outmail148108.authsmtp.net; Received: from outmail148108.authsmtp.net ([62.13.148.108]) by sog-mx-4.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1UPcoU-0002dG-HN for bitcoin-development@lists.sourceforge.net; Tue, 09 Apr 2013 17:58:36 +0000 Received: from mail-c226.authsmtp.com (mail-c226.authsmtp.com [62.13.128.226]) by punt5.authsmtp.com (8.14.2/8.14.2/Kp) with ESMTP id r39HwOHa049229; Tue, 9 Apr 2013 18:58:24 +0100 (BST) Received: from savin (76-10-178-109.dsl.teksavvy.com [76.10.178.109]) (authenticated bits=128) by mail.authsmtp.com (8.14.2/8.14.2/) with ESMTP id r39HwJs0044602 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Tue, 9 Apr 2013 18:58:22 +0100 (BST) Date: Tue, 9 Apr 2013 13:58:19 -0400 From: Peter Todd To: Mike Hearn Message-ID: <20130409175819.GA31229@savin> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="envbJBWh7q8WU6mo" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-Server-Quench: 11ded91a-a13f-11e2-98a9-0025907ec6c5 X-AuthReport-Spam: If SPAM / abuse - report it at: http://www.authsmtp.com/abuse X-AuthRoute: OCd2Yg0TA1ZNQRgX IjsJECJaVQIpKltL GxAVKBZePFsRUQkR aQdMdgsUGUUGAgsB AmUbWlxeVVV7W2E7 bAxPbAVDY01GQQRq WVdMSlVNFUsqAhV5 QWRdUhl2cwNGejB4 bU5iEHFaCBEufEcs Xx9VFjsbZGY1an0W WBFRagNUcgZDfhgQ OVYsUT1vNG8XDQg5 AwQ0PjZ0MThBJSBS WgQAK04nCWENWzE7 RhYNVTkmAURNXD06 KnQA X-Authentic-SMTP: 61633532353630.1020:706 X-AuthFastPath: 0 (Was 255) X-AuthSMTP-Origin: 76.10.178.109/587 X-AuthVirus-Status: No virus detected - but ensure you scan with your own anti-virus system. 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 SPF_PASS SPF: sender matches SPF record X-Headers-End: 1UPcoU-0002dG-HN Cc: Bitcoin Development Subject: Re: [Bitcoin-development] On-going data spam X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Apr 2013 17:58:36 -0000 --envbJBWh7q8WU6mo Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Apr 09, 2013 at 04:53:47PM +0200, Mike Hearn wrote: > there's an obvious backwards compatibility problem there. It should > probably wait until the payment protocol work is done, so the major user = of > micropayments-as-messages can migrate off them. As I pointed out in my initial post on the issue, SatoshiDice is pretty much unaffected by the patch. They just have to deduct enough from incoming bets to make the "you lost" output economical and they're good to go. IIRC they already deduct fees on low-value bets anyway. On the other hand, the patch makes a clear statement that Bitcoin is not for microtransactions. If succesful it will gradually force a number of users, ad-based faucet sites and the like, to off-chain transactions or off Bitcoin entirely. The payment protocol has nothing to do with that. --=20 'peter'[:-1]@petertodd.org --envbJBWh7q8WU6mo Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAlFkVrsACgkQpEFN739thoyUkACeN/J6YesIctiP8IyZt0OSl7k4 6IkAn0/x8JpyvEuVij2TQSC1vPg3DaEg =0MEJ -----END PGP SIGNATURE----- --envbJBWh7q8WU6mo--