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
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <ewillbefull@gmail.com>) id 1V4fr4-0004ZY-3u
for bitcoin-development@lists.sourceforge.net;
Wed, 31 Jul 2013 23:30:54 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.212.174 as permitted sender)
client-ip=209.85.212.174; envelope-from=ewillbefull@gmail.com;
helo=mail-wi0-f174.google.com;
Received: from mail-wi0-f174.google.com ([209.85.212.174])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1V4fr2-0002gs-V7
for bitcoin-development@lists.sourceforge.net;
Wed, 31 Jul 2013 23:30:54 +0000
Received: by mail-wi0-f174.google.com with SMTP id j17so5575142wiw.13
for <bitcoin-development@lists.sourceforge.net>;
Wed, 31 Jul 2013 16:30:46 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.194.95.100 with SMTP id dj4mr31120471wjb.55.1375313446703;
Wed, 31 Jul 2013 16:30:46 -0700 (PDT)
Received: by 10.194.162.34 with HTTP; Wed, 31 Jul 2013 16:30:46 -0700 (PDT)
In-Reply-To: <CABsx9T14Dfh8SEe6wsCJjE=S8hTcfDrAUNMBCjtkvM+UH-bAYQ@mail.gmail.com>
References: <CABsx9T0Ly67ZNJhoRQk0L9Q0-ucq3e=24b5Tg6GRKspRKKtP-g@mail.gmail.com>
<20130731084538.GL16713@giles.gnomon.org.uk>
<CABsx9T3Xvnw2H6awgnT7mr-HzJOqCp_nOVM57BD-B9mY4R43aQ@mail.gmail.com>
<CABsx9T14Dfh8SEe6wsCJjE=S8hTcfDrAUNMBCjtkvM+UH-bAYQ@mail.gmail.com>
Date: Wed, 31 Jul 2013 17:30:46 -0600
Message-ID: <CAGRKETunznLbBZO1gnS7WZH5sn=TnmKPS4Gz_Nrtocoe5devbw@mail.gmail.com>
From: E willbefull <ewillbefull@gmail.com>
To: Gavin Andresen <gavinandresen@gmail.com>,
bitcoin-development@lists.sourceforge.net
Content-Type: multipart/alternative; boundary=047d7bb03d5e721b0f04e2d71d03
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
(ewillbefull[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: 1V4fr2-0002gs-V7
Subject: Re: [Bitcoin-development] Payment Protocol: BIP 70, 71, 72
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: Wed, 31 Jul 2013 23:30:54 -0000
--047d7bb03d5e721b0f04e2d71d03
Content-Type: text/plain; charset=ISO-8859-1
I think it's important to expect PaymentRequest-only bitcoin URIs in the
future. Some types of payments (exotic transactions) may not make sense to
have a single fallback address. Or, a page with a bitcoin URI link may be
relying on a separate service provider to assemble the transaction.
On Wed, Jul 31, 2013 at 5:33 AM, Gavin Andresen <gavinandresen@gmail.com>wrote:
> On Wed, Jul 31, 2013 at 6:45 PM, Roy Badami <roy@gnomon.org.uk> wrote:
> >
> > Is it envisaged to be possible/sensible to have a URI that is *only* a
> > payment request? i.e. something like the following (although I'm not
> > sure this is a valid URI):
> >
> > bitcoin:?request=https%3A%2F%2Fmerchant.com%2Fpay.php%3Fh%3D2a8628fc2fbe
>
> I think we'll want a bitcoin address in there for a long time for
> backwards compatibility.
>
> If web browser support for arbitrary MIME types is strong enough (I
> haven't tested), then a payment request can be initiated with just an
> anchor tag:
> <a href="https://merchant.com/pay.php?3D2a8628fc2fbe"
> type="application/bitcoin-paymentrequest">
>
> Doing it that way saves a http round-trip.
>
> --
> --
> Gavin Andresen
>
>
> ------------------------------------------------------------------------------
> Get your SQL database under version control now!
> Version control is standard for application code, but databases havent
> caught up. So what steps can you take to put your SQL databases under
> version control? Why should you start doing it? Read more to find out.
> http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
--047d7bb03d5e721b0f04e2d71d03
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">I think it's important to expect PaymentRequest-only b=
itcoin URIs in the future. Some types of payments (exotic transactions) may=
not make sense to have a single fallback address. Or, a page with a bitcoi=
n URI link may be relying on a separate service provider to assemble the tr=
ansaction.<br>
</div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Wed,=
Jul 31, 2013 at 5:33 AM, Gavin Andresen <span dir=3D"ltr"><<a href=3D"m=
ailto:gavinandresen@gmail.com" target=3D"_blank">gavinandresen@gmail.com</a=
>></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">On Wed, Jul 31, 2013 at 6:=
45 PM, Roy Badami <<a href=3D"mailto:roy@gnomon.org.uk">roy@gnomon.org.u=
k</a>> wrote:<br>
><br>
> Is it envisaged to be possible/sensible to have a URI that is *only* a=
<br>
> payment request? =A0i.e. something like the following (although I'=
m not<br>
> sure this is a valid URI):<br>
><br>
> bitcoin:?request=3Dhttps%3A%2F%2Fmerchant.com%2Fpay.php%3Fh%3D2a8628fc=
2fbe<br>
<br>
</div>I think we'll want a bitcoin address in there for a long time for=
<br>
backwards compatibility.<br>
<br>
If web browser support for arbitrary MIME types is strong enough (I<br>
haven't tested), then a payment request can be initiated with just an<b=
r>
anchor tag:<br>
=A0 <a href=3D"<a href=3D"https://merchant.com/pay.php?3D2a8628fc2f=
be" target=3D"_blank">https://merchant.com/pay.php?3D2a8628fc2fbe</a>"=
<br>
type=3D"application/bitcoin-paymentrequest"><br>
<br>
Doing it that way saves a http round-trip.<br>
<br>
--<br>
--<br>
Gavin Andresen<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
---------------------------------------------------------------------------=
---<br>
Get your SQL database under version control now!<br>
Version control is standard for application code, but databases havent<br>
caught up. So what steps can you take to put your SQL databases under<br>
version control? Why should you start doing it? Read more to find out.<br>
<a href=3D"http://pubads.g.doubleclick.net/gampad/clk?id=3D49501711&iu=
=3D/4140/ostg.clktrk" target=3D"_blank">http://pubads.g.doubleclick.net/gam=
pad/clk?id=3D49501711&iu=3D/4140/ostg.clktrk</a><br>
_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo=
pment@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
</div></div></blockquote></div><br></div>
--047d7bb03d5e721b0f04e2d71d03--
|
