From: Jonas Schnelli <dev@jonasschnelli.ch>
Content-Type: multipart/signed;
	boundary="Apple-Mail=_FF7A8F49-22A2-4052-8E15-9F0CBE2C7B33";
	protocol="application/pgp-signature"; micalg=pgp-sha256
Mime-Version: 1.0 (Mac OS X Mail 11.4 \(3445.8.2\))
Date: Mon, 25 Jun 2018 22:10:12 +0200
References: <CAPg+sBhGMxXatsyCAqeboQKH8ASSFAfiXzxyXR9UrNFnah5PPw@mail.gmail.com>
	<CHCiA27GTRiVfkF1DoHdroJL1rQS77ocB42nWxIIhqi_fY3VbB3jsMQveRJOtsJiA4RaCAVe3VZmLZsXVYS3A5wVLNP2OgKQiHE0T27P2qc=@achow101.com>
	<21a616f5-7a17-35b9-85ea-f779f20a6a2d@satoshilabs.com>
	<20180621195654.GC99379@coinkite.com>
	<CAPg+sBgdQqZ8sRSn=dd9EkavYJA6GBiCu6-v5k9ca-9WLPp72Q@mail.gmail.com>
	<ljk5Z_a3KK6DHfmPJxI8o9W2CkwszkUG34h0i1MTGU4ss8r3BTQ3GnTtDTfWF6J7ZqcSAmejzrr11muWqYN-_wnWw_0NFn5_lggNnjI0_Rc=@achow101.com>
	<f8f5b1e3-692a-fc1e-2ad3-c4ad4464957f@satoshilabs.com>
To: Tomas Susanka <tomas.susanka@satoshilabs.com>,
	Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
In-Reply-To: <f8f5b1e3-692a-fc1e-2ad3-c4ad4464957f@satoshilabs.com>
Message-Id: <CB0533AE-702D-422F-8C61-2C7AD7A2B6D5@jonasschnelli.ch>
Subject: Re: [bitcoin-dev] BIP 174 thoughts
Precedence: list


--Apple-Mail=_FF7A8F49-22A2-4052-8E15-9F0CBE2C7B33
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_485E5C15-A949-4CBB-9533-6C4C7AA55272"


--Apple-Mail=_485E5C15-A949-4CBB-9533-6C4C7AA55272
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi
> As was partially brought up by William, shouldn't we consider using
> bech32? It doesn't break on double-click and it is a dependency for
> native Segwit addresses anyway, so wallets might already support it or
> they will at some point. But we should probably run some numbers on =
this
> first, since bech32 will obviously be larger than base64.
I don=E2=80=99t think bech32 is a fit here.
Bech32 is a BCH where the error detecting properties are optimised for =
1023 chars max and in the special case of the Bech32 BCH, error =
detection of 4 chars are guaranteed with a max length of 90 chars.

/jonas

--Apple-Mail=_485E5C15-A949-4CBB-9533-6C4C7AA55272
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">Hi<br=
 class=3D""><div><blockquote type=3D"cite" class=3D""><div class=3D""><div=
 text=3D"#000000" bgcolor=3D"#FFFFFF" class=3D""><div =
class=3D"moz-text-plain" wrap=3D"true" style=3D"font-family:
      -moz-fixed; font-size: 12px;" lang=3D"x-unicode"><pre wrap=3D"" =
class=3D"">As was partially brought up by William, shouldn't we consider =
using
bech32? It doesn't break on double-click and it is a dependency for
native Segwit addresses anyway, so wallets might already support it or
they will at some point. But we should probably run some numbers on this
first, since bech32 will obviously be larger than base64.
</pre></div></div></div></blockquote></div>I don=E2=80=99t think bech32 =
is a fit here.<div class=3D"">Bech32 is a BCH where the error detecting =
properties are optimised for 1023 chars max and in the special case of =
the Bech32 BCH, error detection of 4 chars are guaranteed with a max =
length of 90 chars.</div><div class=3D""><br class=3D""></div><div =
class=3D"">/jonas</div></body></html>=

--Apple-Mail=_485E5C15-A949-4CBB-9533-6C4C7AA55272--

--Apple-Mail=_FF7A8F49-22A2-4052-8E15-9F0CBE2C7B33
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQIzBAEBCAAdFiEEyhopCNzi8TB0xizeHrd2uwPHki0FAlsxTCQACgkQHrd2uwPH
ki1QeQ//XVFnOJAx1UZpi4niJxeKBHVhhIpSjpBgp5brfdxMimCm5QvGn2ypvhvg
ddV1cIYQwlyAr0hjh1StMUcVEtNWLIZepNNDai47g2rb51SufH3HFccQA2HbPVsk
HDf8UHXHwj9shF6QQPGKQCqQEVw/eV9C7Z2SjUFECVikjynMktzeVsMnce81sQqu
F/Ltf4lE2zoKS0KxcINoF4OmCrbz9RAeV2v19/d/NyKhI4WhP7STodbO7/tB3djQ
CYtKHkI5vW65WpijueWFgBiK07Mb1W/JcS3gi/REycHRndzIPXPVpYdZdFPhPz5n
mZOR/KHrXNlZkGD1cY3Nqo79UiyG62vofrj+SDQLufkCwh+/4Y58unD2jCgUYUmV
Hvs/5nWKXGQfLU2CW5ivTO0juI/yQdY23fIqAvSNPll+rZaFLnJqV9c3jyuh2h6W
fjFuZOuDl+8mCljvvQTUnvL0M2D6YxfMrgTlHYdr3r4CUI99Fxr8FAEs1bSUvKrg
A+S7bLBXACPom1IKOAV2lbcynJN7ID8yFkIt/RiwJnzcLFxu5MU/G8QJpWSycdbe
oIkxOkPsu3fRsAicDLgiGrnlQ+KoJ4wDIcsM0Pequw5d6gLd+4zUPeZHqlIv7N9e
r12RJkPEpp3m82pKEezQn6/5r1XFq6pxS6MlfryZ8Q+0tZboZYc=
=JMK6
-----END PGP SIGNATURE-----

--Apple-Mail=_FF7A8F49-22A2-4052-8E15-9F0CBE2C7B33--