nostr/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2024-12-23 00:45:53 -05:00
Code Issues Actions Packages Projects Releases Wiki Activity

Use new kind range for events that require auth based on 'A' tag

Browse Source
This commit is contained in:
arthurfranca 2024-02-11 18:52:14 -03:00
parent ee4011d84e
commit d52fd3bacd
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
00.md
View File

@ -12,7 +12,7 @@ This NIP defines how to upgrade a public event with the property of limiting acc
A public event (with no access control), such as of `kind:1`, A public event (with no access control), such as of `kind:1`,
must be published or updated with a `full_event` tag pointing to a must be published or updated with a `full_event` tag pointing to a
`kind:30042` event address. `kind:40042` event address.
It may include one of the following tags holding a preview of the full event content: It may include one of the following tags holding a preview of the full event content:
`summary`, `image`, `audio`, `video`. The first holds a text excerpt while the others an URL. `summary`, `image`, `audio`, `video`. The first holds a text excerpt while the others an URL.
@ -23,7 +23,7 @@ Example:
{ {
"kind": 1063, "kind": 1063,
"tags": [ "tags": [
["full_event", "30042:<32-bytes lowercase hex of a pubkey>:abc", "<recommended relay URL, optional>"], ["full_event", "40042:<32-bytes lowercase hex of a pubkey>:abc", "<recommended relay URL, optional>"],
["image", "<string with preview URI>"], ["image", "<string with preview URI>"],
["dim", "800x600"] ["dim", "800x600"]
], ],
@ -34,7 +34,7 @@ Example:
## Full Event ## Full Event
A "Full Event" is of `kind:30042`. It has [NIP-42](42.md) `A` tags the author A "Full Event" is of `kind:40042`. It has [NIP-42](42.md) `A` tags the author
can update at will with the pubkeys allowed to access it. can update at will with the pubkeys allowed to access it.
It uses the custom NIP-42 event serialization for events that require `AUTH`. It uses the custom NIP-42 event serialization for events that require `AUTH`.
@ -47,7 +47,7 @@ Example:
```json ```json
{ {
"kind": 30042, "kind": 40042,
"pubkey": "<author_pubkey>", "pubkey": "<author_pubkey>",
"tags": [ "tags": [
["d", "<random>"], ["d", "<random>"],
@ -74,4 +74,4 @@ a `#A` filter key set to the client's user pubkey.
If the user has rights to access the full event, the relay will send it If the user has rights to access the full event, the relay will send it
after the NIP-42 authentication flow. after the NIP-42 authentication flow.
For example: `{ kinds: [30042], authors: ["abc"], #d: ["xyz"], #A: ["<client's user pubkey>"], limit: 1 }` For example: `{ kinds: [40042], authors: ["abc"], #d: ["xyz"], #A: ["<client's user pubkey>"], limit: 1 }`