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 <gavinandresen@gmail.com>) id 1W2SQb-0005H1-T6
	for bitcoin-development@lists.sourceforge.net;
	Sun, 12 Jan 2014 21:18:41 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.212.174 as permitted sender)
	client-ip=209.85.212.174; envelope-from=gavinandresen@gmail.com;
	helo=mail-wi0-f174.google.com; 
Received: from mail-wi0-f174.google.com ([209.85.212.174])
	by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1W2SQZ-0004ju-SA
	for bitcoin-development@lists.sourceforge.net;
	Sun, 12 Jan 2014 21:18:41 +0000
Received: by mail-wi0-f174.google.com with SMTP id g10so374880wiw.7
	for <bitcoin-development@lists.sourceforge.net>;
	Sun, 12 Jan 2014 13:18:33 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.194.23.201 with SMTP id o9mr227576wjf.67.1389561513659; Sun,
	12 Jan 2014 13:18:33 -0800 (PST)
Received: by 10.194.10.197 with HTTP; Sun, 12 Jan 2014 13:18:33 -0800 (PST)
In-Reply-To: <op.w9kkxcityldrnw@laptop-air.hsd1.ca.comcast.net>
References: <20140106120338.GA14918@savin>
	<op.w9c5o7vgyldrnw@laptop-air.hsd1.ca.comcast.net>
	<20140110102037.GB25749@savin>
	<op.w9kkxcityldrnw@laptop-air.hsd1.ca.comcast.net>
Date: Sun, 12 Jan 2014 16:18:33 -0500
Message-ID: <CABsx9T2G=yqSUGr0+Ju5-z9P++uS20AwLC+c3DnFMHtcQjQK6w@mail.gmail.com>
From: Gavin Andresen <gavinandresen@gmail.com>
To: Jeremy Spilman <jeremy@taplink.co>
Content-Type: multipart/alternative; boundary=047d7b3a956c6a576304efcc8061
X-Spam-Score: -0.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
	(gavinandresen[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	1.0 HTML_MESSAGE           BODY: HTML included in message
	-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: 1W2SQZ-0004ju-SA
Cc: "bitcoin-development@lists.sourceforge.net"
	<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: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Sun, 12 Jan 2014 21:18:42 -0000

--047d7b3a956c6a576304efcc8061
Content-Type: text/plain; charset=ISO-8859-1

On Sun, Jan 12, 2014 at 5:33 AM, Jeremy Spilman <jeremy@taplink.co> wrote:

> ...
> Now, you would need to get two pubkeys to the payer, throw in a prefix to
> help standardize it, and end up with addresses that could look like (for
> example):
>
>
> xSTLxsn59oaupR6ZKt2yddQ4dp5hcFinnTWkvsDiXtHgAEDg5ajNVzTY8MMQsmqnEn3ZMKxQzrfC3pDimfTWMkiUb7x3jX3J26JSX
>
> tSTLcpwzupCFL3maVZkSiB9ib3BXsCAfkhMLgckQEyoj8Tk83ANzofeuDdbX6bSPqNRfACLLFYK8EwVo1jdjxNDFNDWxhnQiAy4ba
>

No, please. Make it easy for non-geeks, extend the payment protocol, or
we'll spend the next two years writing code that tries to ignore linebreaks
and spaces and changing <input> elements in HTML forms to <textarea> ....

-- 
--
Gavin Andrese

--047d7b3a956c6a576304efcc8061
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On S=
un, Jan 12, 2014 at 5:33 AM, Jeremy Spilman <span dir=3D"ltr">&lt;<a href=
=3D"mailto:jeremy@taplink.co" target=3D"_blank">jeremy@taplink.co</a>&gt;</=
span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im">...</div>
Now, you would need to get two pubkeys to the payer, throw in a prefix to<b=
r>
help standardize it, and end up with addresses that could look like (for<br=
>
example):<br>
<br>
xSTLxsn59oaupR6ZKt2yddQ4dp5hcFinnTWkvsDiXtHgAEDg5ajNVzTY8MMQsmqnEn3ZMKxQzrf=
C3pDimfTWMkiUb7x3jX3J26JSX<br>
tSTLcpwzupCFL3maVZkSiB9ib3BXsCAfkhMLgckQEyoj8Tk83ANzofeuDdbX6bSPqNRfACLLFYK=
8EwVo1jdjxNDFNDWxhnQiAy4ba<br></blockquote><div><br></div><div>No, please. =
Make it easy for non-geeks, extend the payment protocol, or we&#39;ll spend=
 the next two years writing code that tries to ignore linebreaks and spaces=
 and changing &lt;input&gt; elements in HTML forms to &lt;textarea&gt; ....=
</div>
</div><div><br></div>-- <br>--<br>Gavin Andrese<br>
</div></div>

--047d7b3a956c6a576304efcc8061--