From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1W2oPx-00067u-AB for bitcoin-development@lists.sourceforge.net; Mon, 13 Jan 2014 20:47:29 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.215.51 as permitted sender) client-ip=209.85.215.51; envelope-from=gmaxwell@gmail.com; helo=mail-la0-f51.google.com; Received: from mail-la0-f51.google.com ([209.85.215.51]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1W2oPw-0004BR-HO for bitcoin-development@lists.sourceforge.net; Mon, 13 Jan 2014 20:47:29 +0000 Received: by mail-la0-f51.google.com with SMTP id c6so796442lan.10 for ; Mon, 13 Jan 2014 12:47:21 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.152.22.228 with SMTP id h4mr629736laf.71.1389646041804; Mon, 13 Jan 2014 12:47:21 -0800 (PST) Received: by 10.112.198.65 with HTTP; Mon, 13 Jan 2014 12:47:21 -0800 (PST) In-Reply-To: <52D44F86.1040407@gmail.com> References: <20140106120338.GA14918@savin> <20140110102037.GB25749@savin> <20140113194049.GJ38964@giles.gnomon.org.uk> <52D4458C.6010909@gmail.com> <20140113201407.GB7941@petertodd.org> <52D44F86.1040407@gmail.com> Date: Mon, 13 Jan 2014 12:47:21 -0800 Message-ID: From: Gregory Maxwell To: Alan Reiner Content-Type: text/plain; charset=UTF-8 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 (gmaxwell[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: 1W2oPw-0004BR-HO Cc: Bitcoin Development 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:47:29 -0000 On Mon, Jan 13, 2014 at 12:41 PM, Alan Reiner wrote: > It's not public. When I say "please pay me" I also say "use this > multiplier". The multiplier isn't published, and it's not publicly > discoverable without my wallet (or access to my email). If you have enough of a communications channel to do that you can just give the person the finished address (authentication aside). The idea here is to cover the cases where the communication is one way or nearly so. Consider a donation address on a fully static webpage, in a forum signature or email address, or on a billboard. ... or where users-being-users mean that the user isn't going to start up their wallet software to compute a new multiplier every time they give out an address no matter how much we whine at them.