Return-Path: Received: from fraxinus.osuosl.org (smtp4.osuosl.org [140.211.166.137]) by lists.linuxfoundation.org (Postfix) with ESMTP id B4FE6C0881 for ; 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 ; 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 ; 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 ; Tue, 24 Dec 2019 19:32:17 +0000 (UTC) Received: by mail-ot1-f49.google.com with SMTP id a15so27308739otf.1 for ; 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: In-Reply-To: From: Pavol Rusnak Date: Tue, 24 Dec 2019 20:25:02 +0100 Message-ID: To: Chris Belcher , Bitcoin Protocol Discussion 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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
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 Chri= s Belcher via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org> wrote:
<= 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
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
--00000000000073be82059a781aa3--