From: Pavol Rusnak <stick@satoshilabs•com>
To: Chris Belcher <belcher@riseup•net>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Base64-encoded descriptors
Date: Tue, 24 Dec 2019 20:25:02 +0100 [thread overview]
Message-ID: <CAF90AvkHKck8cd3hX6TbP0Bq1czoUv_N56bYf3ViVFncOOG8Sg@mail.gmail.com> (raw)
In-Reply-To: <deb1cedd-ae7d-4ef2-6b89-104183b919b4@riseup.net>
[-- Attachment #1: Type: text/plain, Size: 1449 bytes --]
I'd rather see something using Base58 or even better Bech32. Base64 is not
URL/QR code friendly.
On Tue, Dec 24, 2019, 18:06 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
>
[-- Attachment #2: Type: text/html, Size: 2038 bytes --]
next prev parent reply other threads:[~2019-12-24 19:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-24 17:06 Chris Belcher
2019-12-24 19:09 ` Spencer Dupre`
2019-12-25 1:02 ` Trey Del Bonis
2019-12-24 19:25 ` Pavol Rusnak [this message]
2019-12-25 17:17 ` William Casarin
2019-12-26 5:18 ` Andrew Chow
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAF90AvkHKck8cd3hX6TbP0Bq1czoUv_N56bYf3ViVFncOOG8Sg@mail.gmail.com \
--to=stick@satoshilabs$(echo .)com \
--cc=belcher@riseup$(echo .)net \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox