public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Mike Hearn <mike@plan99.net>
To: Oleg Andreev <oleganza@gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Providing Payment Request within URI
Date: Wed, 25 Feb 2015 21:44:55 +0100	[thread overview]
Message-ID: <CANEZrP2VKpoeZrmae1p9nFJQ-PPMfXjEPfFRhmLacYkxwaN0Uw@mail.gmail.com> (raw)
In-Reply-To: <771EF431-6644-4BE4-B39C-CA73CFC18DB4@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1528 bytes --]

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
>

[-- Attachment #2: Type: text/html, Size: 2135 bytes --]

  reply	other threads:[~2015-02-25 20:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-24 15:58 [Bitcoin-development] Providing Payment Request within URI Oleg Andreev
2015-02-25 20:44 ` Mike Hearn [this message]
2015-02-26  9:32 ` Andreas Schildbach
2015-02-26  9:48   ` Oleg Andreev
     [not found]     ` <54EEF12B.2050803@schildbach.de>
2015-02-26 11:14       ` Oleg Andreev
2015-02-26 12:11         ` Andreas Schildbach

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CANEZrP2VKpoeZrmae1p9nFJQ-PPMfXjEPfFRhmLacYkxwaN0Uw@mail.gmail.com \
    --to=mike@plan99.net \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=oleganza@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox