Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1RungX-0000am-Rw for bitcoin-development@lists.sourceforge.net; Tue, 07 Feb 2012 16:14:25 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 74.125.82.53 as permitted sender) client-ip=74.125.82.53; envelope-from=gavinandresen@gmail.com; helo=mail-ww0-f53.google.com; Received: from mail-ww0-f53.google.com ([74.125.82.53]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1RungS-000220-Fb for bitcoin-development@lists.sourceforge.net; Tue, 07 Feb 2012 16:14:25 +0000 Received: by wgbdr12 with SMTP id dr12so7087797wgb.10 for ; Tue, 07 Feb 2012 08:14:14 -0800 (PST) MIME-Version: 1.0 Received: by 10.180.95.1 with SMTP id dg1mr34971919wib.21.1328631254341; Tue, 07 Feb 2012 08:14:14 -0800 (PST) Received: by 10.223.112.199 with HTTP; Tue, 7 Feb 2012 08:14:14 -0800 (PST) In-Reply-To: <201202071004.37615.luke@dashjr.org> References: <201202061054.26448.luke@dashjr.org> <201202071004.37615.luke@dashjr.org> Date: Tue, 7 Feb 2012 11:14:14 -0500 Message-ID: From: Gavin Andresen To: Luke-Jr Content-Type: text/plain; charset=ISO-8859-1 X-Spam-Score: -1.6 (-) 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 (gavinandresen[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 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: 1RungS-000220-Fb 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 16:14:25 -0000 > Do you have an alternative solution to the > problem of green addresses spamming the blockchain? Sure, here's one: Green address provider give a REST-ful API, that provides the following functionality: + Give transaction ID and credentials, request that the transaction be declared "green" (sender's wallet site/software would do this) + Give transaction ID, return boolean "has this transaction been deeclared green?" As I said, I think any design that relies on clients recognizing two variations of a transaction is a very bad idea. -- -- Gavin Andresen