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; 
MIME-Version: 1.0
Sender: mh.in.england@gmail.com
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
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
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Providing Payment Request within URI
Precedence: list

--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&#39; wallet supports this, but don&#39;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">&lt;<a href=3D"mailto:ole=
ganza@gmail.com" target=3D"_blank">oleganza@gmail.com</a>&gt;</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&#39;s pretty=
 secure, so no additional authentication needed.<br>
<br>
I&#39;d like something like this:<br>
<br>
bitcoin:?r=3Ddata://&lt;base64url-encoded-payment-request&gt;<br>
<br>
If there&#39;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--