From 5ae5a6d0553e34afc3cf19e96043f7e0e2b349ef Mon Sep 17 00:00:00 2001 From: Asai Toshiya Date: Fri, 24 Nov 2023 02:44:12 +0900 Subject: Remove "NIP-33" (#896) --- 57.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to '57.md') diff --git a/57.md b/57.md index 2b2c97b..759e203 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. -- cgit v1.2.3