From 5ae5a6d0553e34afc3cf19e96043f7e0e2b349ef Mon Sep 17 00:00:00 2001 From: Asai Toshiya Date: Fri, 24 Nov 2023 02:44:12 +0900 Subject: [PATCH 1/2] Remove "NIP-33" (#896) --- 09.md | 2 +- 57.md | 4 ++-- 89.md | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/09.md b/09.md index f92410fa..fbbd6e13 100644 --- a/09.md +++ b/09.md @@ -8,7 +8,7 @@ Event Deletion A special event with kind `5`, meaning "deletion" is defined as having a list of one or more `e` tags, each referencing an event the author is requesting to be deleted. -Each tag entry must contain an "e" event id and/or NIP-33 `a` tags intended for deletion. +Each tag entry must contain an "e" event id and/or `a` tags intended for deletion. The event's `content` field MAY contain a text note describing the reason for the deletion. diff --git a/57.md b/57.md index 2b2c97b9..759e2033 100644 --- a/57.md +++ b/57.md @@ -36,7 +36,7 @@ A `zap request` is an event of kind `9734` that is _not_ published to relays, bu In addition, the event MAY include the following tags: - `e` is an optional hex-encoded event id. Clients MUST include this if zapping an event rather than a person. -- `a` is an optional NIP-33 event coordinate that allows tipping parameterized replaceable events such as NIP-23 long-form notes. +- `a` is an optional event coordinate that allows tipping parameterized replaceable events such as NIP-23 long-form notes. Example: @@ -110,7 +110,7 @@ When a client sends a `zap request` event to a server's lnurl-pay callback URL, 4. It MUST have 0 or 1 `e` tags 5. There should be a `relays` tag with the relays to send the `zap receipt` to. 6. If there is an `amount` tag, it MUST be equal to the `amount` query parameter. -7. If there is an `a` tag, it MUST be a valid NIP-33 event coordinate +7. If there is an `a` tag, it MUST be a valid event coordinate The event MUST then be stored for use later, when the invoice is paid. diff --git a/89.md b/89.md index be3d075d..097bdcbd 100644 --- a/89.md +++ b/89.md @@ -65,7 +65,7 @@ The third value of the tag SHOULD be the platform where this recommendation migh * `content` is an optional `metadata`-like stringified JSON object, as described in NIP-01. This content is useful when the pubkey creating the `kind:31990` is not an application. If `content` is empty, the `kind:0` of the pubkey should be used to display application information (e.g. name, picture, web, LUD16, etc.) * `k` tags' value is the event kind that is supported by this `kind:31990`. -Using a `k` tag(s) (instead of having the kind onf the NIP-33 `d` tag) provides: +Using a `k` tag(s) (instead of having the kind of the `d` tag) provides: * Multiple `k` tags can exist in the same event if the application supports more than one event kind and their handler URLs are the same. * The same pubkey can have multiple events with different apps that handle the same event kind. * `bech32` in a URL MUST be replaced by clients with the NIP-19-encoded entity that should be loaded by the application. From 1a106c6bff20a9408fe0ec51b265e3c5de86d25f Mon Sep 17 00:00:00 2001 From: Alejandro Date: Thu, 23 Nov 2023 19:17:28 +0100 Subject: [PATCH 2/2] [NIP-75] add optional 'image' and 'summary' tags (#890) --- 75.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/75.md b/75.md index f3cf5d06..c16436a8 100644 --- a/75.md +++ b/75.md @@ -35,6 +35,8 @@ Example event: The following tags are OPTIONAL. - `closed_at` - timestamp for determining which zaps are included in the tally. Zap receipts published after the `closed_at` timestamp SHOULD NOT count towards the goal progress. +- `image` - an image for the goal +- `summary` - a brief description ```json { @@ -43,6 +45,8 @@ The following tags are OPTIONAL. ["relays", "wss://alicerelay.example.com", "wss://bobrelay.example.com", ...], ["amount", "210000"], ["closed_at", ""], + ["image", ""], + ["summary", ""], ], "content": "Nostrasia travel expenses", ...