Date: Sun, 7 May 2017 18:34:29 -0400
From: Peter Todd <pete@petertodd.org>
To: Pieter Wuille <pieter.wuille@gmail.com>
Message-ID: <20170507223429.GA23545@fedora-23-dvm>
References: <CAPg+sBh0sFA7b6a+48Oojwy655GB9W6Th8JiCpd+2ruQjPev8Q@mail.gmail.com>
	<CAPg+sBiPiLHZFoYY=gs6LT+Q2Kb5NmbVU05u7c+0WRPjveBJhQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="wRRV7LY7NUeQGEoC"
Content-Disposition: inline
In-Reply-To: <CAPg+sBiPiLHZFoYY=gs6LT+Q2Kb5NmbVU05u7c+0WRPjveBJhQ@mail.gmail.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] A BIP proposal for segwit addresses
Precedence: list


--wRRV7LY7NUeQGEoC
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sun, May 07, 2017 at 02:39:14PM -0700, Pieter Wuille via bitcoin-dev wro=
te:
> > I don't understand your comment about non-english speaking users.
> Obviously they cannot voice-communicate at all with only-english-speaking
> users, so there is no need to communicate voice-communicate addresses
> between them.
>=20
> I assume that Peter Todd is talking about cases where English speakers are
> interacting with non-native English speakers, who may know how to pronoun=
ce
> numbers or alphabetical characters, but not all special characters.

Exactly - knowledge of the English language isn't a binary. Equally, I don't
remember ever learning names of special characters in French class back in
elementary school, but I do recall us drilling the alphabet and especially
numbers repeatedly.

If I were trying to tell a French speaker a BTC address, I'd probably be ab=
le
to succesfully do it with bech32, but not with any encoding using special
characters.

> In general:
>=20
> In the past weeks people have contributed two new reference implementatio=
ns
> (Haskell and Rust), and a C++ and Go one are underway (see
> https://github.com/sipa/bech32).

FWIW, I also did a partial rust implementation of just the Bech32 encoding =
for
a prototype non-BTC use-case. Other than the version number being it's own
"chunk" I found it very straight-forward to implement and I think it'll make
for a nice replacement for what otherwise would have been hex digests.

--=20
https://petertodd.org 'peter'[:-1]@petertodd.org

--wRRV7LY7NUeQGEoC
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

-----BEGIN PGP SIGNATURE-----

iQEcBAEBCAAGBQJZD6D0AAoJECSBQD2l8JH7TrAH/j1qGrouE1xadWSyHR3yraN3
3tMfNMMnp3VnB3KTmz9u4Dv4ku4g7OW5vPLYlFKeUPnB2VAMkNPHrc2QWRYnNzeQ
fhVi4ue0BrPf7vaYB6icq7gW9zLraC7p4/qBbeK6ZFOGa2N+PHHfTRveWpT04ThH
tC97avRgiNM1JCGGy+I7oaKca6RNLuchPCW7OoFouV6h+qc+bztE5vt8aN0pQuUd
7Km7vgLIqK/Mq0GVPkZQqPlsWE6jXJnmWkbqrgIDQN6IM+YsVSiCKFCZhg/x8awZ
5SygIvRWL02GqoFnJidSRVQmA6Xwl1Ylr05CiU3azjqVKxmoEQeUOV3c/HskJWw=
=+BN2
-----END PGP SIGNATURE-----

--wRRV7LY7NUeQGEoC--