Chris Belcher [ARCHIVE] on Nostr: 📅 Original date posted:2019-12-24 📝 Original message:I've recently been playing ...
📅 Original date posted:2019-12-24
📝 Original message: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.
Published at
2023-06-07 18:22:05Event JSON
{
"id": "b38cae34de657af410d325d9388f4e168c263ceed4c8a402f19061c0c79fe292",
"pubkey": "cd99305dce8f7a8772455d28d44a8451787c19b2ffd2c8b1010acecc3c5f95c7",
"created_at": 1686162125,
"kind": 1,
"tags": [
[
"e",
"8bbdf831a89ba0a55bf3e37d63be3e6c3f6d586728dc217a1365a527f149e0ff",
"",
"reply"
],
[
"p",
"a23dbf6c6cc83e14cc3df4e56cc71845f611908084cfe620e83e40c06ccdd3d0"
]
],
"content": "📅 Original date posted:2019-12-24\n📝 Original message:I've recently been playing around with descriptors, and they are very\nnice to work with. They should become the standard for master public\nkeys IMO.\n\nOne downside is that users cant easily copypaste them to-and-fro to make\nwatch-only wallet. The descriptors contain parenthesis and commas which\nstop highlighting by double-clicking. Also the syntax might look scary\nto newbs.\n\nAn obvious solution is to base64 encode the descriptors. Then users\nwould get a text blog as the master public key without any extra details\nto bother them, and developers can easily base64 decode for developing\nwith them.\n\nA complication might be the descriptor checksum. If there's a typo in\nthe base64 text then that could decode into multiple character errors in\nthe descriptor, which might be problematic for the checksum. Maybe the\ndescriptor could be base64 encoded without the checksum, then attach the\nchecksum to the end of the base64 text.\n\nThoughts?\n\nI didn't come up with these ideas, they came from discussions with achow101.",
"sig": "274e2f00e62dd28b0e7a686f021a0ca7bab38b1ae4311eb894825048ce3ebd8e542ccf1826ba12982631517bab70b8e4a12ff0c6f3cbec7fee7d88ddec0b1d60"
}