Support Sats Names to make lighting address easier to recognize, easier to read, easier to remember

[OliverThompsonOT]

If you don't know what is Sats Names, you can read this doc:
https://docs.sats.id/sats-names/about

Sats Names is a standard for writing names to Bitcoin using ordinals. The goal is to build a name ecosystem for Bitcoin, that is built by Bitcoiners, and developed entirely on Bitcoin.

it can make lighting address easier to recognize, easier to read, easier to remember, and most important, it's decentralized.

• All namestate lives on Bitcoin
• The protocol will remain credibly neutral
• Names are inscribed as ordinals, and the only fees involved are paid to miners on the Bitcoin network.

FAQs: https://docs.sats.id/sats-names/faqs

Why we need this?

• easier to recognize, easier to read, easier to remember, and most important, it's decentralized

I'm not an engineer, but perhaps you can discuss with the author of Sats how to implement this. https://twitter.com/satsnames

My idea is as follows:

for instance, an address that owns bitcoin.sats could mint an inscription declaring that the Lightning Network address/invoice corresponding to that bitcoin.sats is ****.
Afterwards, when transferring to this bitcoin.sats via the Lightning Network, one could send to the Lightning Network receiving address corresponding to this bitcoin.sats

[saubyk]

Unclear on what this has to do with the bolt specification? Seems like an issue you should raise with the team which created the lightning address standard.

[OliverThompsonOT]

Unclear on what this has to do with the bolt specification? Seems like an issue you should raise with the team who created the lightning address standard.

how to find them?

[OliverThompsonOT]

Unclear on what this has to do with the bolt specification? Seems like an issue you should raise with the team who created the lightning address standard.

I am unsure of whom I should seek.

As for the Bitcoin and Lightning addresses, I propose that we devise an address format that is not only easier to recognize, read, and remember, but also importantly, decentralized.

[dpad85]

I am unsure of whom I should seek.

See https://github.com/lnurl/luds/blob/luds/16.md - as well as https://github.com/andrerfneves/lightning-address.

[TheBlueMatt]

This isn't an actionable proposal. If you want to contribute a new way of describing payment info, it should come in the form of a PR here or to the bLIPs repo (if applicable).