Nostr Web Client

Nope, relays have domain names too.

It’s quite easy for a relay to pull some data out of a note that has a specific syntax and publish that data in .well-known as a NIP-05 identifier.

eg I add relay abc.xyz and publish a note that says.

Claim Stu@abc.xyz

Backup npub1a…

The relay abc.xyz then adds Stu@abc.xyz to its .well-known file and I now have NIP-05 completed without ever going outside nostr.

Then if my key is lost, I go to the backup pubkey (npub1a) and publish a note that reads…

Claim Stu@abc.xyz

Backup npub1b…

Stuff like this will become the norm.

Reply to this note

Please Login to reply.

Discussion

StackSats.IO 2y ago

Nostr.com.au was intended from the start to provide relay + NIP05. Seemed like an obvious idea to me.

I get some people don’t like being reliant on dns but it’s a good solution for nostr right now and should be adopted until better things can be built.

⚡️🌱🌙 2y ago

My post above still uses DNS.

Relays have domain names, I’m just suggesting a way of telling a domain your NIP-05 details via nostr notes and a relay event handler instead of via a web form.

Obviously web forms are used now, because that method already exists and is well known 🙃

But by the end of this year, I think we will see NIP-05 identifiers being set up entirely inside nostr, everything for submitting details to making payment.

StackSats.IO 2y ago

The paid relays already take your key to whitelist entry, adding to the nostr.json at the same time won’t be difficult.

Think it was Andre on Twitter who gave his ID as the email format recently - this becomes your nostr identity with NIP05 and your payment identity with Lightning, and should be a single identifier generally.

thewall 2y ago

Take a look at my nostr.json. I signed it with my lightning key. I think something like this is the future of NIP-05.

https://lnwall.space/.well-known/nostr.json

⚡️🌱🌙 2y ago

Yes, maybe could list multiple pubkeys, wallets and relays with a single identity, this would allow you to use a single identity with a pubkey/wallet on each device and no need to transfer keys from device to device whilst also having some resilience to losing any one device. The nick/identity should be sovereign.

Then if relays publish NIP-05 information on relay.domain/.well-known/nostr.json it makes identification native to nostr infrastructure and recorded in multiple locations as a consensus reference and not reliant on a single point of failure.

𝖋𝖎𝖆𝖙𝖉𝖊𝖓𝖎𝖊𝖗 (¯`◕‿◕´¯) 2y ago

What is stopping a scammer from stealing your identity and linking it to their npub?

thewall 2y ago

In my case I’ve signed it with my lightning node. The problem with online identity is that you need to peg it to something. Easy for me since I have a well known lightning node now. Others tweet their npub, but that requires an established twitter following. It’s a really hard problem.

⚡️🌱🌙 2y ago

Anyone can claim to be Elvis Presley.

The only way to avoid that is to set up NIP-05 as I have done. Using your real name and a real name DNS domain, with an SSL Certificate from a Certification Authority. This way you can port your real world ID to DNS and from DNS to a pubkey via NIP-05.

Lots of people here don’t like that though, and prefer the anonymity of a nym, that’s OK. But I think they run a much higher risk of impersonation because nyms are easier to steal, as they are created out of thin air.

It all depends on where you want to trace your sovereignty from, either from yourself or from a nym you created. There are pros and cons for each approach.

Sophia 2y ago

Elvis has left the building

HoloKat 2y ago

Aren’t there free ssls that don’t need your identity though

Carlos 2y ago

With certificates, you don't trace your sovereignity from yourself, but from the CA / cert issuer. Third party.

How would one know if elvispresley.com or elvispresley.net is the real one? Both can have valid certs from valid CAs (many, if not most, are compromised anyway).