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

This commit is contained in:
arthurfranca 2024-02-11 18:52:14 -03:00
parent ee4011d84e
commit d52fd3bacd

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`,
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:
`summary`, `image`, `audio`, `video`. The first holds a text excerpt while the others an URL.
@ -23,7 +23,7 @@ Example:
{
"kind": 1063,
"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>"],
["dim", "800x600"]
],
@ -34,7 +34,7 @@ Example:
## 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.
It uses the custom NIP-42 event serialization for events that require `AUTH`.
@ -47,7 +47,7 @@ Example:
```json
{
"kind": 30042,
"kind": 40042,
"pubkey": "<author_pubkey>",
"tags": [
["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
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 }`