Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1RumbK-0000UZ-Vq for bitcoin-development@lists.sourceforge.net; Tue, 07 Feb 2012 15:04:58 +0000 X-ACL-Warn: Received: from zinan.dashjr.org ([173.242.112.54]) by sog-mx-2.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1RumbF-0002gj-42 for bitcoin-development@lists.sourceforge.net; Tue, 07 Feb 2012 15:04:58 +0000 Received: from ishibashi.localnet (fl-184-4-164-217.dhcp.embarqhsd.net [184.4.164.217]) (Authenticated sender: luke-jr) by zinan.dashjr.org (Postfix) with ESMTPSA id 6F3115607E7; Tue, 7 Feb 2012 15:04:47 +0000 (UTC) From: "Luke-Jr" To: Gavin Andresen Date: Tue, 7 Feb 2012 10:04:36 -0500 User-Agent: KMail/1.13.7 (Linux/3.2.2-gentoo; KDE/4.7.4; x86_64; ; ) References: <201202061054.26448.luke@dashjr.org> In-Reply-To: <201202061054.26448.luke@dashjr.org> X-PGP-Key-Fingerprint: CE5A D56A 36CC 69FA E7D2 3558 665F C11D D53E 9583 X-PGP-Key-ID: 665FC11DD53E9583 X-PGP-Keyserver: x-hkp://subkeys.pgp.net MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201202071004.37615.luke@dashjr.org> X-Spam-Score: -0.0 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay domain X-Headers-End: 1RumbF-0002gj-42 Cc: bitcoin-development@lists.sourceforge.net Subject: Re: [Bitcoin-development] Version 0.6 release candidate 1 plan 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, 07 Feb 2012 15:04:59 -0000 On Monday, February 06, 2012 10:54:25 AM Luke-Jr wrote: > > 769 : Make transactions with extra data in scriptSig non-standard > > If this affects relaying, it will significantly harm the ability to replace > the current spammy "green address" scheme with a sensible extra signature > system. On the miner end, it could significantly harm adoption of such a > system. FWIW, at least MtGox was OK with the plan to move to non-blockchain-spam 0-confirmation via an extra signature. Why do you ignore this possibility, and merge stuff that will break it? Do you have an alternative solution to the problem of green addresses spamming the blockchain? As I noted in the pull request, stripping extra data has no negative impact on normal transactions, and clients creating these can be written to expect the txnid to change (or simply not care what the txnid is).