From 2e2ed85d49cc8f71865c6938697724b9d4a143b3 Mon Sep 17 00:00:00 2001
From: fiatjaf <fiatjaf@gmail.com>
Date: Sun, 21 Jun 2026 20:44:06 -0300
Subject: [PATCH] nip05 of things.

---
 05.md | 19 +++++++++++++++++++
 1 file changed, 19 insertions(+)

diff --git a/05.md b/05.md
index 2694ce61..ccaadbb4 100644
--- a/05.md
+++ b/05.md
@@ -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"]
+  }
+}
+```