<oembed><type>rich</type><version>1.0</version><title>Jonas Schnelli [ARCHIVE] wrote</title><author_name>Jonas Schnelli [ARCHIVE] (npub1nf…3dtxs)</author_name><author_url>https://yabu.me/npub1nfrrurat393mqymf3s26pujyn5vujlem3pzcukr5p9d4qpklngxq43dtxs</author_url><provider_name>njump</provider_name><provider_url>https://yabu.me</provider_url><html>📅 Original date posted:2018-06-25&#xA;📝 Original message:Hi&#xA;&gt; As was partially brought up by William, shouldn&#39;t we consider using&#xA;&gt; bech32? It doesn&#39;t break on double-click and it is a dependency for&#xA;&gt; native Segwit addresses anyway, so wallets might already support it or&#xA;&gt; they will at some point. But we should probably run some numbers on this&#xA;&gt; first, since bech32 will obviously be larger than base64.&#xA;I don’t think bech32 is a fit here.&#xA;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.&#xA;&#xA;/jonas&#xA;-------------- next part --------------&#xA;An HTML attachment was scrubbed...&#xA;URL: &lt;http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20180625/88470c4c/attachment.html&gt;&#xA;-------------- next part --------------&#xA;A non-text attachment was scrubbed...&#xA;Name: signature.asc&#xA;Type: application/pgp-signature&#xA;Size: 833 bytes&#xA;Desc: Message signed with OpenPGP&#xA;URL: &lt;http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20180625/88470c4c/attachment.sig&gt;</html></oembed>