š
Original date posted:2019-12-24
š Original message: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 at 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 at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20191224/4255cd9f/attachment.html>;
Spencer Dupre` [ARCHIVE] /
npub1t3ā¦m4gum
2023-06-07 18:22:05
in reply to nevent1qā¦8u3a
Author Public Key
npub1t3mppu9wsk3gjq0tmx3t2evpvh5mshdm97t5wlcsa4n3r5j5hvnqum4gumPublished at
2023-06-07 18:22:05Event JSON
{
"id": "db18fbd6c01b922e711f04c1615da6fb39ca1fd987535074a17ed4c9ccda2c40",
"pubkey": "5c7610f0ae85a28901ebd9a2b5658165e9b85dbb2f97477f10ed6711d254bb26",
"created_at": 1686162125,
"kind": 1,
"tags": [
[
"e",
"8bbdf831a89ba0a55bf3e37d63be3e6c3f6d586728dc217a1365a527f149e0ff",
"",
"root"
],
[
"e",
"b38cae34de657af410d325d9388f4e168c263ceed4c8a402f19061c0c79fe292",
"",
"reply"
],
[
"p",
"cd99305dce8f7a8772455d28d44a8451787c19b2ffd2c8b1010acecc3c5f95c7"
]
],
"content": "š
Original date posted:2019-12-24\nš Original message:Sounds like a good UX improvement, but do we really need to introduce a new\nencoding? Perhaps bech32 could be used instead.\n\nOn Tue, Dec 24, 2019, 12:07 PM Chris Belcher via bitcoin-dev \u003c\nbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\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\u003e\n\u003e A complication might be the descriptor checksum. If there's a typo in\n\u003e the base64 text then that could decode into multiple character errors in\n\u003e the descriptor, which might be problematic for the checksum. Maybe the\n\u003e descriptor could be base64 encoded without the checksum, then attach the\n\u003e checksum to the end of the base64 text.\n\u003e\n\u003e Thoughts?\n\u003e\n\u003e I didn't come up with these ideas, they came from discussions with\n\u003e achow101.\n\u003e _______________________________________________\n\u003e bitcoin-dev mailing list\n\u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20191224/4255cd9f/attachment.html\u003e",
"sig": "c0ecb4d57ff9625f3b2fdcd2b7251313e6ebd373aecda2ef4cfaf5fd266cb4844bf654777695e12ca69bef196d1beb1e8e9aff4d94dd7599da5568cc35b86fd3"
}