public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Oleg Andreev <oleganza@gmail.com>
To: Andreas Schildbach <andreas@schildbach.de>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Providing Payment Request within URI
Date: Thu, 26 Feb 2015 10:48:49 +0100	[thread overview]
Message-ID: <E7A57403-A898-461D-9750-A3A0001D82EB@gmail.com> (raw)
In-Reply-To: <54EEE81F.1000602@schildbach.de>

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=somescheme://<payment request>" to make it more compact. 

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:
> 
> 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
> 
> https://github.com/schildbach/bitcoin-wallet/blob/master/wallet/src/de/schildbach/wallet/ui/InputParser.java#L86
> 
> https://github.com/schildbach/bitcoin-wallet/blob/master/wallet/src/de/schildbach/wallet/util/Qr.java#L134
> 
> https://github.com/schildbach/bitcoin-wallet/blob/master/wallet/src/de/schildbach/wallet/util/Base43.java
> 
> Basically it's "BITCOIN:-" plus the payment request in Base43 encoded
> form. I picked Base43, because that's optimized for QR codes.
> 
> 
> On 02/24/2015 04: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://<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/
>> 
> 
> 




  reply	other threads:[~2015-02-26  9:49 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
2015-02-26  9:32 ` Andreas Schildbach
2015-02-26  9:48   ` Oleg Andreev [this message]
     [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=E7A57403-A898-461D-9750-A3A0001D82EB@gmail.com \
    --to=oleganza@gmail.com \
    --cc=andreas@schildbach.de \
    --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