1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
|
Return-Path: <stick@satoshilabs.com>
Received: from fraxinus.osuosl.org (smtp4.osuosl.org [140.211.166.137])
by lists.linuxfoundation.org (Postfix) with ESMTP id B4FE6C0881
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 24 Dec 2019 19:32:18 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by fraxinus.osuosl.org (Postfix) with ESMTP id 9C032847E5
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 24 Dec 2019 19:32:18 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
Received: from fraxinus.osuosl.org ([127.0.0.1])
by localhost (.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id qjoLBc5BTPMe
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 24 Dec 2019 19:32:17 +0000 (UTC)
X-Greylist: delayed 00:07:03 by SQLgrey-1.7.6
Received: from mail-ot1-f49.google.com (mail-ot1-f49.google.com
[209.85.210.49])
by fraxinus.osuosl.org (Postfix) with ESMTPS id C49FF847DE
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 24 Dec 2019 19:32:17 +0000 (UTC)
Received: by mail-ot1-f49.google.com with SMTP id a15so27308739otf.1
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 24 Dec 2019 11:32:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=satoshilabs.com; s=google;
h=mime-version:references:in-reply-to:from:date:message-id:subject:to;
bh=UHQokLdfOTbT5qbeiU2kJPPS7Lk3cZe+R8tCXZoI1Qs=;
b=XBtm1tZVbhM5+A4zX0/KUtqYsGzwrW9QrHb7bqp0GPSzjYYAoSk/xd6H2ZtIy/YJoV
5ez5mrCO8dx3hvyWzbQogQtmTqyM162LwJQOWS9T+XxpFNfmHE1XGjlWWkCJaRY2t+NK
8qCtgMTsbDo5EEzVGGdK20tqb09g29a+zi5ULVLt+LE7RX4dH71MIjW12k2d/AGeIHR2
0iz46l16VrFBHG/iGudU5gvA2E6eRjCEFG0T9tXqRxN7AL2uw+N5fWFKCQ1b81Ey47ja
yzf2YOXLGMgarMs12wLiix9O7x8xW9e2czfJRGBXwtw4EPyLs8ideuMQRQJunj4O3RB0
qYQA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:mime-version:references:in-reply-to:from:date
:message-id:subject:to;
bh=UHQokLdfOTbT5qbeiU2kJPPS7Lk3cZe+R8tCXZoI1Qs=;
b=rSDU+ogRC/u1/pfRJ3UPQaOKEI7xqbhAibq2LS1KSG0TE/ygiPiA5dEp+k4iY4zlG5
+LrKOktWU5EaMFYsZEiOm7hlLG0QmCASrzX64plpx/sRm1Tz1GoONuFq6LhegQ8QU6kL
jVBgCtbSbtmA8e/CUovz2/5CT5UpweLRhGymuv9BSegK/456jptWtMzxoZoobLfwQDpC
rGi/pc7JPuIinM3dtYy6Ks1pLojmcFtZpO5noQC8t9/tpSCkhzFZo9K+We+ydLSYzOV7
Vzg/0reqdQ1lV6NcydIZA54oyFJy8K78xbTR+i+SJzbixidTqa2bqAvbAV+ErC9SB/ly
yfbg==
X-Gm-Message-State: APjAAAUTy4z8UYhhqyxOPm5W1KXm66hXrEdqnA5JjQwbOp2A38wNEik4
HO5wKaVEHyDQ8UGLE2zIndOl4abdpd5ooyI/2avQRA==
X-Google-Smtp-Source: APXvYqzd1aBJnYV+liSnSliOmzsHEMKVsyenYWfGrWJZJ4FxzPlf8Qn8V3e2Jc8jnaCEzEJ3LLzaveXugsQw/RJVqGo=
X-Received: by 2002:a05:6830:155a:: with SMTP id
l26mr41090006otp.339.1577215514094;
Tue, 24 Dec 2019 11:25:14 -0800 (PST)
MIME-Version: 1.0
References: <deb1cedd-ae7d-4ef2-6b89-104183b919b4@riseup.net>
In-Reply-To: <deb1cedd-ae7d-4ef2-6b89-104183b919b4@riseup.net>
From: Pavol Rusnak <stick@satoshilabs.com>
Date: Tue, 24 Dec 2019 20:25:02 +0100
Message-ID: <CAF90AvkHKck8cd3hX6TbP0Bq1czoUv_N56bYf3ViVFncOOG8Sg@mail.gmail.com>
To: Chris Belcher <belcher@riseup.net>,
Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="00000000000073be82059a781aa3"
Subject: Re: [bitcoin-dev] Base64-encoded descriptors
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Dec 2019 19:32:19 -0000
--00000000000073be82059a781aa3
Content-Type: text/plain; charset="UTF-8"
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
>
--00000000000073be82059a781aa3
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"auto">I'd rather see something using Base58 or even better =
Bech32. Base64 is not URL/QR code friendly.</div><br><div class=3D"gmail_qu=
ote"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, Dec 24, 2019, 18:06 Chri=
s Belcher via bitcoin-dev <<a href=3D"mailto:bitcoin-dev@lists.linuxfoun=
dation.org">bitcoin-dev@lists.linuxfoundation.org</a>> wrote:<br></div><=
blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px=
#ccc solid;padding-left:1ex">I've recently been playing around with de=
scriptors, 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'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'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>
--00000000000073be82059a781aa3--
|
