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 1W2nhI-0000Pn-R1 for bitcoin-development@lists.sourceforge.net; Mon, 13 Jan 2014 20:01:20 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gnomon.org.uk designates 93.93.131.22 as permitted sender) client-ip=93.93.131.22; envelope-from=roy@gnomon.org.uk; helo=darla.gnomon.org.uk; Received: from darla.gnomon.org.uk ([93.93.131.22]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) id 1W2nhF-0001y7-MD for bitcoin-development@lists.sourceforge.net; Mon, 13 Jan 2014 20:01:20 +0000 Received: from darla.gnomon.org.uk (localhost.gnomon.org.uk [127.0.0.1]) by darla.gnomon.org.uk (8.14.3/8.14.3) with ESMTP id s0DK15QK011526 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 13 Jan 2014 20:01:10 GMT (envelope-from roy@darla.gnomon.org.uk) Received: (from roy@localhost) by darla.gnomon.org.uk (8.14.3/8.14.1/Submit) id s0DK15ua011525; Mon, 13 Jan 2014 20:01:05 GMT (envelope-from roy) Date: Mon, 13 Jan 2014 20:01:05 +0000 From: Roy Badami To: Mike Hearn Message-ID: <20140113200104.GL38964@giles.gnomon.org.uk> References: <20140106120338.GA14918@savin> <20140110102037.GB25749@savin> <20140113133746.GI38964@giles.gnomon.org.uk> <20140113195319.GK38964@giles.gnomon.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) 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 SPF_HELO_PASS SPF: HELO matches SPF record -0.0 SPF_PASS SPF: sender matches SPF record -0.1 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain X-Headers-End: 1W2nhF-0001y7-MD 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 20:01:21 -0000 rOn Mon, Jan 13, 2014 at 08:57:33PM +0100, Mike Hearn wrote: > > > > 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!). Yes, sorry, I miscontrued the thread here and now see that your message was exactly talking about using stealth addresses within the payment protocol. Sorry for the confusion. roy