Expirement using private kind range

43.md

@@ -40,20 +40,19 @@ when sending new DMs.
 
 ## Chat Session
 
-The "Chat Session Envelope" is a [NIP-59](59.md) gift wrap event but with a specific kind: `1043`.
+The "Chat Session Envelope" is a regular [NIP-59](59.md) gift wrap event but with a specific kind: `40043`.
 
 The NIP-44 encryption when wrapping use the random author's privkey and the recipient's pubkey to generate the conversation key (CK).
 When sealing the encryption uses the main sender's privkey and the recipient's pubkey.
 Both encryptions use the default salt to generate the CK.
 
 It MAY include [NIP-13](13.md) PoW.
 Relays MAY block it if below a PoW difficulty such as if less than 16.
-Relays MAY require increasing PoW difficulty the more `kind:1043` events are sent to the same pubkey in a short time.
+Relays MAY require increasing PoW difficulty the more `kind:40043` events are sent to the same pubkey in a short time.
 Relays SHOULD block it if of byte size higher than 3KB.
-Relays SHOULD limit the rate at which `kind:1043` events are published with the same `p` tag per client IP.
+Relays SHOULD limit the rate at which `kind:40043` events are published with the same `p` tag per client IP.
 
-It has a `p` tag set to the recipient's pubkey.
-Relays SHOULD require users to [NIP-42](42.md) `AUTH` as the `p` tagged pubkey when requesting the event.
+It has a [NIP-42](42.md) `A` tag and a `p` tag both set to the recipient's pubkey.
 
 The NIP-59 rumor is a `kind:1044` "Chat Session Request" event.
 It's `.content` is the session's privkey.
@@ -66,11 +65,13 @@ Event example:
 
 ```js
 {
-  "kind": 1043,
+  "kind": 40043,
   "pubkey": "<random-pubkey>",
   "tags": [
+    ["d", "<random>"],
+    ["A", "<pubkey-B>"],
     ["p", "<pubkey-B>"],
-    ["nonce", "65962", "16"] // atleast 16 PoW difficulty
+    ["nonce", "65962", "16"]
   ],
   "content": "<nip44EncryptV2(JSON.stringify({
     "kind": 13, // seal
@@ -95,7 +96,7 @@ Event example:
 
 ## Chat Session List
 
-The [NIP-51](51.md) `kind:10043` is the user's "Chat Session List" event.
+The replaceable [NIP-51](51.md) `kind:40143` is the user's "Chat Session List" event.
 
 It encrypts `s` (session) tags using the author's own keypair with default salt
 as arguments to generate the NIP-44 conversation key.
@@ -109,16 +110,20 @@ The 4th value if present is set to "1", meaning the other chat participant accep
 
 `s` tags of expired sessions should be kept to indicate active chats.
 
-Relays SHOULD require users to [NIP-42](42.md) `AUTH` as the event author when requesting the event.
+It has a NIP-42 `A` tag set to the event author's pubkey.
 
 The user should publish the event to all of their own NIP-65 `write` relays.
 
 Event example:
 
 ```js
 {
-  "kind": 10043,
-  "pubkey": "<pubkey-B>"
+  "kind": 40143,
+  "pubkey": "<pubkey-B>",
+  "tags: [
+    ["d", ""], // empty string
+    ["A", "<pubkey-B>"]
+  ]
   "content": "<nip44EncryptV2(JSON.stringify([
     ["s", "<pubkey-A>", "<session-privkey>", "1704525400", "1"],
     // other "s" tags