From: Mike Hearn <mike@plan99.net>
To: "Ryan X. Charles" <ryan@bitpay.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] BIP70 proposed changes
Date: Fri, 21 Feb 2014 21:04:31 +0530 [thread overview]
Message-ID: <CANEZrP25u1V2rv_XM1pKzxm4YvUec89Vf1OmVujJLFBzEmmbXA@mail.gmail.com> (raw)
In-Reply-To: <5303B110.70603@bitpay.com>
[-- Attachment #1: Type: text/plain, Size: 785 bytes --]
>
> One more thing. The new bitcoin URI in BIP 72 is extremely long and
> makes for very dense QR codes.
BIP 73 seems OK except that existing wallets that can scan QR codes will
choke. One reason the new URIs are long is for backwards compatibility.
One thing that makes the URI smaller is not escaping the payment URL -
bitcoinj/Bitcoin Wallet at least does not require it, and it reduces the
size of the QR code by a non-trivial amount.
Removing the https:// and just defaulting to it also saves some bytes.
Finally, BitPay is using rather long invoice IDs. Do you really need an ID
like JkLdFhQVFqmUurXpPXZcRp? That's a really huge ID space and the invoices
expire fast. So you could potentially implement a short mapping on the
server side and make much smaller IDs that way.
[-- Attachment #2: Type: text/html, Size: 1152 bytes --]
next prev parent reply other threads:[~2014-02-21 15:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-18 17:31 [Bitcoin-development] BIP70 proposed changes Andreas Schildbach
2014-02-18 19:14 ` Ryan X. Charles
2014-02-18 20:15 ` Gavin Andresen
2014-02-18 21:40 ` Andreas Schildbach
2014-02-19 14:10 ` Jeff Garzik
2014-02-19 16:44 ` Mike Hearn
2014-05-06 2:35 ` Odinn Cyberguerrilla
2014-05-06 8:22 ` Alon Muroch
2014-02-18 21:47 ` Peter Todd
2014-02-18 23:41 ` Bernd Jendrissek
2014-02-18 22:02 ` Derber
2014-02-21 15:34 ` Mike Hearn [this message]
2014-03-05 10:18 ` Mike Hearn
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=CANEZrP25u1V2rv_XM1pKzxm4YvUec89Vf1OmVujJLFBzEmmbXA@mail.gmail.com \
--to=mike@plan99.net \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=ryan@bitpay.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