From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1W2ndj-0000A3-BN for bitcoin-development@lists.sourceforge.net; Mon, 13 Jan 2014 19:57:39 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.219.53 as permitted sender) client-ip=209.85.219.53; envelope-from=mh.in.england@gmail.com; helo=mail-oa0-f53.google.com; Received: from mail-oa0-f53.google.com ([209.85.219.53]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1W2ndi-00037f-Iy for bitcoin-development@lists.sourceforge.net; Mon, 13 Jan 2014 19:57:39 +0000 Received: by mail-oa0-f53.google.com with SMTP id h16so8583909oag.40 for ; Mon, 13 Jan 2014 11:57:33 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.60.165.36 with SMTP id yv4mr3486253oeb.55.1389643053100; Mon, 13 Jan 2014 11:57:33 -0800 (PST) Sender: mh.in.england@gmail.com Received: by 10.76.99.112 with HTTP; Mon, 13 Jan 2014 11:57:33 -0800 (PST) In-Reply-To: <20140113195319.GK38964@giles.gnomon.org.uk> References: <20140106120338.GA14918@savin> <20140110102037.GB25749@savin> <20140113133746.GI38964@giles.gnomon.org.uk> <20140113195319.GK38964@giles.gnomon.org.uk> Date: Mon, 13 Jan 2014 20:57:33 +0100 X-Google-Sender-Auth: Jhrp3Ewty5Qg33s1nh_ouPxx8lA Message-ID: From: Mike Hearn To: Roy Badami Content-Type: multipart/alternative; boundary=047d7b3a86748b75e404efdf7c0f X-Spam-Score: -0.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 1.0 HTML_MESSAGE BODY: HTML included in message 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: 1W2ndi-00037f-Iy Cc: "bitcoin-development@lists.sourceforge.net" Subject: Re: [Bitcoin-development] Stealth Addresses 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: Mon, 13 Jan 2014 19:57:39 -0000 --047d7b3a86748b75e404efdf7c0f Content-Type: text/plain; charset=UTF-8 > > On further reflection, I'm not sure I understand this use case of the > payment protocol. Since a PaymentRequest currently contains the > Outputs that specify the addresses to send to, reusing a > PaymentRequest like this without using stealth addresses implies > address reuse. Yes indeed ...... which is why we're talking about extending the protocol (in a future version! the first version isn't even out yet!). --047d7b3a86748b75e404efdf7c0f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On further reflection, I'm not sure I unders= tand this use case of the
payment protocol. =C2=A0Since a PaymentRequest currently contains the
Outputs that specify the addresses to send to, reusing a
PaymentRequest like this without using stealth addresses implies
address reuse.

Yes indeed ...... which is w= hy we're talking about extending the protocol (in a future version! the= first version isn't even out yet!).
--047d7b3a86748b75e404efdf7c0f--