<div dir="ltr">I don't know if i should response to this mail list or make a comment in commit file (<a href="https://github.com/sipa/bech32/commit/52b5a0fa6d3174c4150393fb7d6b58d34b4f5e0b#diff-d23a42e5c904045098e8f8b1189f481e">https://github.com/sipa/bech32/commit/52b5a0fa6d3174c4150393fb7d6b58d34b4f5e0b#diff-d23a42e5c904045098e8f8b1189f481e</a>)<br><br>* Motivation:<div><br></div><div>Here I think it could worth to mention that 58 requires mathematical operations over big numbers. This is not very fast and most of the programming languages don't provide support for big numbers OOB.<br><br>* Why not make an address format that is generic for all scriptPubKeys?: </div><div><br></div><div>I understand that if a new generic encoding format is introduced that could lead to some confusions but what if in the future there is a new type of address that can also be encoded with bech32? Don't we need a address type anyway?</div><div><br></div><div>thx</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">2017-03-29 7:07 GMT-03:00 Andreas Schildbach via bitcoin-dev <span dir="ltr"><<a href="mailto:bitcoin-dev@lists.linuxfoundation.org" target="_blank">bitcoin-dev@lists.linuxfoundation.org</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 03/21/2017 08:14 PM, Peter Todd via bitcoin-dev wrote:<br>
> On Tue, Mar 21, 2017 at 05:16:30PM +0100, Andreas Schildbach via bitcoin-dev wrote:<br>
>> Why use Base 32 when the QR code alphanumeric mode allows 44 characters?<br>
>> In Bitcoin Wallet, I use Base 43 (alphabet:<br>
>> "<wbr>0123456789ABCDEFGHIJKLMNOPQRST<wbr>UVWXYZ$*+-./:") for most efficient QR<br>
>> code encoding. I only leave out the space character because it gets<br>
>> replaced by "+" in URLs.<br>
><br>
> Doing that only makes addresses a few % shorter, at the cost of significant<br>
> downsides. For example, not everyone knows what those additional characters<br>
> are called, particularly for non-English-speaking users. Non-alphanumeric<br>
> characters also complicate using the addresses in a variety of contexts ('/'<br>
> in particularly isn't valid in filenames).<br>
<br>
</span>I'm not convinced that transmitting addresses via voice should be a<br>
usecase to target at. I don't understand your comment about non-english<br>
speaking users. Obviously they cannot voice-communicate at all with<br>
only-english-speaking users, so there is no need to communicate<br>
voice-communicate addresses between them.<br>
<br>
Addresses in QR codes, addresses in URLs and addresses in NFC NDEF<br>
messages are the three most used forms.<br>
<br>
Speaking of URLs, actually Base 32 (as well as Base 43) makes QR codes<br>
*bigger* because due to the characters used for URL parameters (?&=)<br>
those QR codes are locked to binary mode. To make them shorter, we'd<br>
need to use something like "Base 64url" (or ideally Base 94 -- all<br>
printable ASCII characters).<br>
<div class="HOEnZb"><div class="h5"><br>
<br>
______________________________<wbr>_________________<br>
bitcoin-dev mailing list<br>
<a href="mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.<wbr>linuxfoundation.org</a><br>
<a href="https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" rel="noreferrer" target="_blank">https://lists.linuxfoundation.<wbr>org/mailman/listinfo/bitcoin-<wbr>dev</a><br>
</div></div></blockquote></div><br></div>