MIME-Version: 1.0
References: <deb1cedd-ae7d-4ef2-6b89-104183b919b4@riseup.net>
In-Reply-To: <deb1cedd-ae7d-4ef2-6b89-104183b919b4@riseup.net>
From: "Spencer Dupre`" <spencer.dupre@gmail.com>
Date: Tue, 24 Dec 2019 14:09:33 -0500
Message-ID: <CAOB=H7qZ55XXncp9ovR8YpXwBwoVMO=WmbPS_aRxdqk0dFoEiQ@mail.gmail.com>
To: Chris Belcher <belcher@riseup.net>, 
 Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="000000000000150459059a77e3ec"
Subject: Re: [bitcoin-dev] Base64-encoded descriptors
Precedence: list

--000000000000150459059a77e3ec
Content-Type: text/plain; charset="UTF-8"

Sounds like a good UX improvement, but do we really need to introduce a new
encoding? Perhaps bech32 could be used instead.

On Tue, Dec 24, 2019, 12:07 PM Chris Belcher via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:

> I've recently been playing around with descriptors, and they are very
> nice to work with. They should become the standard for master public
> keys IMO.
>
> One downside is that users cant easily copypaste them to-and-fro to make
> watch-only wallet. The descriptors contain parenthesis and commas which
> stop highlighting by double-clicking. Also the syntax might look scary
> to newbs.
>
> An obvious solution is to base64 encode the descriptors. Then users
> would get a text blog as the master public key without any extra details
> to bother them, and developers can easily base64 decode for developing
> with them.
>
> A complication might be the descriptor checksum. If there's a typo in
> the base64 text then that could decode into multiple character errors in
> the descriptor, which might be problematic for the checksum. Maybe the
> descriptor could be base64 encoded without the checksum, then attach the
> checksum to the end of the base64 text.
>
> Thoughts?
>
> I didn't come up with these ideas, they came from discussions with
> achow101.
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>

--000000000000150459059a77e3ec
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">Sounds like a good UX improvement, but do we really need =
to introduce a new encoding? Perhaps bech32 could be used instead.</div><br=
><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, D=
ec 24, 2019, 12:07 PM Chris Belcher via bitcoin-dev &lt;<a href=3D"mailto:b=
itcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.linuxfoundation.org=
</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:=
0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I&#39;ve recently b=
een playing around with descriptors, and they are very<br>
nice to work with. They should become the standard for master public<br>
keys IMO.<br>
<br>
One downside is that users cant easily copypaste them to-and-fro to make<br=
>
watch-only wallet. The descriptors contain parenthesis and commas which<br>
stop highlighting by double-clicking. Also the syntax might look scary<br>
to newbs.<br>
<br>
An obvious solution is to base64 encode the descriptors. Then users<br>
would get a text blog as the master public key without any extra details<br=
>
to bother them, and developers can easily base64 decode for developing<br>
with them.<br>
<br>
A complication might be the descriptor checksum. If there&#39;s a typo in<b=
r>
the base64 text then that could decode into multiple character errors in<br=
>
the descriptor, which might be problematic for the checksum. Maybe the<br>
descriptor could be base64 encoded without the checksum, then attach the<br=
>
checksum to the end of the base64 text.<br>
<br>
Thoughts?<br>
<br>
I didn&#39;t come up with these ideas, they came from discussions with acho=
w101.<br>
_______________________________________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank" =
rel=3D"noreferrer">bitcoin-dev@lists.linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer noreferrer" target=3D"_blank">https://lists.linuxfoundati=
on.org/mailman/listinfo/bitcoin-dev</a><br>
</blockquote></div>

--000000000000150459059a77e3ec--