From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from fraxinus.osuosl.org (smtp4.osuosl.org [140.211.166.137]) by lists.linuxfoundation.org (Postfix) with ESMTP id 40645C0881 for ; Tue, 24 Dec 2019 19:09:46 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by fraxinus.osuosl.org (Postfix) with ESMTP id 2F70084FF9 for ; Tue, 24 Dec 2019 19:09:46 +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 8opp4XRjWlqp for ; Tue, 24 Dec 2019 19:09:45 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-pl1-f170.google.com (mail-pl1-f170.google.com [209.85.214.170]) by fraxinus.osuosl.org (Postfix) with ESMTPS id 9286B848D5 for ; Tue, 24 Dec 2019 19:09:45 +0000 (UTC) Received: by mail-pl1-f170.google.com with SMTP id p27so8736257pli.10 for ; Tue, 24 Dec 2019 11:09:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=+1ePefsPaq+tbN1HBwXML9TzHfkepkEnSMXPgeIHVSQ=; b=Xeuzdo+J+UxEF1hUpp4LHIYQL7kB1am7XtBvZNYc7+AvSOOhFxWuBchBD49Clo4FpJ 6r0xS2Br1r12jFpVXrqzcikTx0mxHoZdgVkcibPPLqtohW6xpC8mTVV6QeoQx5nk1ZiP tjPPggLpWeCfIrbnQoej+vLdskkLXrw50eNR3IRx2csM6rySazUf0wq7Rd34RNS8ERdQ Oej2Vl3cxI2sn6glO2XdfKbXYB0bC8KbDYq8gKZtTw2zcj9AbKwySMN4sQO4vKrpX3+I T0sJ6bfKzz6KNt6O9LA+LvLnqKPrdDPEdN9eg7Ds0xTlG5M3e8ic+3pc0WfO4aMZAvap oFOw== 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=+1ePefsPaq+tbN1HBwXML9TzHfkepkEnSMXPgeIHVSQ=; b=UxJDAMmXjaSEbIQdDJX7RMKxXfh8rhTIAy5eZpJ+cBVbCtA6eCRNrnhKFkt2q0l5ZR pWwLRN705njMpBSmwVMOBZThhdjP+U7fGxggitHwA9UWfqN8Xrk6/g6o+hxpPtMYtCkN 9XK/MSSLm20zhltU7GrS+U1ggJlLX0pL0uhaPokdMnDnaIazQyp+cM6QyPizDwyBqD/h 0NwdclCHhiUHzTBs6CJ8+BP9XDZrqQVKCvvcj4ahGEEDOZp3WvX/NK2oH+hFHuEHxgP2 GRKX1PHXDPlDGOPni7PgiwkrBIC9nHbZitRnUQBu6oshDCVPuzEcmvNxUx+bi1Viiuix 6frQ== X-Gm-Message-State: APjAAAUNzNzoBrQ+I4Nd+1DDMoQcLwKaUC+eIC6042q8lm+Kp1M1P9WV EsdeGrPLLXlK4ZD0m8PleY0Fhqd+idGCzQ7+4Q0= X-Google-Smtp-Source: APXvYqzP4+yskM3b3l9UooLvdPOlQ0EdzF0GcRHyY59xE2i6lanbKZI2Dv0hjJUT9O3txJwTJDOwFVjpTBmstOybF0s= X-Received: by 2002:a17:902:8d95:: with SMTP id v21mr37276227plo.61.1577214585142; Tue, 24 Dec 2019 11:09:45 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: "Spencer Dupre`" Date: Tue, 24 Dec 2019 14:09:33 -0500 Message-ID: To: Chris Belcher , Bitcoin Protocol Discussion Content-Type: multipart/alternative; boundary="000000000000150459059a77e3ec" X-Mailman-Approved-At: Tue, 24 Dec 2019 23:55:47 +0000 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Dec 2019 19:09:46 -0000 --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
Sounds like a good UX improvement, but do we really need = to introduce a new encoding? Perhaps bech32 could be used instead.
On Tue, D= ec 24, 2019, 12:07 PM Chris Belcher via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org= > wrote:
I've recently b= een 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 acho= w101.
_______________________________________________
bitcoin-dev mailing list
bitcoin-dev@lists.linuxfoundation.org
https://lists.linuxfoundati= on.org/mailman/listinfo/bitcoin-dev
--000000000000150459059a77e3ec--