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 1S3tAj-0007K6-4H for bitcoin-development@lists.sourceforge.net; Sat, 03 Mar 2012 17:55:09 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 74.125.82.175 as permitted sender) client-ip=74.125.82.175; envelope-from=gavinandresen@gmail.com; helo=mail-we0-f175.google.com; Received: from mail-we0-f175.google.com ([74.125.82.175]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1S3tAi-0006jN-AI for bitcoin-development@lists.sourceforge.net; Sat, 03 Mar 2012 17:55:09 +0000 Received: by wera1 with SMTP id a1so2368648wer.34 for ; Sat, 03 Mar 2012 09:55:02 -0800 (PST) Received-SPF: pass (google.com: domain of gavinandresen@gmail.com designates 10.180.104.137 as permitted sender) client-ip=10.180.104.137; Authentication-Results: mr.google.com; spf=pass (google.com: domain of gavinandresen@gmail.com designates 10.180.104.137 as permitted sender) smtp.mail=gavinandresen@gmail.com; dkim=pass header.i=gavinandresen@gmail.com Received: from mr.google.com ([10.180.104.137]) by 10.180.104.137 with SMTP id ge9mr4987807wib.20.1330797302274 (num_hops = 1); Sat, 03 Mar 2012 09:55:02 -0800 (PST) MIME-Version: 1.0 Received: by 10.180.104.137 with SMTP id ge9mr3947925wib.20.1330797302172; Sat, 03 Mar 2012 09:55:02 -0800 (PST) Received: by 10.223.58.129 with HTTP; Sat, 3 Mar 2012 09:55:02 -0800 (PST) In-Reply-To: References: Date: Sat, 3 Mar 2012 12:55:02 -0500 Message-ID: From: Gavin Andresen To: Watson Ladd 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: 1S3tAi-0006jN-AI Cc: bitcoin-development@lists.sourceforge.net Subject: Re: [Bitcoin-development] Fwd: Proposal for a new opcode 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: Sat, 03 Mar 2012 17:55:09 -0000 On Fri, Mar 2, 2012 at 2:57 PM, Watson Ladd wrote: > Dear all, > I am proposing a new opcode for the purposes of anonymous > transactions. That's very exciting! I'm eager to read the paper for all of the details, and working out what else would need to be done besides a new opcode to enable strong anonymity (at the very least, I assume we'll need one or more new 'standard' transaction types that clients understand). -- -- Gavin Andresen