From: Oleg Andreev <oleganza@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: [Bitcoin-development] Providing Payment Request within URI
Date: Tue, 24 Feb 2015 16:58:57 +0100 [thread overview]
Message-ID: <771EF431-6644-4BE4-B39C-CA73CFC18DB4@gmail.com> (raw)
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?
next reply other threads:[~2015-02-24 15:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-24 15:58 Oleg Andreev [this message]
2015-02-25 20:44 ` [Bitcoin-development] Providing Payment Request within URI Mike Hearn
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=771EF431-6644-4BE4-B39C-CA73CFC18DB4@gmail.com \
--to=oleganza@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
/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