From: Peter Todd <pete@petertodd•org>
To: Andreas Schildbach <andreas@schildbach•de>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] A BIP proposal for segwit addresses
Date: Tue, 21 Mar 2017 15:14:54 -0400 [thread overview]
Message-ID: <20170321191454.GA17834@savin.petertodd.org> (raw)
In-Reply-To: <oarjko$8fp$1@blaine.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 946 bytes --]
On Tue, Mar 21, 2017 at 05:16:30PM +0100, Andreas Schildbach via bitcoin-dev wrote:
> Why use Base 32 when the QR code alphanumeric mode allows 44 characters?
> In Bitcoin Wallet, I use Base 43 (alphabet:
> "0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ$*+-./:") for most efficient QR
> code encoding. I only leave out the space character because it gets
> replaced by "+" in URLs.
Doing that only makes addresses a few % shorter, at the cost of significant
downsides. For example, not everyone knows what those additional characters
are called, particularly for non-English-speaking users. Non-alphanumeric
characters also complicate using the addresses in a variety of contexts ('/'
in particularly isn't valid in filenames).
I'd suggest you review the "Rational" section of the BIP for more details:
https://github.com/sipa/bech32/blob/master/bip-witaddr.mediawiki#rationale
--
https://petertodd.org 'peter'[:-1]@petertodd.org
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
next prev parent reply other threads:[~2017-03-21 19:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-20 21:35 Pieter Wuille
2017-03-21 16:16 ` Andreas Schildbach
2017-03-21 19:14 ` Peter Todd [this message]
2017-03-29 10:07 ` Andreas Schildbach
2017-03-30 4:50 ` Lucas Ontivero
2017-05-07 21:39 ` Pieter Wuille
2017-05-07 22:34 ` Peter Todd
2017-05-20 20:13 ` Pieter Wuille
2018-07-26 13:43 ` Russell O'Connor
2018-07-26 14:31 ` Russell O'Connor
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=20170321191454.GA17834@savin.petertodd.org \
--to=pete@petertodd$(echo .)org \
--cc=andreas@schildbach$(echo .)de \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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