From mboxrd@z Thu Jan 1 00:00:00 1970 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 ) 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 ; 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: From: Mike Hearn To: Oleg Andreev 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 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 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:// > > 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
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.

Instead, take a loo= k 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 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.

I'd like something like this:

bitcoin:?r=3Ddata://<base64url-encoded-payment-request>

If there's no standard for that, would it be a good idea to extend BIP7= 2 this way?
---------------------------------------------------------------------------= ---
Dive into the World of Parallel Programming The Go Parallel Website, sponso= red
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-develo= pment@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-de= velopment

--047d7b6d9ac83ddcce050fefb5b4--