Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
OliverThompsonOT opened this issue May 26, 2023 · 4 comments

Comments

@OliverThompsonOT
Copy link

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
  • It seems that some Lightning Network wallets are currently using email as an address scheme, but this solution is not decentralized, it's not neutral enough

How to

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

@michaelWuensch
Copy link
Contributor

I doubt they will be easier to remember.
Right now there could be [email protected] or [email protected], etc.
But if I get it right with sats names, there can only be one oliver.sats.
If lots of people use this everyone would have to come up with a crazy name, as all nice and easy ones are already gone.
xx0l1ver1984.sats doesn't feel like easier to read or remember.

@OliverThompsonOT
Copy link
Author

I doubt they will be easier to remember. Right now there could be [email protected] or [email protected], etc. But if I get it right with sats names, there can only be one oliver.sats. If lots of people use this everyone would have to come up with a crazy name, as all nice and easy ones are already gone. xx0l1ver1984.sats doesn't feel like easier to read or remember.

  • there are lots of names, anyone cannot mint them all. such as 20230128, this is my birthday, it's a good name, it's easy to remember. also, like jack700, such as this.
  • [email protected] or [email protected] this kind of names is not decentralized, decentralized is the most important thing in our community.

@OliverThompsonOT
Copy link
Author

I doubt they will be easier to remember. Right now there could be [email protected] or [email protected], etc. But if I get it right with sats names, there can only be one oliver.sats. If lots of people use this everyone would have to come up with a crazy name, as all nice and easy ones are already gone. xx0l1ver1984.sats doesn't feel like easier to read or remember.

actually, you can not mint all of the good names.
let us think about our bank account number, They are all 16-digit numbers, and there are 10^16 combinations.
if we just use 9-digit numbers, which is better than bank account number, there are 10^9 combinations, which allow lots of people use.
also, you can mint digit plus letter.
such as moon8923.sats, is also a readable name, better than [email protected] or [email protected]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants
@michaelWuensch @OliverThompsonOT and others