Gotcha. As I mention in my post, the situation is that you are editing your profile, for example in a Nostr client. You want to be able to accept payments (maybe you're an artist and post music to Wavlake). Your bitcoin wallet (Phoenix, for example) gives you an address that you copy and paste in. Now we have ~10 different types of addresses across bitcoin and lightning, suited for different use cases. Wallets support different combinations of those, so we need some good UI patterns for telling users what is supported, and give them tips and validation so they can set things up correctly. It is about money after all, so it's important that users feel confident.
The mockup looks at a situation where a reusable lightning address (aka BOLT12 offer or Lightning offer) is the best address type to use. A email-like address (BIP353 Human Readable Address) is OK, but will be resolved to a reusable lightning address for better security & privacy, which we inform the user about so there are no surprises.
Big picture, I don't think anyone other than hardcore techies will recognize and understand the different address types. I am exploring whether we can just call everything a "bitcoin address". So instead of the label being "Enter a lightning offer", it is "Enter a bitcoin address". And then we provide 1-2 extra pointers below to point people in the right direction.
I'm doing lots of explorations like these and tend to share bits and snippets. There's often a lot of context that is not obvious from these short social media blurbs. So I totally get that it may not make sense. Thanks for being interested and asking.
GBKS / Christoph Ono
npub1ku…v0eyw
2024-10-16 05:40:41
in reply to nevent1q…3ea8
Author Public Key
npub1kuc70777tsvj67fl75s2dmy376t97hv05xmyuyshzzy6vhj5q5jstv0eywPublished at
2024-10-16 05:40:41Event JSON
{
"id": "3665eb8c0e1a84c1230a1d92fef9863ab39fe4796956e300767dd6d3ccb91acb",
"pubkey": "b731e7fbde5c192d793ff520a6ec91f6965f5d8fa1b64e12171089a65e540525",
"created_at": 1729057241,
"kind": 1,
"tags": [
[
"e",
"21ffa71c6b6d9fb6c0ab1a2ea085eb4f59ca4ff081577b136b4c071823927283",
"",
"root"
],
[
"e",
"70188e1820b0b1da60446910ed6d60be61d9daba54d8363054579c0d9f36402c",
"",
"reply"
],
[
"p",
"b731e7fbde5c192d793ff520a6ec91f6965f5d8fa1b64e12171089a65e540525"
],
[
"p",
"fea186c2a4678dbc437704eed2160846e8a781e5fb17056e9bb333840d5bdef2"
]
],
"content": "Gotcha. As I mention in my post, the situation is that you are editing your profile, for example in a Nostr client. You want to be able to accept payments (maybe you're an artist and post music to Wavlake). Your bitcoin wallet (Phoenix, for example) gives you an address that you copy and paste in. Now we have ~10 different types of addresses across bitcoin and lightning, suited for different use cases. Wallets support different combinations of those, so we need some good UI patterns for telling users what is supported, and give them tips and validation so they can set things up correctly. It is about money after all, so it's important that users feel confident.\n\nThe mockup looks at a situation where a reusable lightning address (aka BOLT12 offer or Lightning offer) is the best address type to use. A email-like address (BIP353 Human Readable Address) is OK, but will be resolved to a reusable lightning address for better security \u0026 privacy, which we inform the user about so there are no surprises.\n\nBig picture, I don't think anyone other than hardcore techies will recognize and understand the different address types. I am exploring whether we can just call everything a \"bitcoin address\". So instead of the label being \"Enter a lightning offer\", it is \"Enter a bitcoin address\". And then we provide 1-2 extra pointers below to point people in the right direction.\n\nI'm doing lots of explorations like these and tend to share bits and snippets. There's often a lot of context that is not obvious from these short social media blurbs. So I totally get that it may not make sense. Thanks for being interested and asking.",
"sig": "61bd84fe9e6bb175b046f19abbdbb5bbf82749e671f86619b98fb6c7320ddc5fd6b75d52f226706df08fdc2ca1ac9c032a930e77634583fa9008058fb0e0ecd5"
}