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-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1W2evm-0002ZE-PC for bitcoin-development@lists.sourceforge.net; Mon, 13 Jan 2014 10:39:42 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.219.51 as permitted sender) client-ip=209.85.219.51; envelope-from=mh.in.england@gmail.com; helo=mail-oa0-f51.google.com; Received: from mail-oa0-f51.google.com ([209.85.219.51]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1W2evk-0006Rr-MV for bitcoin-development@lists.sourceforge.net; Mon, 13 Jan 2014 10:39:42 +0000 Received: by mail-oa0-f51.google.com with SMTP id m1so7736811oag.38 for ; Mon, 13 Jan 2014 02:39:35 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.182.88.202 with SMTP id bi10mr1055019obb.52.1389609575294; Mon, 13 Jan 2014 02:39:35 -0800 (PST) Sender: mh.in.england@gmail.com Received: by 10.76.99.112 with HTTP; Mon, 13 Jan 2014 02:39:35 -0800 (PST) In-Reply-To: References: <20140106120338.GA14918@savin> <20140110102037.GB25749@savin> Date: Mon, 13 Jan 2014 11:39:35 +0100 X-Google-Sender-Auth: MeTzIloETFguEiAz4-ELXUDzeLE Message-ID: From: Mike Hearn To: Gregory Maxwell Content-Type: multipart/alternative; boundary=089e0111be761cabe104efd7b151 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: 1W2evk-0006Rr-MV 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 10:39:42 -0000 --089e0111be761cabe104efd7b151 Content-Type: text/plain; charset=UTF-8 > > However, if you're able to use the payment protocol then you probably > don't need stealth addresses to prevent reuse. > I was thinking that people could upload a payment protocol file somewhere once (like to their personal web page, or shared via dropbox or google drive or some custom new pastebin style service), and then just encode a regular bitcoin URI into the qrcode on the billboard. Likewise, I could attach a payment request to an email and send it to you, and now you can pay me whenever you want forever. Getting a little static piece of data to someone *once* should be something we can make easy. Constantly refreshing it, on the other hand ... --089e0111be761cabe104efd7b151 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
However, if you're able to use the payment p= rotocol then you probably
don't need stealth addresses to prevent reuse.
I was thinking that people could upload a payment protocol file= somewhere once (like to their personal web page, or shared via dropbox or = google drive or some custom new pastebin style service), and then just enco= de a regular bitcoin URI into the qrcode on the billboard.

Likewise, I could attach a payment request to an email = and send it to you, and now you can pay me whenever you want forever.
=

Getting a little static piece of data to someone onc= e should be something we can make easy. Constantly refreshing it, on th= e other hand ...
--089e0111be761cabe104efd7b151--