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
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mh.in.england@gmail.com>) id 1YQipO-0006MI-J6
for bitcoin-development@lists.sourceforge.net;
Wed, 25 Feb 2015 20:45:06 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 74.125.82.48 as permitted sender)
client-ip=74.125.82.48; envelope-from=mh.in.england@gmail.com;
helo=mail-wg0-f48.google.com;
Received: from mail-wg0-f48.google.com ([74.125.82.48])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1YQipJ-0005UT-RC
for bitcoin-development@lists.sourceforge.net;
Wed, 25 Feb 2015 20:45:06 +0000
Received: by wghl18 with SMTP id l18so6125522wgh.7
for <bitcoin-development@lists.sourceforge.net>;
Wed, 25 Feb 2015 12:44:55 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.180.21.174 with SMTP id w14mr251909wie.86.1424897095881;
Wed, 25 Feb 2015 12:44:55 -0800 (PST)
Sender: mh.in.england@gmail.com
Received: by 10.194.188.11 with HTTP; Wed, 25 Feb 2015 12:44:55 -0800 (PST)
In-Reply-To: <771EF431-6644-4BE4-B39C-CA73CFC18DB4@gmail.com>
References: <771EF431-6644-4BE4-B39C-CA73CFC18DB4@gmail.com>
Date: Wed, 25 Feb 2015 21:44:55 +0100
X-Google-Sender-Auth: 5k0w0Hk94g2-NJvnzqljZVwzzM4
Message-ID: <CANEZrP2VKpoeZrmae1p9nFJQ-PPMfXjEPfFRhmLacYkxwaN0Uw@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Oleg Andreev <oleganza@gmail.com>
Content-Type: multipart/alternative; boundary=047d7b6d9ac83ddcce050fefb5b4
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: 1YQipJ-0005UT-RC
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Providing Payment Request within URI
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, 25 Feb 2015 20:45:06 -0000
--047d7b6d9ac83ddcce050fefb5b4
Content-Type: text/plain; charset=UTF-8
Andreas' wallet supports this, but don't do it. Payment requests can get
larger in future even without signing. Exploding the capacity of a QR code
is very easy.
Instead, take a look at the Bluetooth/NFC discussion happening in a
different thread.
On Tue, Feb 24, 2015 at 4:58 PM, Oleg Andreev <oleganza@gmail.com> wrote:
> Hi,
>
> I wonder if there is a standard way to put Payment Request data into
> bitcoin: URI or directly into QR code. The goal is to allow device to
> generate a multi-output payment request on its own, without relying on the
> server and x509 certificates. When scanned via QR code from, say, POS, it's
> pretty secure, so no additional authentication needed.
>
> I'd like something like this:
>
> bitcoin:?r=data://<base64url-encoded-payment-request>
>
> If there's no standard for that, would it be a good idea to extend BIP72
> this way?
>
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming The Go Parallel Website,
> sponsored
> by Intel and developed in partnership with Slashdot Media, is your hub for
> all
> things parallel software development, from weekly thought leadership blogs
> to
> news, videos, case studies, tutorials and more. Take a look and join the
> conversation now. http://goparallel.sourceforge.net/
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
--047d7b6d9ac83ddcce050fefb5b4
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Andreas' wallet supports this, but don't do it. Pa=
yment requests can get larger in future even without signing. Exploding the=
capacity of a QR code is very easy.<div><br></div><div>Instead, take a loo=
k at the Bluetooth/NFC discussion happening in a different thread.</div></d=
iv><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Tue, Feb 24=
, 2015 at 4:58 PM, Oleg Andreev <span dir=3D"ltr"><<a href=3D"mailto:ole=
ganza@gmail.com" target=3D"_blank">oleganza@gmail.com</a>></span> wrote:=
<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-lef=
t:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
I wonder if there is a standard way to put Payment Request data into bitcoi=
n: URI or directly into QR code. The goal is to allow device to generate a =
multi-output payment request on its own, without relying on the server and =
x509 certificates. When scanned via QR code from, say, POS, it's pretty=
secure, so no additional authentication needed.<br>
<br>
I'd like something like this:<br>
<br>
bitcoin:?r=3Ddata://<base64url-encoded-payment-request><br>
<br>
If there's no standard for that, would it be a good idea to extend BIP7=
2 this way?<br>
---------------------------------------------------------------------------=
---<br>
Dive into the World of Parallel Programming The Go Parallel Website, sponso=
red<br>
by Intel and developed in partnership with Slashdot Media, is your hub for =
all<br>
things parallel software development, from weekly thought leadership blogs =
to<br>
news, videos, case studies, tutorials and more. Take a look and join the<br=
>
conversation now. <a href=3D"http://goparallel.sourceforge.net/" target=3D"=
_blank">http://goparallel.sourceforge.net/</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>
</blockquote></div><br></div>
--047d7b6d9ac83ddcce050fefb5b4--
|
