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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <oleganza@gmail.com>) id 1YQv42-0004WB-PY
for bitcoin-development@lists.sourceforge.net;
Thu, 26 Feb 2015 09:49:02 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.212.176 as permitted sender)
client-ip=209.85.212.176; envelope-from=oleganza@gmail.com;
helo=mail-wi0-f176.google.com;
Received: from mail-wi0-f176.google.com ([209.85.212.176])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1YQv40-0004O5-Tu
for bitcoin-development@lists.sourceforge.net;
Thu, 26 Feb 2015 09:49:02 +0000
Received: by mail-wi0-f176.google.com with SMTP id h11so39518164wiw.3
for <bitcoin-development@lists.sourceforge.net>;
Thu, 26 Feb 2015 01:48:54 -0800 (PST)
X-Received: by 10.181.13.4 with SMTP id eu4mr14748008wid.41.1424944133730;
Thu, 26 Feb 2015 01:48:53 -0800 (PST)
Received: from ?IPv6:2a01:e35:8a2c:a630:3040:78ad:a018:c67b?
([2a01:e35:8a2c:a630:3040:78ad:a018:c67b])
by mx.google.com with ESMTPSA id
md8sm29025457wic.13.2015.02.26.01.48.50
(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
Thu, 26 Feb 2015 01:48:52 -0800 (PST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: Oleg Andreev <oleganza@gmail.com>
In-Reply-To: <54EEE81F.1000602@schildbach.de>
Date: Thu, 26 Feb 2015 10:48:49 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <E7A57403-A898-461D-9750-A3A0001D82EB@gmail.com>
References: <771EF431-6644-4BE4-B39C-CA73CFC18DB4@gmail.com>
<54EEE81F.1000602@schildbach.de>
To: Andreas Schildbach <andreas@schildbach.de>
X-Mailer: Apple Mail (2.2070.6)
X-Spam-Score: -1.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
(oleganza[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
-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: 1YQv40-0004O5-Tu
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: Thu, 26 Feb 2015 09:49:02 -0000
Thanks for references. Yeah, I don't need X509 signing (if I could use =
certificates, I wouldn't need to include PR in the URL in the first =
place).
I presume you used "BITCOIN:-<payment request>" instead of =
"bitcoin:?r=3Dsomescheme://<payment request>" to make it more compact.=20=
I also tried to look up Base43, but I could not find any info on how it =
is specifically optimized for QR codes. Could you enlighten me?
> On 26 Feb 2015, at 10:32, Andreas Schildbach <andreas@schildbach.de> =
wrote:
>=20
> Yeah, you'd be limited to simple usecases. X509 signing or lots of
> outputs will make the QR code hard to scan. However, if all you want =
to
> do is send to a custom script (without using P2SH) I invite you to =
have
> a look at
>=20
> =
https://github.com/schildbach/bitcoin-wallet/blob/master/wallet/src/de/sch=
ildbach/wallet/ui/InputParser.java#L86
>=20
> =
https://github.com/schildbach/bitcoin-wallet/blob/master/wallet/src/de/sch=
ildbach/wallet/util/Qr.java#L134
>=20
> =
https://github.com/schildbach/bitcoin-wallet/blob/master/wallet/src/de/sch=
ildbach/wallet/util/Base43.java
>=20
> Basically it's "BITCOIN:-" plus the payment request in Base43 encoded
> form. I picked Base43, because that's optimized for QR codes.
>=20
>=20
> On 02/24/2015 04:58 PM, Oleg Andreev wrote:
>> Hi,
>>=20
>> 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.
>>=20
>> I'd like something like this:=20
>>=20
>> bitcoin:?r=3Ddata://<base64url-encoded-payment-request>
>>=20
>> 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=20
>> conversation now. http://goparallel.sourceforge.net/
>>=20
>=20
>=20
|
