1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
|
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 <mh.in.england@gmail.com>) 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 <bitcoin-development@lists.sourceforge.net>;
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: <CAAS2fgTz0TaGhym_35V3N2-vHVzU9BeuV8q+QJjwh5bg77FEZg@mail.gmail.com>
References: <20140106120338.GA14918@savin>
<op.w9c5o7vgyldrnw@laptop-air.hsd1.ca.comcast.net>
<20140110102037.GB25749@savin>
<op.w9kkxcityldrnw@laptop-air.hsd1.ca.comcast.net>
<CABsx9T2G=yqSUGr0+Ju5-z9P++uS20AwLC+c3DnFMHtcQjQK6w@mail.gmail.com>
<CAAS2fgTz0TaGhym_35V3N2-vHVzU9BeuV8q+QJjwh5bg77FEZg@mail.gmail.com>
Date: Mon, 13 Jan 2014 11:39:35 +0100
X-Google-Sender-Auth: MeTzIloETFguEiAz4-ELXUDzeLE
Message-ID: <CANEZrP0huBWqgvQik9Yc26Tu4CwR0VSXcfC+qfzsZqvoU4VJGA@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Gregory Maxwell <gmaxwell@gmail.com>
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"
<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: 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
<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex">However, if you're able to use the payment p=
rotocol then you probably<br>
don't need stealth addresses to prevent reuse.<br></blockquote><div><br=
></div><div>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.</div>
<div><br></div><div>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.</div>=
<div><br></div><div>Getting a little static piece of data to someone <i>onc=
e</i> should be something we can make easy. Constantly refreshing it, on th=
e other hand ...</div>
</div></div></div>
--089e0111be761cabe104efd7b151--
|
