upleb.uk

Public git repos — served from a NIP-34 GRASP relay at git.upleb.uk

summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
Diffstat
-rw-r--r--17.md2
-rw-r--r--29.md12
-rw-r--r--44.md8
-rw-r--r--46.md34
-rw-r--r--47.md2
-rw-r--r--51.md8
-rw-r--r--68.md92
-rw-r--r--86.md90
-rw-r--r--90.md2
-rw-r--r--BREAKING.md100
-rw-r--r--README.md12
11 files changed, 281 insertions, 81 deletions
diff --git a/17.md b/17.md
index 72f40c4..f091a96 100644
--- a/17.md
+++ b/17.md
@@ -133,7 +133,7 @@ When sending a message to anyone, clients must then connect to the relays in the
133 133
134This example sends the message `Hola, que tal?` from `nsec1w8udu59ydjvedgs3yv5qccshcj8k05fh3l60k9x57asjrqdpa00qkmr89m` to `nsec12ywtkplvyq5t6twdqwwygavp5lm4fhuang89c943nf2z92eez43szvn4dt`. 134This example sends the message `Hola, que tal?` from `nsec1w8udu59ydjvedgs3yv5qccshcj8k05fh3l60k9x57asjrqdpa00qkmr89m` to `nsec12ywtkplvyq5t6twdqwwygavp5lm4fhuang89c943nf2z92eez43szvn4dt`.
135 135
136The two final GiftWraps, one to the receiver and the other to the sender, are: 136The two final GiftWraps, one to the receiver and the other to the sender, respectively, are:
137 137
138```json 138```json
139{ 139{
diff --git a/29.md b/29.md
index 7705c6d..601d63a 100644
--- a/29.md
+++ b/29.md
@@ -22,15 +22,13 @@ Relays are supposed to generate the events that describe group metadata and grou
22 22
23A group may be identified by a string in the format `<host>'<group-id>`. For example, a group with _id_ `abcdef` hosted at the relay `wss://groups.nostr.com` would be identified by the string `groups.nostr.com'abcdef`. 23A group may be identified by a string in the format `<host>'<group-id>`. For example, a group with _id_ `abcdef` hosted at the relay `wss://groups.nostr.com` would be identified by the string `groups.nostr.com'abcdef`.
24 24
25Group identifiers must be strings restricted to the characters `a-z0-9-_`. 25Group identifiers must be strings restricted to the characters `a-z0-9-_`, and SHOULD be random in order to avoid name collisions.
26 26
27When encountering just the `<host>` without the `'<group-id>`, clients can choose to connect to the group with id `_`, which is a special top-level group dedicated to relay-local discussions. 27When encountering just the `<host>` without the `'<group-id>`, clients MAY infer `_` as the group id, which is a special top-level group dedicated to relay-local discussions.
28
29Group identifiers in most cases should be random or pseudo-random, as that mitigates message replay confusion and ensures they can be migrated or forked to other relays easily without risking conflicting with other groups using the same id in these new relays. This isn't a hard rule, as, for example, in `unmanaged` and/or ephemeral relays groups might not want to migrate ever, so they might not care about this. Notably, the `_` relay-local group isn't expected to be migrated ever.
30 28
31## The `h` tag 29## The `h` tag
32 30
33Events sent by users to groups (chat messages, text notes, moderation events etc) must have an `h` tag with the value set to the group _id_. 31Events sent by users to groups (chat messages, text notes, moderation events etc) MUST have an `h` tag with the value set to the group _id_.
34 32
35## Timeline references 33## Timeline references
36 34
@@ -241,4 +239,6 @@ A definition for `kind:10009` was included in [NIP-51](51.md) that allows client
241 239
242### Using `unmanaged` relays 240### Using `unmanaged` relays
243 241
244To prevent event leakage, replay and confusion, when using `unmanaged` relays, clients should include the [NIP-70](70.md) `-` tag, as just the `previous` tag won't be checked by other `unmanaged` relays. 242To prevent event leakage, when using `unmanaged` relays, clients should include the [NIP-70](70.md) `-` tag, as just the `previous` tag won't be checked by other `unmanaged` relays.
243
244Groups MAY be named without relay support by adding a `name` to the corresponding tag in a user's `kind 10009` group list.
diff --git a/44.md b/44.md
index 8f781b8..8f27fed 100644
--- a/44.md
+++ b/44.md
@@ -63,7 +63,7 @@ NIP-44 version 2 has the following design characteristics:
63- SHA256 is used instead of SHA3 or BLAKE because it is already used in nostr. Also BLAKE's speed advantage 63- SHA256 is used instead of SHA3 or BLAKE because it is already used in nostr. Also BLAKE's speed advantage
64 is smaller in non-parallel environments. 64 is smaller in non-parallel environments.
65- A custom padding scheme is used instead of padmé because it provides better leakage reduction for small messages. 65- A custom padding scheme is used instead of padmé because it provides better leakage reduction for small messages.
66- Base64 encoding is used instead of another compression algorithm because it is widely available, and is already used in nostr. 66- Base64 encoding is used instead of another encoding algorithm because it is widely available, and is already used in nostr.
67 67
68### Encryption 68### Encryption
69 69
@@ -86,7 +86,7 @@ NIP-44 version 2 has the following design characteristics:
86 - Content must be encoded from UTF-8 into byte array 86 - Content must be encoded from UTF-8 into byte array
87 - Validate plaintext length. Minimum is 1 byte, maximum is 65535 bytes 87 - Validate plaintext length. Minimum is 1 byte, maximum is 65535 bytes
88 - Padding format is: `[plaintext_length: u16][plaintext][zero_bytes]` 88 - Padding format is: `[plaintext_length: u16][plaintext][zero_bytes]`
89 - Padding algorithm is related to powers-of-two, with min padded msg size of 32 89 - Padding algorithm is related to powers-of-two, with min padded msg size of 32bytes
90 - Plaintext length is encoded in big-endian as first 2 bytes of the padded blob 90 - Plaintext length is encoded in big-endian as first 2 bytes of the padded blob
915. Encrypt padded content 915. Encrypt padded content
92 - Use ChaCha20, with key and nonce from step 3 92 - Use ChaCha20, with key and nonce from step 3
@@ -148,8 +148,8 @@ validation rules, refer to BIP-340.
148 - `x[i:j]`, where `x` is a byte array and `i, j <= 0` returns a `(j - i)`-byte array with a copy of the 148 - `x[i:j]`, where `x` is a byte array and `i, j <= 0` returns a `(j - i)`-byte array with a copy of the
149 `i`-th byte (inclusive) to the `j`-th byte (exclusive) of `x`. 149 `i`-th byte (inclusive) to the `j`-th byte (exclusive) of `x`.
150- Constants `c`: 150- Constants `c`:
151 - `min_plaintext_size` is 1. 1b msg is padded to 32b. 151 - `min_plaintext_size` is 1. 1bytes msg is padded to 32bytes.
152 - `max_plaintext_size` is 65535 (64kb - 1). It is padded to 65536. 152 - `max_plaintext_size` is 65535 (64kB - 1). It is padded to 65536bytes.
153- Functions 153- Functions
154 - `base64_encode(string)` and `base64_decode(bytes)` are Base64 ([RFC 4648](https://datatracker.ietf.org/doc/html/rfc4648), with padding) 154 - `base64_encode(string)` and `base64_decode(bytes)` are Base64 ([RFC 4648](https://datatracker.ietf.org/doc/html/rfc4648), with padding)
155 - `concat` refers to byte array concatenation 155 - `concat` refers to byte array concatenation
diff --git a/46.md b/46.md
index ce6764d..d170628 100644
--- a/46.md
+++ b/46.md
@@ -45,15 +45,25 @@ _remote-signer_ provides connection token in the form:
45bunker://<remote-signer-pubkey>?relay=<wss://relay-to-connect-on>&relay=<wss://another-relay-to-connect-on>&secret=<optional-secret-value> 45bunker://<remote-signer-pubkey>?relay=<wss://relay-to-connect-on>&relay=<wss://another-relay-to-connect-on>&secret=<optional-secret-value>
46``` 46```
47 47
48_user_ passes this token to _client_, which then sends `connect` request to _remote-signer_ via the specified relays. Optional secret can be used for single successfully established connection only, _remote-signer_ SHOULD ignore new attempts to establish connection with old secret. 48_user_ passes this token to _client_, which then sends `connect` request to _remote-signer_ via the specified relays. Optional secret can be used for single successfully established connection only, _remote-signer_ SHOULD ignore new attempts to establish connection with old secret.
49 49
50### Direct connection initiated by the _client_ 50### Direct connection initiated by the _client_
51 51
52_client_ provides a connection token in the form: 52_client_ provides a connection token using `nostrconnect://` as the protocol, and `client-pubkey` as the origin. Additional information should be passed as query parameters:
53
54- `relay` (required) - one or more relay urls on which the _client_ is listening for responses from the _remote-signer_.
55- `secret` (required) - a short random string that the _remote-signer_ should return as the `result` field of its response.
56- `perms` (optional) - a comma-separated list of permissions the _client_ is requesting be approved by the _remote-signer_
57- `name` (optional) - the name of the _client_ application
58- `url` (optional) - the canonical url of the _client_ application
59- `image` (optional) - a small image representing the _client_ application
60
61Here's an example:
53 62
54``` 63```
55nostrconnect://<client-pubkey>?relay=<wss://relay-to-connect-on>&metadata=<json metadata: {"name":"...", "url": "...", "description": "...", "perms": "..."}>&secret=<required-secret-value> 64nostrconnect://83f3b2ae6aa368e8275397b9c26cf550101d63ebaab900d19dd4a4429f5ad8f5?relay=wss%3A%2F%2Frelay1.example.com&perms=nip44_encrypt%2Cnip44_decrypt%2Csign_event%3A13%2Csign_event%3A14%2Csign_event%3A1059&name=My+Client&secret=0s8j2djs&relay=wss%3A%2F%2Frelay2.example2.com
56``` 65```
66
57_user_ passes this token to _remote-signer_, which then sends `connect` *response* event to the `client-pubkey` via the specified relays. Client discovers `remote-signer-pubkey` from connect response author. `secret` value MUST be provided to avoid connection spoofing, _client_ MUST validate the `secret` returned by `connect` response. 67_user_ passes this token to _remote-signer_, which then sends `connect` *response* event to the `client-pubkey` via the specified relays. Client discovers `remote-signer-pubkey` from connect response author. `secret` value MUST be provided to avoid connection spoofing, _client_ MUST validate the `secret` returned by `connect` response.
58 68
59## Request Events `kind: 24133` 69## Request Events `kind: 24133`
@@ -62,12 +72,12 @@ _user_ passes this token to _remote-signer_, which then sends `connect` *respons
62{ 72{
63 "kind": 24133, 73 "kind": 24133,
64 "pubkey": <local_keypair_pubkey>, 74 "pubkey": <local_keypair_pubkey>,
65 "content": <nip04(<request>)>, 75 "content": <nip44(<request>)>,
66 "tags": [["p", <remote-signer-pubkey>]], 76 "tags": [["p", <remote-signer-pubkey>]],
67} 77}
68``` 78```
69 79
70The `content` field is a JSON-RPC-like message that is [NIP-04](04.md) encrypted and has the following structure: 80The `content` field is a JSON-RPC-like message that is [NIP-44](44.md) encrypted and has the following structure:
71 81
72```jsonc 82```jsonc
73{ 83{
@@ -99,7 +109,7 @@ Each of the following are methods that the _client_ sends to the _remote-signer_
99 109
100### Requested permissions 110### Requested permissions
101 111
102The `connect` method may be provided with `optional_requested_permissions` for user convenience. The permissions are a comma-separated list of `method[:params]`, i.e. `nip04_encrypt,sign_event:4` meaning permissions to call `nip04_encrypt` and to call `sign_event` with `kind:4`. Optional parameter for `sign_event` is the kind number, parameters for other methods are to be defined later. Same permission format may be used for `perms` field of `metadata` in `nostrconnect://` string. 112The `connect` method may be provided with `optional_requested_permissions` for user convenience. The permissions are a comma-separated list of `method[:params]`, i.e. `nip44_encrypt,sign_event:4` meaning permissions to call `nip44_encrypt` and to call `sign_event` with `kind:4`. Optional parameter for `sign_event` is the kind number, parameters for other methods are to be defined later. Same permission format may be used for `perms` field of `metadata` in `nostrconnect://` string.
103 113
104## Response Events `kind:24133` 114## Response Events `kind:24133`
105 115
@@ -108,13 +118,13 @@ The `connect` method may be provided with `optional_requested_permissions` for u
108 "id": <id>, 118 "id": <id>,
109 "kind": 24133, 119 "kind": 24133,
110 "pubkey": <remote-signer-pubkey>, 120 "pubkey": <remote-signer-pubkey>,
111 "content": <nip04(<response>)>, 121 "content": <nip44(<response>)>,
112 "tags": [["p", <client-pubkey>]], 122 "tags": [["p", <client-pubkey>]],
113 "created_at": <unix timestamp in seconds> 123 "created_at": <unix timestamp in seconds>
114} 124}
115``` 125```
116 126
117The `content` field is a JSON-RPC-like message that is [NIP-04](04.md) encrypted and has the following structure: 127The `content` field is a JSON-RPC-like message that is [NIP-44](44.md) encrypted and has the following structure:
118 128
119```json 129```json
120{ 130{
@@ -140,7 +150,7 @@ The `content` field is a JSON-RPC-like message that is [NIP-04](04.md) encrypted
140{ 150{
141 "kind": 24133, 151 "kind": 24133,
142 "pubkey": "eff37350d839ce3707332348af4549a96051bd695d3223af4aabce4993531d86", 152 "pubkey": "eff37350d839ce3707332348af4549a96051bd695d3223af4aabce4993531d86",
143 "content": nip04({ 153 "content": nip44({
144 "id": <random_string>, 154 "id": <random_string>,
145 "method": "sign_event", 155 "method": "sign_event",
146 "params": [json_stringified(<{ 156 "params": [json_stringified(<{
@@ -160,7 +170,7 @@ The `content` field is a JSON-RPC-like message that is [NIP-04](04.md) encrypted
160{ 170{
161 "kind": 24133, 171 "kind": 24133,
162 "pubkey": "fa984bd7dbb282f07e16e7ae87b26a2a7b9b90b7246a44771f0cf5ae58018f52", 172 "pubkey": "fa984bd7dbb282f07e16e7ae87b26a2a7b9b90b7246a44771f0cf5ae58018f52",
163 "content": nip04({ 173 "content": nip44({
164 "id": <random_string>, 174 "id": <random_string>,
165 "result": json_stringified(<signed-event>) 175 "result": json_stringified(<signed-event>)
166 }), 176 }),
@@ -203,7 +213,7 @@ _remote-signer_ MAY publish it's metadata by using [NIP-05](05.md) and [NIP-89](
203 }, 213 },
204 "nip46": { 214 "nip46": {
205 "relays": ["wss://relay1","wss://relay2"...], 215 "relays": ["wss://relay1","wss://relay2"...],
206 "nostrconnect_url": "https://remote-signer-domain.com/<nostrconnect>" 216 "nostrconnect_url": "https://remote-signer-domain.example/<nostrconnect>"
207 } 217 }
208} 218}
209``` 219```
@@ -214,4 +224,4 @@ The `<remote-signer-app-pubkey>` MAY be used to verify the domain from _remote-s
214 224
215_remote-signer_ MAY publish a NIP-89 `kind: 31990` event with `k` tag of `24133`, which MAY also include one or more `relay` tags and MAY include `nostrconnect_url` tag. The semantics of `relay` and `nostrconnect_url` tags are the same as in the section above. 225_remote-signer_ MAY publish a NIP-89 `kind: 31990` event with `k` tag of `24133`, which MAY also include one or more `relay` tags and MAY include `nostrconnect_url` tag. The semantics of `relay` and `nostrconnect_url` tags are the same as in the section above.
216 226
217_client_ MAY improve UX by discovering _remote-signers_ using their `kind: 31990` events. _client_ MAY then pre-generate `nostrconnect://` strings for the _remote-signers_, and SHOULD in that case verify that `kind: 31990` event's author is mentioned in signer's `nostr.json?name=_` file as `<remote-signer-app-pubkey>`. 227_client_ MAY improve UX by discovering _remote-signers_ using their `kind: 31990` events. _client_ MAY then pre-generate `nostrconnect://` strings for the _remote-signers_, and SHOULD in that case verify that `kind: 31990` event's author is mentioned in signer's `nostr.json?name=_` file as `<remote-signer-app-pubkey>`.
diff --git a/47.md b/47.md
index 71cd076..d1030a4 100644
--- a/47.md
+++ b/47.md
@@ -175,7 +175,7 @@ Request:
175Response: 175Response:
176 176
177For every invoice in the request, a separate response event is sent. To differentiate between the responses, each 177For every invoice in the request, a separate response event is sent. To differentiate between the responses, each
178response event contains an `d` tag with the id of the invoice it is responding to, if no id was given, then the 178response event contains a `d` tag with the id of the invoice it is responding to, if no id was given, then the
179payment hash of the invoice should be used. 179payment hash of the invoice should be used.
180 180
181```jsonc 181```jsonc
diff --git a/51.md b/51.md
index 3792d7f..23d5b99 100644
--- a/51.md
+++ b/51.md
@@ -14,7 +14,7 @@ When new items are added to an existing list, clients SHOULD append them to the
14 14
15## Types of lists 15## Types of lists
16 16
17## Standard lists 17### Standard lists
18 18
19Standard lists use normal replaceable events, meaning users may only have a single list of each kind. They have special meaning and clients may rely on them to augment a user's profile or browsing experience. 19Standard lists use normal replaceable events, meaning users may only have a single list of each kind. They have special meaning and clients may rely on them to augment a user's profile or browsing experience.
20 20
@@ -29,14 +29,14 @@ For example, _mute list_ can contain the public keys of spammers and bad actors
29| Public chats | 10005 | [NIP-28](28.md) chat channels the user is in | `"e"` (kind:40 channel definitions) | 29| Public chats | 10005 | [NIP-28](28.md) chat channels the user is in | `"e"` (kind:40 channel definitions) |
30| Blocked relays | 10006 | relays clients should never connect to | `"relay"` (relay URLs) | 30| Blocked relays | 10006 | relays clients should never connect to | `"relay"` (relay URLs) |
31| Search relays | 10007 | relays clients should use when performing search queries | `"relay"` (relay URLs) | 31| Search relays | 10007 | relays clients should use when performing search queries | `"relay"` (relay URLs) |
32| Simple groups | 10009 | [NIP-29](29.md) groups the user is in | `"group"` ([NIP-29](29.md) group ids + mandatory relay URL) | 32| Simple groups | 10009 | [NIP-29](29.md) groups the user is in | `"group"` ([NIP-29](29.md) group id + relay URL + optional group name), `"r"` for each relay in use |
33| Interests | 10015 | topics a user may be interested in and pointers | `"t"` (hashtags) and `"a"` (kind:30015 interest set) | 33| Interests | 10015 | topics a user may be interested in and pointers | `"t"` (hashtags) and `"a"` (kind:30015 interest set) |
34| Emojis | 10030 | user preferred emojis and pointers to emoji sets | `"emoji"` (see [NIP-30](30.md)) and `"a"` (kind:30030 emoji set) | 34| Emojis | 10030 | user preferred emojis and pointers to emoji sets | `"emoji"` (see [NIP-30](30.md)) and `"a"` (kind:30030 emoji set) |
35| DM relays | 10050 | Where to receive [NIP-17](17.md) direct messages | `"relay"` (see [NIP-17](17.md)) | 35| DM relays | 10050 | Where to receive [NIP-17](17.md) direct messages | `"relay"` (see [NIP-17](17.md)) |
36| Good wiki authors | 10101 | [NIP-54](54.md) user recommended wiki authors | `"p"` (pubkeys) | 36| Good wiki authors | 10101 | [NIP-54](54.md) user recommended wiki authors | `"p"` (pubkeys) |
37| Good wiki relays | 10102 | [NIP-54](54.md) relays deemed to only host useful articles | `"relay"` (relay URLs) | 37| Good wiki relays | 10102 | [NIP-54](54.md) relays deemed to only host useful articles | `"relay"` (relay URLs) |
38 38
39## Sets 39### Sets
40 40
41Sets are lists with well-defined meaning that can enhance the functionality and the UI of clients that rely on them. Unlike standard lists, users are expected to have more than one set of each kind, therefore each of them must be assigned a different `"d"` identifier. 41Sets are lists with well-defined meaning that can enhance the functionality and the UI of clients that rely on them. Unlike standard lists, users are expected to have more than one set of each kind, therefore each of them must be assigned a different `"d"` identifier.
42 42
@@ -56,7 +56,7 @@ Aside from their main identifier, the `"d"` tag, sets can optionally have a `"ti
56| Emoji sets | 30030 | categorized emoji groups | `"emoji"` (see [NIP-30](30.md)) | 56| Emoji sets | 30030 | categorized emoji groups | `"emoji"` (see [NIP-30](30.md)) |
57| Release artifact sets | 30063 | groups of files of a software release | `"e"` (kind:1063 [file metadata](94.md) events), `"i"` (application identifier, typically reverse domain notation), `"version"` | 57| Release artifact sets | 30063 | groups of files of a software release | `"e"` (kind:1063 [file metadata](94.md) events), `"i"` (application identifier, typically reverse domain notation), `"version"` |
58 58
59## Deprecated standard lists 59### Deprecated standard lists
60 60
61Some clients have used these lists in the past, but they should work on transitioning to the [standard formats](#standard-lists) above. 61Some clients have used these lists in the past, but they should work on transitioning to the [standard formats](#standard-lists) above.
62 62
diff --git a/68.md b/68.md
new file mode 100644
index 0000000..6c1e7d2
--- /dev/null
+++ b/68.md
@@ -0,0 +1,92 @@
1NIP-68
2======
3
4Picture-first feeds
5-------------------
6
7`draft` `optional`
8
9This NIP defines event kind `20` for picture-first clients. Images must be self-contained. They are hosted externally and referenced using `imeta` tags.
10
11The idea is for this type of event to cater to Nostr clients resembling platforms like Instagram, Flickr, Snapchat, or 9GAG, where the picture itself takes center stage in the user experience.
12
13## Picture Events
14
15Picture events contain a `title` tag and description in the `.content`.
16
17They may contain multiple images to be displayed as a single post.
18
19```jsonc
20{
21 "id": <32-bytes lowercase hex-encoded SHA-256 of the the serialized event data>,
22 "pubkey": <32-bytes lowercase hex-encoded public key of the event creator>,
23 "created_at": <Unix timestamp in seconds>,
24 "kind": 20,
25 "content": "<description of post>",
26 "tags": [
27 ["title", "<short title of post>"],
28
29 // Picture Data
30 [
31 "imeta",
32 "url https://nostr.build/i/my-image.jpg",
33 "m image/jpeg",
34 "blurhash eVF$^OI:${M{o#*0-nNFxakD-?xVM}WEWB%iNKxvR-oetmo#R-aen$",
35 "dim 3024x4032",
36 "alt A scenic photo overlooking the coast of Costa Rica",
37 "x <sha256 hash as specified in NIP 94>",
38 "fallback https://nostrcheck.me/alt1.jpg",
39 "fallback https://void.cat/alt1.jpg"
40 ],
41 [
42 "imeta",
43 "url https://nostr.build/i/my-image2.jpg",
44 "m image/jpeg",
45 "blurhash eVF$^OI:${M{o#*0-nNFxakD-?xVM}WEWB%iNKxvR-oetmo#R-aen$",
46 "dim 3024x4032",
47 "alt Another scenic photo overlooking the coast of Costa Rica",
48 "x <sha256 hash as specified in NIP 94>",
49 "fallback https://nostrcheck.me/alt2.jpg",
50 "fallback https://void.cat/alt2.jpg",
51
52 "annotate-user <32-bytes hex of a pubkey>:<posX>:<posY>" // Tag users in specific locations in the picture
53 ],
54
55 ["content-warning", "<reason>"], // if NSFW
56
57 // Tagged users
58 ["p", "<32-bytes hex of a pubkey>", "<optional recommended relay URL>"],
59 ["p", "<32-bytes hex of a pubkey>", "<optional recommended relay URL>"],
60
61 // Specify the media type for filters to allow clients to filter by supported kinds
62 ["m", "image/jpeg"],
63
64 // Hashes of each image to make them queryable
65 ["x", "<sha256>"]
66
67 // Hashtags
68 ["t", "<tag>"],
69 ["t", "<tag>"],
70
71 // location
72 ["location", "<location>"], // city name, state, country
73 ["g", "<geohash>"],
74
75 // When text is written in the image, add the tag to represent the language
76 ["L", "ISO-639-1"],
77 ["l", "en", "ISO-639-1"]
78 ]
79}
80```
81
82The `imeta` tag `annotate-user` places a user link in the specific position in the image.
83
84Only the following media types are accepted:
85- `image/apng`: Animated Portable Network Graphics (APNG)
86- `image/avif`: AV1 Image File Format (AVIF)
87- `image/gif`: Graphics Interchange Format (GIF)
88- `image/jpeg`: Joint Photographic Expert Group image (JPEG)
89- `image/png`: Portable Network Graphics (PNG)
90- `image/webp`: Web Picture format (WEBP)
91
92Picture events might be used with [NIP-71](71.md)'s kind `34236` to display short vertical videos in the same feed.
diff --git a/86.md b/86.md
new file mode 100644
index 0000000..6f64eee
--- /dev/null
+++ b/86.md
@@ -0,0 +1,90 @@
1NIP-86
2======
3
4Relay Management API
5--------------------
6
7`draft` `optional`
8
9Relays may provide an API for performing management tasks. This is made available as a JSON-RPC-like request-response protocol over HTTP, on the same URI as the relay's websocket.
10
11When a relay receives an HTTP(s) request with a `Content-Type` header of `application/nostr+json+rpc` to a URI supporting WebSocket upgrades, it should parse the request as a JSON document with the following fields:
12
13```json
14{
15 "method": "<method-name>",
16 "params": ["<array>", "<of>", "<parameters>"]
17}
18```
19
20Then it should return a response in the format
21
22```json
23{
24 "result": {"<arbitrary>": "<value>"},
25 "error": "<optional error message, if the call has errored>"
26}
27```
28
29This is the list of **methods** that may be supported:
30
31* `supportedmethods`:
32 - params: `[]`
33 - result: `["<method-name>", "<method-name>", ...]` (an array with the names of all the other supported methods)
34* `banpubkey`:
35 - params: `["<32-byte-hex-public-key>", "<optional-reason>"]`
36 - result: `true` (a boolean always set to `true`)
37* `listbannedpubkeys`:
38 - params: `[]`
39 - result: `[{"pubkey": "<32-byte-hex>", "reason": "<optional-reason>"}, ...]`, an array of objects
40* `allowpubkey`:
41 - params: `["<32-byte-hex-public-key>", "<optional-reason>"]`
42 - result: `true` (a boolean always set to `true`)
43* `listallowedpubkeys`:
44 - params: `[]`
45 - result: `[{"pubkey": "<32-byte-hex>", "reason": "<optional-reason>"}, ...]`, an array of objects
46* `listeventsneedingmoderation`:
47 - params: `[]`
48 - result: `[{"id": "<32-byte-hex>", "reason": "<optional-reason>"}]`, an array of objects
49* `allowevent`:
50 - params: `["<32-byte-hex-event-id>", "<optional-reason>"]`
51 - result: `true` (a boolean always set to `true`)
52* `banevent`:
53 - params: `["<32-byte-hex-event-id>", "<optional-reason>"]`
54 - result: `true` (a boolean always set to `true`)
55* `listbannedevents`:
56 - params: `[]`
57 - result: `[{"id": "<32-byte hex>", "reason": "<optional-reason>"}, ...]`, an array of objects
58* `changerelayname`:
59 - params: `["<new-name>"]`
60 - result: `true` (a boolean always set to `true`)
61* `changerelaydescription`:
62 - params: `["<new-description>"]`
63 - result: `true` (a boolean always set to `true`)
64* `changerelayicon`:
65 - params: `["<new-icon-url>"]`
66 - result: `true` (a boolean always set to `true`)
67* `allowkind`:
68 - params: `[<kind-number>]`
69 - result: `true` (a boolean always set to `true`)
70* `disallowkind`:
71 - params: `[<kind-number>]`
72 - result: `true` (a boolean always set to `true`)
73* `listallowedkinds`:
74 - params: `[]`
75 - result: `[<kind-number>, ...]`, an array of numbers
76* `blockip`:
77 - params: `["<ip-address>", "<optional-reason>"]`
78 - result: `true` (a boolean always set to `true`)
79* `unblockip`:
80 - params: `["<ip-address>"]`
81 - result: `true` (a boolean always set to `true`)
82* `listblockedips`:
83 - params: `[]`
84 - result: `[{"ip": "<ip-address>", "reason": "<optional-reason>"}, ...]`, an array of objects
85
86### Authorization
87
88The request must contain an `Authorization` header with a valid [NIP-98](./98.md) event, except the `payload` tag is required. The `u` tag is the relay URL.
89
90If `Authorization` is not provided or is invalid, the endpoint should return a 401 response.
diff --git a/90.md b/90.md
index 696ebd5..1d69b0f 100644
--- a/90.md
+++ b/90.md
@@ -185,7 +185,7 @@ Any job feedback event MIGHT include results in the `.content` field, as describ
185* Customer publishes a job request (e.g. `kind:5000` speech-to-text). 185* Customer publishes a job request (e.g. `kind:5000` speech-to-text).
186* Service Providers MAY submit `kind:7000` job-feedback events (e.g. `payment-required`, `processing`, `error`, etc.). 186* Service Providers MAY submit `kind:7000` job-feedback events (e.g. `payment-required`, `processing`, `error`, etc.).
187* Upon completion, the service provider publishes the result of the job with a `kind:6000` job-result event. 187* Upon completion, the service provider publishes the result of the job with a `kind:6000` job-result event.
188* At any point, if there is an `amount` pending to be paid as instructed by the service provider, the user can pay the included `bolt11` or zap the job result event the service provider has sent to the user 188* At any point, if there is an `amount` pending to be paid as instructed by the service provider, the user can pay the included `bolt11` or zap the job result event the service provider has sent to the user.
189 189
190Job feedback (`kind:7000`) and Job Results (`kind:6000-6999`) events MAY include an `amount` tag, this can be interpreted as a suggestion to pay. Service Providers MUST use the `payment-required` feedback event to signal that a payment is required and no further actions will be performed until the payment is sent. 190Job feedback (`kind:7000`) and Job Results (`kind:6000-6999`) events MAY include an `amount` tag, this can be interpreted as a suggestion to pay. Service Providers MUST use the `payment-required` feedback event to signal that a payment is required and no further actions will be performed until the payment is sent.
191 191
diff --git a/BREAKING.md b/BREAKING.md
index b4bd53d..77900d3 100644
--- a/BREAKING.md
+++ b/BREAKING.md
@@ -5,54 +5,57 @@ reverse chronological order.
5 5
6| Date | Commit | NIP | Change | 6| Date | Commit | NIP | Change |
7| ----------- | --------- | -------- | ------ | 7| ----------- | --------- | -------- | ------ |
8| 2024-10-15 | [1cda2dcc](https://github.com/nostr-protocol/nips/commit/1cda2dcc) | [NIP-71](71.md) | some tags were replaced with `imeta` tag | 8| 2024-12-05 | [6d16019e](https://github.com/nostr-protocol/nips/commit/6d16019e) | [46](46.md) | message encryption was changed to NIP-44 |
9| 2024-10-15 | [1cda2dcc](https://github.com/nostr-protocol/nips/commit/1cda2dcc) | [NIP-71](71.md) | `kind: 34237` was dropped | 9| 2024-11-12 | [2838e3bd](https://github.com/nostr-protocol/nips/commit/2838e3bd) | [29](29.md) | `kind: 12` and `kind: 10` were removed (use `kind: 1111` instead) |
10| 2024-10-07 | [7bb8997b](https://github.com/nostr-protocol/nips/commit/7bb8997b) | [NIP-55](55.md) | some fields and passing data were changed | 10| 2024-11-12 | [926a51e7](https://github.com/nostr-protocol/nips/commit/926a51e7) | [46](46.md) | NIP-05 login was removed |
11| 2024-08-18 | [3aff37bd](https://github.com/nostr-protocol/nips/commit/3aff37bd) | [NIP-54](54.md) | content should be Asciidoc | 11| 2024-11-12 | [926a51e7](https://github.com/nostr-protocol/nips/commit/926a51e7) | [46](46.md) | `create_account` method was removed |
12| 2024-07-31 | [3ea2f1a4](https://github.com/nostr-protocol/nips/commit/3ea2f1a4) | [NIP-45](45.md) | [444ad28d](https://github.com/nostr-protocol/nips/commit/444ad28d) was reverted | 12| 2024-11-12 | [926a51e7](https://github.com/nostr-protocol/nips/commit/926a51e7) | [46](46.md) | `connect` params and result were changed |
13| 2024-07-30 | [444ad28d](https://github.com/nostr-protocol/nips/commit/444ad28d) | [NIP-45](45.md) | NIP-45 was deprecated | 13| 2024-10-29 | [f1e8d2c4](https://github.com/nostr-protocol/nips/commit/f1e8d2c4) | [46](46.md) | bunker URL should use `remote-signer-key` |
14| 2024-07-26 | [ecee40df](https://github.com/nostr-protocol/nips/commit/ecee40df) | [NIP-19](19.md) | `nrelay` was deprecated | 14| 2024-10-15 | [1cda2dcc](https://github.com/nostr-protocol/nips/commit/1cda2dcc) | [71](71.md) | some tags were replaced with `imeta` tag |
15| 2024-07-23 | [0227a2cd](https://github.com/nostr-protocol/nips/commit/0227a2cd) | [NIP-01](01.md) | events should be sorted by id after created_at | 15| 2024-10-15 | [1cda2dcc](https://github.com/nostr-protocol/nips/commit/1cda2dcc) | [71](71.md) | `kind: 34237` was dropped |
16| 2024-06-06 | [58e94b20](https://github.com/nostr-protocol/nips/commit/58e94b20) | [NIP-25](25.md) | [8073c848](https://github.com/nostr-protocol/nips/commit/8073c848) was reverted | 16| 2024-10-07 | [7bb8997b](https://github.com/nostr-protocol/nips/commit/7bb8997b) | [55](55.md) | some fields and passing data were changed |
17| 2024-06-06 | [a6dfc7b5](https://github.com/nostr-protocol/nips/commit/a6dfc7b5) | [NIP-55](55.md) | NIP number was changed | 17| 2024-08-18 | [3aff37bd](https://github.com/nostr-protocol/nips/commit/3aff37bd) | [54](54.md) | content should be Asciidoc |
18| 2024-05-25 | [5d1d1c17](https://github.com/nostr-protocol/nips/commit/5d1d1c17) | [NIP-71](71.md) | 'aes-256-gcm' tag was removed | 18| 2024-07-31 | [3ea2f1a4](https://github.com/nostr-protocol/nips/commit/3ea2f1a4) | [45](45.md) | [444ad28d](https://github.com/nostr-protocol/nips/commit/444ad28d) was reverted |
19| 2024-05-07 | [8073c848](https://github.com/nostr-protocol/nips/commit/8073c848) | [NIP-25](25.md) | e-tags were changed to not include entire thread | 19| 2024-07-30 | [444ad28d](https://github.com/nostr-protocol/nips/commit/444ad28d) | [45](45.md) | NIP-45 was deprecated |
20| 2024-04-30 | [bad88262](https://github.com/nostr-protocol/nips/commit/bad88262) | [NIP-34](34.md) | 'earliest-unique-commit' tag was removed (use 'r' tag instead) | 20| 2024-07-26 | [ecee40df](https://github.com/nostr-protocol/nips/commit/ecee40df) | [19](19.md) | `nrelay` was deprecated |
21| 2024-02-25 | [4a171cb0](https://github.com/nostr-protocol/nips/commit/4a171cb0) | [NIP-18](18.md) | quote repost should use `q` tag | 21| 2024-07-23 | [0227a2cd](https://github.com/nostr-protocol/nips/commit/0227a2cd) | [01](01.md) | events should be sorted by id after created_at |
22| 2024-02-21 | [c6cd655c](https://github.com/nostr-protocol/nips/commit/c6cd655c) | [NIP-46](46.md) | Params were stringified | 22| 2024-06-06 | [58e94b20](https://github.com/nostr-protocol/nips/commit/58e94b20) | [25](25.md) | [8073c848](https://github.com/nostr-protocol/nips/commit/8073c848) was reverted |
23| 2024-02-16 | [cbec02ab](https://github.com/nostr-protocol/nips/commit/cbec02ab) | [NIP-49](49.md) | Password first normalized to NFKC | 23| 2024-06-06 | [a6dfc7b5](https://github.com/nostr-protocol/nips/commit/a6dfc7b5) | [55](55.md) | NIP number was changed |
24| 2024-02-15 | [afbb8dd0](https://github.com/nostr-protocol/nips/commit/afbb8dd0) | [NIP-39](39.md) | PGP identity was removed | 24| 2024-05-25 | [5d1d1c17](https://github.com/nostr-protocol/nips/commit/5d1d1c17) | [71](71.md) | 'aes-256-gcm' tag was removed |
25| 2024-02-07 | [d3dad114](https://github.com/nostr-protocol/nips/commit/d3dad114) | [NIP-46](46.md) | Connection token format was changed | 25| 2024-05-07 | [8073c848](https://github.com/nostr-protocol/nips/commit/8073c848) | [25](25.md) | e-tags were changed to not include entire thread |
26| 2024-01-30 | [1a2b21b6](https://github.com/nostr-protocol/nips/commit/1a2b21b6) | [NIP-59](59.md) | 'p' tag became optional | 26| 2024-04-30 | [bad88262](https://github.com/nostr-protocol/nips/commit/bad88262) | [34](34.md) | 'earliest-unique-commit' tag was removed (use 'r' tag instead) |
27| 2023-01-27 | [c2f34817](https://github.com/nostr-protocol/nips/commit/c2f34817) | [NIP-47](47.md) | optional expiration tag should be honored | 27| 2024-02-25 | [4a171cb0](https://github.com/nostr-protocol/nips/commit/4a171cb0) | [18](18.md) | quote repost should use `q` tag |
28| 2024-01-10 | [3d8652ea](https://github.com/nostr-protocol/nips/commit/3d8652ea) | [NIP-02](02.md) | list entries should be chronological | 28| 2024-02-21 | [c6cd655c](https://github.com/nostr-protocol/nips/commit/c6cd655c) | [46](46.md) | Params were stringified |
29| 2024-01-10 | [3d8652ea](https://github.com/nostr-protocol/nips/commit/3d8652ea) | [NIP-51](51.md) | list entries should be chronological | 29| 2024-02-16 | [cbec02ab](https://github.com/nostr-protocol/nips/commit/cbec02ab) | [49](49.md) | Password first normalized to NFKC |
30| 2023-12-30 | [29869821](https://github.com/nostr-protocol/nips/commit/29869821) | [NIP-52](52.md) | 'name' tag was removed (use 'title' tag instead) | 30| 2024-02-15 | [afbb8dd0](https://github.com/nostr-protocol/nips/commit/afbb8dd0) | [39](39.md) | PGP identity was removed |
31| 2023-12-27 | [17c67ef5](https://github.com/nostr-protocol/nips/commit/17c67ef5) | [NIP-94](94.md) | 'aes-256-gcm' tag was removed | 31| 2024-02-07 | [d3dad114](https://github.com/nostr-protocol/nips/commit/d3dad114) | [46](46.md) | Connection token format was changed |
32| 2023-12-03 | [0ba45895](https://github.com/nostr-protocol/nips/commit/0ba45895) | [NIP-01](01.md) | WebSocket status code `4000` was replaced by 'CLOSED' message | 32| 2024-01-30 | [1a2b21b6](https://github.com/nostr-protocol/nips/commit/1a2b21b6) | [59](59.md) | 'p' tag became optional |
33| 2023-11-28 | [6de35f9e](https://github.com/nostr-protocol/nips/commit/6de35f9e) | [NIP-89](89.md) | 'client' tag value was changed | 33| 2023-01-27 | [c2f34817](https://github.com/nostr-protocol/nips/commit/c2f34817) | [47](47.md) | optional expiration tag should be honored |
34| 2023-11-20 | [7822a8b1](https://github.com/nostr-protocol/nips/commit/7822a8b1) | [NIP-51](51.md) | `kind: 30000` and `kind: 30001` were deprecated | 34| 2024-01-10 | [3d8652ea](https://github.com/nostr-protocol/nips/commit/3d8652ea) | [02](02.md), [51](51.md) | list entries should be chronological |
35| 2023-11-11 | [cbdca1e9](https://github.com/nostr-protocol/nips/commit/cbdca1e9) | [NIP-84](84.md) | 'range' tag was removed | 35| 2023-12-30 | [29869821](https://github.com/nostr-protocol/nips/commit/29869821) | [52](52.md) | 'name' tag was removed (use 'title' tag instead) |
36| 2023-11-10 | [c945d8bd](https://github.com/nostr-protocol/nips/commit/c945d8bd) | [NIP-32](32.md) | 'l' tag annotations was removed | 36| 2023-12-27 | [17c67ef5](https://github.com/nostr-protocol/nips/commit/17c67ef5) | [94](94.md) | 'aes-256-gcm' tag was removed |
37| 2023-11-07 | [108b7f16](https://github.com/nostr-protocol/nips/commit/108b7f16) | [NIP-01](01.md) | 'OK' message must have 4 items | 37| 2023-12-03 | [0ba45895](https://github.com/nostr-protocol/nips/commit/0ba45895) | [01](01.md) | WebSocket status code `4000` was replaced by 'CLOSED' message |
38| 2023-10-17 | [cf672b76](https://github.com/nostr-protocol/nips/commit/cf672b76) | [NIP-03](03.md) | 'block' tag was removed | 38| 2023-11-28 | [6de35f9e](https://github.com/nostr-protocol/nips/commit/6de35f9e) | [89](89.md) | 'client' tag value was changed |
39| 2023-09-29 | [7dc6385f](https://github.com/nostr-protocol/nips/commit/7dc6385f) | [NIP-57](57.md) | optional 'a' tag was included in `zap receipt` | 39| 2023-11-20 | [7822a8b1](https://github.com/nostr-protocol/nips/commit/7822a8b1) | [51](51.md) | `kind: 30001` was deprecated |
40| 2023-08-21 | [89915e02](https://github.com/nostr-protocol/nips/commit/89915e02) | [NIP-11](11.md) | 'min_prefix' was removed | 40| 2023-11-20 | [7822a8b1](https://github.com/nostr-protocol/nips/commit/7822a8b1) | [51](51.md) | the meaning of `kind: 30000` was changed |
41| 2023-08-20 | [37c4375e](https://github.com/nostr-protocol/nips/commit/37c4375e) | [NIP-01](01.md) | replaceable events with same timestamp should be retained event with lowest id | 41| 2023-11-11 | [cbdca1e9](https://github.com/nostr-protocol/nips/commit/cbdca1e9) | [84](84.md) | 'range' tag was removed |
42| 2023-08-15 | [88ee873c](https://github.com/nostr-protocol/nips/commit/88ee873c) | [NIP-15](15.md) | 'countries' tag was renamed to 'regions' | 42| 2023-11-10 | [c945d8bd](https://github.com/nostr-protocol/nips/commit/c945d8bd) | [32](32.md) | 'l' tag annotations was removed |
43| 2023-08-14 | [72bb8a12](https://github.com/nostr-protocol/nips/commit/72bb8a12) | [NIP-12](12.md) | NIP-12, 16, 20 and 33 were merged into NIP-01 | 43| 2023-11-07 | [108b7f16](https://github.com/nostr-protocol/nips/commit/108b7f16) | [01](01.md) | 'OK' message must have 4 items |
44| 2023-08-14 | [72bb8a12](https://github.com/nostr-protocol/nips/commit/72bb8a12) | [NIP-16](16.md) | NIP-12, 16, 20 and 33 were merged into NIP-01 | 44| 2023-10-17 | [cf672b76](https://github.com/nostr-protocol/nips/commit/cf672b76) | [03](03.md) | 'block' tag was removed |
45| 2023-08-14 | [72bb8a12](https://github.com/nostr-protocol/nips/commit/72bb8a12) | [NIP-20](20.md) | NIP-12, 16, 20 and 33 were merged into NIP-01 | 45| 2023-09-29 | [7dc6385f](https://github.com/nostr-protocol/nips/commit/7dc6385f) | [57](57.md) | optional 'a' tag was included in `zap receipt` |
46| 2023-08-14 | [72bb8a12](https://github.com/nostr-protocol/nips/commit/72bb8a12) | [NIP-33](33.md) | NIP-12, 16, 20 and 33 were merged into NIP-01 | 46| 2023-08-21 | [89915e02](https://github.com/nostr-protocol/nips/commit/89915e02) | [11](11.md) | 'min_prefix' was removed |
47| 2023-08-11 | [d87f8617](https://github.com/nostr-protocol/nips/commit/d87f8617) | [NIP-25](25.md) | empty `content` should be considered as "+" | 47| 2023-08-20 | [37c4375e](https://github.com/nostr-protocol/nips/commit/37c4375e) | [01](01.md) | replaceable events with same timestamp should be retained event with lowest id |
48| 2023-08-01 | [5d63b157](https://github.com/nostr-protocol/nips/commit/5d63b157) | [NIP-57](57.md) | 'zap' tag was changed | 48| 2023-08-15 | [88ee873c](https://github.com/nostr-protocol/nips/commit/88ee873c) | [15](15.md) | 'countries' tag was renamed to 'regions' |
49| 2023-07-15 | [d1814405](https://github.com/nostr-protocol/nips/commit/d1814405) | [NIP-01](01.md) | `since` and `until` filters should be `since <= created_at <= until` | 49| 2023-08-14 | [72bb8a12](https://github.com/nostr-protocol/nips/commit/72bb8a12) | [12](12.md), [16](16.md), [20](20.md), [33](33.md) | NIP-12, 16, 20 and 33 were merged into NIP-01 |
50| 2023-07-12 | [a1cd2bd8](https://github.com/nostr-protocol/nips/commit/a1cd2bd8) | [NIP-25](25.md) | custom emoji was supported | 50| 2023-08-11 | [d87f8617](https://github.com/nostr-protocol/nips/commit/d87f8617) | [25](25.md) | empty `content` should be considered as "+" |
51| 2023-06-18 | [83cbd3e1](https://github.com/nostr-protocol/nips/commit/83cbd3e1) | [NIP-11](11.md) | 'image' was renamed to 'icon' | 51| 2023-08-01 | [5d63b157](https://github.com/nostr-protocol/nips/commit/5d63b157) | [57](57.md) | 'zap' tag was changed |
52| 2023-04-13 | [bf0a0da6](https://github.com/nostr-protocol/nips/commit/bf0a0da6) | [NIP-15](15.md) | different NIP was re-added as NIP-15 | 52| 2023-07-15 | [d1814405](https://github.com/nostr-protocol/nips/commit/d1814405) | [01](01.md) | `since` and `until` filters should be `since <= created_at <= until` |
53| 2023-04-09 | [fb5b7c73](https://github.com/nostr-protocol/nips/commit/fb5b7c73) | [NIP-15](15.md) | NIP-15 was merged into NIP-01 | 53| 2023-07-12 | [a1cd2bd8](https://github.com/nostr-protocol/nips/commit/a1cd2bd8) | [25](25.md) | custom emoji was supported |
54| 2023-03-29 | [599e1313](https://github.com/nostr-protocol/nips/commit/599e1313) | [NIP-18](18.md) | NIP-18 was bring back | 54| 2023-06-18 | [83cbd3e1](https://github.com/nostr-protocol/nips/commit/83cbd3e1) | [11](11.md) | 'image' was renamed to 'icon' |
55| 2023-03-15 | [e1004d3d](https://github.com/nostr-protocol/nips/commit/e1004d3d) | [NIP-19](19.md) | `1: relay` was changed to optionally | 55| 2023-04-13 | [bf0a0da6](https://github.com/nostr-protocol/nips/commit/bf0a0da6) | [15](15.md) | different NIP was re-added as NIP-15 |
56| 2023-04-09 | [fb5b7c73](https://github.com/nostr-protocol/nips/commit/fb5b7c73) | [15](15.md) | NIP-15 was merged into NIP-01 |
57| 2023-03-29 | [599e1313](https://github.com/nostr-protocol/nips/commit/599e1313) | [18](18.md) | NIP-18 was bring back |
58| 2023-03-15 | [e1004d3d](https://github.com/nostr-protocol/nips/commit/e1004d3d) | [19](19.md) | `1: relay` was changed to optionally |
56 59
57Breaking changes prior to 2023-03-01 are not yet documented. 60Breaking changes prior to 2023-03-01 are not yet documented.
58 61
@@ -60,4 +63,3 @@ Breaking changes prior to 2023-03-01 are not yet documented.
60 63
61- If it isn't clear that a change is breaking or not, we list it. 64- If it isn't clear that a change is breaking or not, we list it.
62- The date is the date it was merged, not necessarily the date of the commit. 65- The date is the date it was merged, not necessarily the date of the commit.
63
diff --git a/README.md b/README.md
index cbd45cf..eb6fd94 100644
--- a/README.md
+++ b/README.md
@@ -78,6 +78,7 @@ They exist to document what may be implemented by [Nostr](https://github.com/nos
78- [NIP-61: Nutzaps](61.md) 78- [NIP-61: Nutzaps](61.md)
79- [NIP-64: Chess (PGN)](64.md) 79- [NIP-64: Chess (PGN)](64.md)
80- [NIP-65: Relay List Metadata](65.md) 80- [NIP-65: Relay List Metadata](65.md)
81- [NIP-68: Picture-first feeds](68.md)
81- [NIP-69: Peer-to-peer Order events](69.md) 82- [NIP-69: Peer-to-peer Order events](69.md)
82- [NIP-70: Protected Events](70.md) 83- [NIP-70: Protected Events](70.md)
83- [NIP-71: Video Events](71.md) 84- [NIP-71: Video Events](71.md)
@@ -86,6 +87,7 @@ They exist to document what may be implemented by [Nostr](https://github.com/nos
86- [NIP-75: Zap Goals](75.md) 87- [NIP-75: Zap Goals](75.md)
87- [NIP-78: Application-specific data](78.md) 88- [NIP-78: Application-specific data](78.md)
88- [NIP-84: Highlights](84.md) 89- [NIP-84: Highlights](84.md)
90- [NIP-86: Relay Management API](86.md)
89- [NIP-89: Recommended Application Handlers](89.md) 91- [NIP-89: Recommended Application Handlers](89.md)
90- [NIP-90: Data Vending Machines](90.md) 92- [NIP-90: Data Vending Machines](90.md)
91- [NIP-92: Media Attachments](92.md) 93- [NIP-92: Media Attachments](92.md)
@@ -93,6 +95,8 @@ They exist to document what may be implemented by [Nostr](https://github.com/nos
93- [NIP-96: HTTP File Storage Integration](96.md) 95- [NIP-96: HTTP File Storage Integration](96.md)
94- [NIP-98: HTTP Auth](98.md) 96- [NIP-98: HTTP Auth](98.md)
95- [NIP-99: Classified Listings](99.md) 97- [NIP-99: Classified Listings](99.md)
98- [NIP-7D: Threads](7D.md)
99- [NIP-C7: Chats](C7.md)
96 100
97## Event Kinds 101## Event Kinds
98 102
@@ -107,14 +111,15 @@ They exist to document what may be implemented by [Nostr](https://github.com/nos
107| `6` | Repost | [18](18.md) | 111| `6` | Repost | [18](18.md) |
108| `7` | Reaction | [25](25.md) | 112| `7` | Reaction | [25](25.md) |
109| `8` | Badge Award | [58](58.md) | 113| `8` | Badge Award | [58](58.md) |
110| `9` | Group Chat Message | [29](29.md) | 114| `9` | Chat Message | [C7](C7.md) |
111| `10` | Group Chat Threaded Reply | 29 (deprecated) | 115| `10` | Group Chat Threaded Reply | 29 (deprecated) |
112| `11` | Group Thread | [29](29.md) | 116| `11` | Thread | [7D](7D.md) |
113| `12` | Group Thread Reply | 29 (deprecated) | 117| `12` | Group Thread Reply | 29 (deprecated) |
114| `13` | Seal | [59](59.md) | 118| `13` | Seal | [59](59.md) |
115| `14` | Direct Message | [17](17.md) | 119| `14` | Direct Message | [17](17.md) |
116| `16` | Generic Repost | [18](18.md) | 120| `16` | Generic Repost | [18](18.md) |
117| `17` | Reaction to a website | [25](25.md) | 121| `17` | Reaction to a website | [25](25.md) |
122| `20` | Picture | [68](68.md) |
118| `40` | Channel Creation | [28](28.md) | 123| `40` | Channel Creation | [28](28.md) |
119| `41` | Channel Metadata | [28](28.md) | 124| `41` | Channel Metadata | [28](28.md) |
120| `42` | Channel Message | [28](28.md) | 125| `42` | Channel Message | [28](28.md) |
@@ -179,7 +184,7 @@ They exist to document what may be implemented by [Nostr](https://github.com/nos
179| `24242` | Blobs stored on mediaservers | [Blossom][blossom] | 184| `24242` | Blobs stored on mediaservers | [Blossom][blossom] |
180| `27235` | HTTP Auth | [98](98.md) | 185| `27235` | HTTP Auth | [98](98.md) |
181| `30000` | Follow sets | [51](51.md) | 186| `30000` | Follow sets | [51](51.md) |
182| `30001` | Generic lists | [51](51.md) | 187| `30001` | Generic lists | 51 (deprecated) |
183| `30002` | Relay sets | [51](51.md) | 188| `30002` | Relay sets | [51](51.md) |
184| `30003` | Bookmark sets | [51](51.md) | 189| `30003` | Bookmark sets | [51](51.md) |
185| `30004` | Curation sets | [51](51.md) | 190| `30004` | Curation sets | [51](51.md) |
@@ -278,6 +283,7 @@ They exist to document what may be implemented by [Nostr](https://github.com/nos
278| `L` | label namespace | -- | [32](32.md) | 283| `L` | label namespace | -- | [32](32.md) |
279| `m` | MIME type | -- | [94](94.md) | 284| `m` | MIME type | -- | [94](94.md) |
280| `p` | pubkey (hex) | relay URL, petname | [01](01.md), [02](02.md) | 285| `p` | pubkey (hex) | relay URL, petname | [01](01.md), [02](02.md) |
286| `P` | pubkey (hex) | -- | [57](57.md) |
281| `q` | event id (hex) | relay URL, pubkey (hex) | [18](18.md) | 287| `q` | event id (hex) | relay URL, pubkey (hex) | [18](18.md) |
282| `r` | a reference (URL, etc) | -- | [24](24.md), [25](25.md) | 288| `r` | a reference (URL, etc) | -- | [24](24.md), [25](25.md) |
283| `r` | relay url | marker | [65](65.md) | 289| `r` | relay url | marker | [65](65.md) |
generated by cgit v1.2.3 (git 2.39.1) at 2026-08-22 23:18:53 +0000