Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1W3zsV-0003l1-F1 for bitcoin-development@lists.sourceforge.net; Fri, 17 Jan 2014 03:13:51 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of taplink.co designates 50.117.27.232 as permitted sender) client-ip=50.117.27.232; envelope-from=jeremy@taplink.co; helo=mail.taplink.co; Received: from mail.taplink.co ([50.117.27.232]) by sog-mx-1.v43.ch3.sourceforge.com with smtp (Exim 4.76) id 1W3zsU-0002Mv-Iy for bitcoin-development@lists.sourceforge.net; Fri, 17 Jan 2014 03:13:51 +0000 Received: from [10.64.218.203] ([166.147.102.214]) by mail.taplink.co ; Thu, 16 Jan 2014 19:23:58 -0800 References: <20140113133746.GI38964@giles.gnomon.org.uk> <20140114225321.GT38964@giles.gnomon.org.uk> <20140116212805.GA4421@petertodd.org> Mime-Version: 1.0 (1.0) In-Reply-To: <20140116212805.GA4421@petertodd.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-Id: X-Mailer: iPhone Mail (10B146) From: Jeremy Spilman Date: Thu, 16 Jan 2014 21:13:39 -0600 To: Peter Todd oclient: 166.147.102.214#jeremy@taplink.co#465 X-Spam-Score: -1.9 (-) 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_PASS SPF: sender matches SPF record -0.3 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain -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: 1W3zsU-0002Mv-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: Fri, 17 Jan 2014 03:13:51 -0000 I hear you, and I really don't care that much what it's called, as much as, d= oes it work and how! > I might even try to enter in a "reusable" address in blockchain.info, whic= h won't work, and I'll just figure > "must be some new unsupported thing" and move on with my life. >=20 Regardless of what it's called, Blockchain.info should tell the user, hey th= is address doesn't let the whole world see every single payment that's made t= o it! If you paid something to this address, only you know how to find the p= ayment - look for the stealth address in your transaction list.=20 So if we call the address that has the pubKeys the "reusable address" and th= e address that's generated from the shared secret the "stealth address" then= is everyone happy? :-)=