Relationship status

81.md

@@ -0,0 +1,73 @@
+NIP-81
+======
+
+Relationship Status
+-------------------
+
+`draft` `optional`
+
+This NIP defines two new event kinds (`30382` and `30383`) to document the relationship between two keys. 
+
+Both kinds offer public and private tags to describe that relationship. Private tags are JSON Stringified, [NIP-44](44.md)-encrypted to the signer's keys and placed inside the `.content` of the event. 
+
+### Public Relationship Status
+
+Event kind `30382` is used when the relationship itself is public, with the `d` tag receiving the public key each target key.
+
+```js
+{
+  "kind": 30382,
+  "tags": [
+    ["d", "e88a691e98d9987c964521dff60025f60700378a4879180dcbbb4a5027850411"],
+    ["n", "Follows"],
+    ["n", "Bitcoiners"],
+    ["n", "6064460175057025"]
+  ],
+  "content": nip44Encrypt(JSON.stringify([
+    ["petname", "NVK (Coldcard)"],
+    ["summary", "Owes me a beer"]
+  ])),
+  // ...other fields
+}
+```
+
+`petname` SHOULD be used instead of the person's display name in all interfaces.
+
+### Relationship Categories
+
+Optional `n` tags `["n", "<list code>"]` add the target key to unbound lists. This allows clients to query by `n` and download all members of a list. 
+
+List `codes` can be human readable or not. A new event kind named "Unbound List Names" (`kind:10008`) uses `map` tags to display the list name. Clients SHOULD display the `name` instead of the `code` if the `code` is present in this list.
+
+```js
+{
+  "kind": 10008,
+  "content": nip44Encrypt(JSON.stringify([
+    ["map", "<code>", "<name>"],
+    ["map", "Bitcoiners", "Bitcoiners"], 
+    ["map", "6064460175057025", "Debtors"]
+  ])),
+  // ...other fields
+}
+```
+
+### Private Relationship Status
+
+For relationships that MUST remain private, Event kind `30383` uses a similar structure but with a hashed `d` tag using [NIP-44](44.md)'s `hkdf` function. 
+
+```js
+{
+  "kind": 30383,
+  "tags": [
+    ["d", sha256(hkdf(private_key, salt: 'nip81') || "<pubkey>")],
+    ["n", "6064460175057025"],
+  ],
+  "content": nip44Encrypt(JSON.stringify([
+    ["p", "<pubkey>", "relay"],
+    ["n", "Clients List"],
+    ["petname", "<My buddy>"],
+    ["summary", "<Summary of the relationship>"],
+  ])),
+  // ...other fields
+}
+```

README.md

@@ -70,6 +70,7 @@ They exist to document what may be implemented by [Nostr](https://github.com/nos
 - [NIP-72: Moderated Communities](72.md)
 - [NIP-75: Zap Goals](75.md)
 - [NIP-78: Application-specific data](78.md)
+- [NIP-81: Relationship Status](81.md)
 - [NIP-84: Highlights](84.md)
 - [NIP-89: Recommended Application Handlers](89.md)
 - [NIP-90: Data Vending Machines](90.md)
@@ -123,6 +124,7 @@ They exist to document what may be implemented by [Nostr](https://github.com/nos
 | `10005`       | Public chats list          | [51](51.md)              |
 | `10006`       | Blocked relays list        | [51](51.md)              |
 | `10007`       | Search relays list         | [51](51.md)              |
+| `10008`       | Unbound List Names         | [81](81.md)              |
 | `10015`       | Interests list             | [51](51.md)              |
 | `10030`       | User emoji list            | [51](51.md)              |
 | `10096`       | File storage server list   | [96](96.md)              |
@@ -151,6 +153,7 @@ They exist to document what may be implemented by [Nostr](https://github.com/nos
 | `30078`       | Application-specific Data  | [78](78.md)              |
 | `30311`       | Live Event                 | [53](53.md)              |
 | `30315`       | User Statuses              | [38](38.md)              |
+| `30382`       | Relationship Status        | [81](81.md)              |
 | `30402`       | Classified Listing         | [99](99.md)              |
 | `30403`       | Draft Classified Listing   | [99](99.md)              |
 | `31922`       | Date-Based Calendar Event  | [52](52.md)              |