From d346df0840d206ef6000fd13f51549ba7c5aaa22 Mon Sep 17 00:00:00 2001
From: fiatjaf <fiatjaf@gmail.com>
Date: Fri, 9 Aug 2024 08:40:57 -0300
Subject: [PATCH] NIP-74: addressable chat.

---
 74.md | 29 +++++++++++++++++++++++++++++
 1 file changed, 29 insertions(+)
 create mode 100644 74.md

diff --git a/74.md b/74.md
new file mode 100644
index 00000000..c6e8d572
--- /dev/null
+++ b/74.md
@@ -0,0 +1,29 @@
+NIP-74
+======
+
+Addressable Chat
+----------------
+
+`draft` `optional`
+
+Every time an addressable event (kinds 30000-39999) contains a `"relays"` tag with any number of relay URLs specified in it (`["relays", "wss://myrelay.com", "wss://addressable.chat"]`) clients have the option of toggling a chat box about the topic of that event.
+
+Chat messages are expected to be read and published from and to the specified relays, which will _somehow_ provide moderation and consistency.
+
+(Clients can also use different relays other than those specified by the addressable event author, but this would be a power/optional/manual feature until other means of signaling this are invented.)
+
+### Chat Message
+
+Chat messages must have `kind:1311`. Clients MUST include the `a` tag of the activity with a `root` marker. Other Kind-1 tags such as `reply` and `mention` can also be used. An `e` tag containing the specific ID of the current addressable event version being replied to SHOULD also be included.
+
+```json
+{
+  "kind": 1311,
+  "tags": [
+    ["a", "<addressable-event-kind>:<addressable-author-pubkey>:<d-identifier>", "<optional relay url>", "root"],
+    ["e", "<addressable-event-id>", "<optional relay url>", "root"]
+  ],
+  "content": "hello fans of this article",
+  ...
+}
+```