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 12:14:22 +0100 [thread overview]
Message-ID: <DFD6CE20-6B88-4629-BF5E-23250C306B6E@gmail.com> (raw)
In-Reply-To: <54EEF12B.2050803@schildbach.de>
> Base43 is the same as any BaseX standard, but using a different alphabet
> (43 characters). It's meant to be used for efficiently storing binary
> data into QR codes. The alphabet is picked to match the 'Alphanumeric'
> input mode of QR codes as closely as possible, but at the same time be
> allowed in URIs.
Does it mean Base58 or Base64 take more space in QR code than Base43? Do you have an estimate of the gains?
next prev parent reply other threads:[~2015-02-26 11:14 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
[not found] ` <54EEF12B.2050803@schildbach.de>
2015-02-26 11:14 ` Oleg Andreev [this message]
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=DFD6CE20-6B88-4629-BF5E-23250C306B6E@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