> when you point to a NIP 05 domain in your profile, don't you have to sign that

Yea, not clear what this solves... if the nip 05 response at the domain matches the pub that signed the kind 0 then there's nothing more to prove

Only problem I see with nip05 is clients probably need to detect if their nip05 has been rugpulled by the domain so they can update their kind 0

justin_shocknet

> when you point to a NIP 05 domain in your profile, don't you have to sign that?

Yeah. I can't really figure why this is necessary either.

k00b

 is a specification for uploading a little json referencing an npub to a .well-known folder of a domain and then referring to it from your nostr profile.

It demonstrates that the npub has the ability to upload a file at that domain.

For instance, jb55's npub shows that he is nip-05 verified at jb55.com and here is what you get if you go to 

https://jb55.com/.well-known/nostr.json

You can see that the npub that claims to be jb55 apparently was able to get their npub posted at at 

VIP creates a cryptographically verifiable link between a domain-based NIP-05 identifier (like 

) and a Nostr public key through a challenge/response handshake.

I'm not sure I understand why this is useful though: when you point to a NIP 05 domain in your profile, don't you have to sign that? If so, isn't this already a cryptographic link between the NIP 05 identifier? I must be missing something.

nostr

[NIP 05](https://github.com/nostr-protocol/nips/blob/master/05.md) is a specification for uploading a little json referencing an npub to a .well-known folder of a domain and then referring to it from your nostr profile.

It demonstrates that the npub has the ability to upload a file at that domain. 

For instance, jb55's npub shows that he is nip-05 verified at jb55.com and here is what you get if you go to https://jb55.com/.well-known/nostr.json

![](https://m.stacker.news/122829)

You can see that the npub that claims to be jb55 apparently was able to get their npub posted at at https://jb55.com/.well-known/nostr.json

So what does NIP-VIP do?

> VIP creates a cryptographically verifiable link between a domain-based NIP-05 identifier (like alice@example.com) and a Nostr public key through a challenge/response handshake.

I'm not sure I understand why this is useful though: when you point to a NIP 05 domain in your profile, don't you have to sign that? If so, isn't this already a cryptographic link between the NIP 05 identifier? I must be missing something.