Just published a Block Engineering blog post titled “Trust in Nostr NIP-05 Identifiers”. Check it out!
https://engineering.block.xyz/blog/trust-in-nostr-nip-05-identifiers
Discussion
If Block and Cash App had vanity addresses, it would make the verification even more robust.
I also think it would be silly for the Cash App to have a lightning address that's not at a cash app URL, but that's somewhat because I want every user on the Cash App to have a lightning address.
NIP05 "affiliation" is an underrated NIP.
I love NIP-05!
You’re right that identification is not verification. But each NIP-05 domain owner can decide what they want to do before linking an npub to a domain address. And that linking could include a verification step. It’s up to the domain owner to decide their linking policies and other to decide how much to trust.
Top 🤝😍
Great article!
One thing I have found quite limiting about NIP-05 is that it only allows you to have one "association" at a time. I have dikaios1517@nostrplebs.com. I proudly keep it, because I have been with them since just after the service went live. Yet... I have a lot of other groups I am associated with, that I must forego them being able to confirm that association if I want to stay with nostrplebs.
I don't see any reason why this must be the case. If I want to continue to rep nostrplebs, but also have my church's domain confirm that my npub is associated with my church, or my employer's domain confirm that my npub is associated with them, or Sovereign Craft confirm my npub is the same Dikaios1517 they see on the server there, all of them should be able to do so, without having to trade one out for the other in my kind 0.
Maybe there should be a primary NIP-05, and then a comma separated field in the kind 0 with alternative NIP-05s that also point to your npub for those other associations?
And/or some way to tie multiple npubs together? I have multiple and would like to have some way of showing that they’re owned or controlled by “me” / my primary npub.
I don’t think it’s a bad idea to have more than one NIP-05 on the profile. That happens in practice quite often. I don’t know if it should be on kind 0 — it’s abused quite heavily by developers adding whatever they want on it. Maybe it should be a new kind.
Right? I have a few NIP-05s I COULD switch to at any time. But I can only be looked up by one of them at a time? Seems clients should be able to request from the domain whether I have that particular NIP-05 "active" or not, and it should still return my npub.
The aspect of me confirming, by signing a Nostr event, that I am in fact associated with that domain is important, though. So maybe a list kind of some sort?
Something like this? I added an alias field to the nostr.json response
{ "names": { "trbouma": "df82f7b15bdae5815a25e12ae8a26c50eac1ee47f524776c6ae80805ce8271f4" }, "aliases": [ "trbouma@openproof.org" ], "relays": { "df82f7b15bdae5815a25e12ae8a26c50eac1ee47f524776c6ae80805ce8271f4": [ "wss://relay.getsafebox.app" ] } }
What is the origin of this response?
Say a friend of mine from church is wanting to find me on Nostr. They search for dikaios1517@[churchdomain]. Is this the response that would be sent from the domain to my nostr client saying, "Here's his npub. He's also known as dikaios1517@nostrplebs.com" so the client can then display the proper profile to my friend?
Love that Block is bringing the world of Nostr to the masses.
Sounds great
Nostr addresses are easy identification service that any company or organization of any size should implement for their employees that wish to have a public presence on Nostr. I'm here for it.
Sigh OK I'll fix my nip05