š
Original date posted:2019-12-25
š Original message:Hey Chris,
Chris Belcher via bitcoin-dev <bitcoin-dev at lists.linuxfoundation.org> writes:
> 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.
I don't think encoding descriptors is a good idea. Encoding makes more
sense if it's non-human-readable binary data that you want transfer over
a plaintext channel.
Descriptors aren't binary data, and have a wealth of useful information
that you can view at a glance. Obfuscating this information just to gain
the ability to copy-paste doesn't seem like a good idea.
> I didn't come up with these ideas, they came from discussions with achow101.
I suggested base58 or base62 +hrp for PSBT in id:87zhzlbfq5.fsf at jb55.com
[1] for the reasons that you mentioned, so I'm a bit sad that base64 was
chosen. base64 isn't really good for double-click copy-pasting, it
contains characters such as +/= which aren't always included when
double-clicking. I prefer bech32, base58 or base62. In this case,
encoding of any kind doesn't make much sense IMO.
Cheers,
Will
[1] https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2018-June/016151.html
--
https://jb55.com
William Casarin [ARCHIVE] /
npub1d7ā¦93exj
2023-06-07 18:22:06
in reply to nevent1qā¦0fjr
Author Public Key
npub1d7e068ud72v0au6xf53qvek44eccfhlgnhzuclf6za6hnxrvx89sc93exjPublished at
2023-06-07 18:22:06Event JSON
{
"id": "33886c60baf39f03640322b4b18e71eb49a2071a49b3249cb98e66fcf8bbbabd",
"pubkey": "6fb2fd1f8df298fef3464d220666d5ae7184dfe89dc5cc7d3a177579986c31cb",
"created_at": 1686162126,
"kind": 1,
"tags": [
[
"e",
"8bbdf831a89ba0a55bf3e37d63be3e6c3f6d586728dc217a1365a527f149e0ff",
"",
"root"
],
[
"e",
"478e8dcb59ea3f099b2099693d900f868b91798f4ae88458eae437558f9e7aa9",
"",
"reply"
],
[
"p",
"7631397e469f47f3535567311f5f7c17129e0ff2cb253df015e3d92ddfd92c63"
]
],
"content": "š
Original date posted:2019-12-25\nš Original message:Hey Chris,\n\nChris Belcher via bitcoin-dev \u003cbitcoin-dev at lists.linuxfoundation.org\u003e writes:\n\u003e I've recently been playing around with descriptors, and they are very\n\u003e nice to work with. They should become the standard for master public\n\u003e keys IMO.\n\u003e\n\u003e One downside is that users cant easily copypaste them to-and-fro to make\n\u003e watch-only wallet. The descriptors contain parenthesis and commas which\n\u003e stop highlighting by double-clicking. Also the syntax might look scary\n\u003e to newbs.\n\u003e\n\u003e An obvious solution is to base64 encode the descriptors. Then users\n\u003e would get a text blog as the master public key without any extra details\n\u003e to bother them, and developers can easily base64 decode for developing\n\u003e with them.\n\nI don't think encoding descriptors is a good idea. Encoding makes more\nsense if it's non-human-readable binary data that you want transfer over\na plaintext channel.\n\nDescriptors aren't binary data, and have a wealth of useful information\nthat you can view at a glance. Obfuscating this information just to gain\nthe ability to copy-paste doesn't seem like a good idea.\n\n\u003e I didn't come up with these ideas, they came from discussions with achow101.\n\nI suggested base58 or base62 +hrp for PSBT in id:87zhzlbfq5.fsf at jb55.com\n[1] for the reasons that you mentioned, so I'm a bit sad that base64 was\nchosen. base64 isn't really good for double-click copy-pasting, it\ncontains characters such as +/= which aren't always included when\ndouble-clicking. I prefer bech32, base58 or base62. In this case,\nencoding of any kind doesn't make much sense IMO.\n\nCheers,\nWill\n\n[1] https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2018-June/016151.html\n\n\n-- \nhttps://jb55.com",
"sig": "98b06a1ba12d29f8bc5de0ae137680ea4b06e8d8bd9c0b25f28f526f9111c21ed399e125c44c7730c317de3636419762bbaa24e71d6978c55c059f55003345fa"
}