laantungir/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2026-08-09 07:44:51 +00:00
Code Issues Packages Projects Releases Wiki Activity

nip05 of things.

Browse Source
This commit is contained in:
fiatjaf
2026-06-21 20:44:15 -03:00
parent 3dc9705a4f
commit 2e2ed85d49
1 changed files with 19 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
05.md
+19
View File
@@ -101,3 +101,22 @@ Users should ensure that their `/.well-known/nostr.json` is served with the HTTP
The `/.well-known/nostr.json` endpoint MUST NOT return any HTTP redirects.
Fetchers MUST ignore any HTTP redirects given by the `/.well-known/nostr.json` endpoint.
## NIP-05 for Events
The world is messy, and some people like DNS as a pointer to things, so we can also use these DNS-based internet identifiers to point to events such as [NIP-29 groups](29.md) or [NIP-5A nsites](5A.md), among other use cases.
When using NIP-05 to point to events, we introduce a `"events"` field in the `/.well-known/nostr.json` object, for example:
```json
{
"events": {
"golf-appreciators": "<kind-39000-hex-event-id-for-the-golf-group>",
"homepage": "<kind-35128-hex-event-id-for-the-nsite>"
},
"relays": {
"<kind-39000-hex-event-id-for-the-golf-group>": ["wss://groups.relay.com"],
"<kind-35128-hex-event-id-for-the-nsite>": ["wss://somerelay.com", "wss://someotherrelay.com"]
}
}
```