diff options
| author | Asai Toshiya <to.asai.60@gmail.com> | 2023-11-24 02:44:12 +0900 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-11-23 14:44:12 -0300 |
| commit | 5ae5a6d0553e34afc3cf19e96043f7e0e2b349ef (patch) | |
| tree | 208799976bccde900c48c22037d756201eb02d4d /57.md | |
| parent | 7822a8b12670312aff104ddc03066425882f739d (diff) | |
Remove "NIP-33" (#896)
Diffstat (limited to '57.md')
| -rw-r--r-- | 57.md | 4 |
1 files changed, 2 insertions, 2 deletions
| @@ -36,7 +36,7 @@ A `zap request` is an event of kind `9734` that is _not_ published to relays, bu | |||
| 36 | In addition, the event MAY include the following tags: | 36 | In addition, the event MAY include the following tags: |
| 37 | 37 | ||
| 38 | - `e` is an optional hex-encoded event id. Clients MUST include this if zapping an event rather than a person. | 38 | - `e` is an optional hex-encoded event id. Clients MUST include this if zapping an event rather than a person. |
| 39 | - `a` is an optional NIP-33 event coordinate that allows tipping parameterized replaceable events such as NIP-23 long-form notes. | 39 | - `a` is an optional event coordinate that allows tipping parameterized replaceable events such as NIP-23 long-form notes. |
| 40 | 40 | ||
| 41 | Example: | 41 | Example: |
| 42 | 42 | ||
| @@ -110,7 +110,7 @@ When a client sends a `zap request` event to a server's lnurl-pay callback URL, | |||
| 110 | 4. It MUST have 0 or 1 `e` tags | 110 | 4. It MUST have 0 or 1 `e` tags |
| 111 | 5. There should be a `relays` tag with the relays to send the `zap receipt` to. | 111 | 5. There should be a `relays` tag with the relays to send the `zap receipt` to. |
| 112 | 6. If there is an `amount` tag, it MUST be equal to the `amount` query parameter. | 112 | 6. If there is an `amount` tag, it MUST be equal to the `amount` query parameter. |
| 113 | 7. If there is an `a` tag, it MUST be a valid NIP-33 event coordinate | 113 | 7. If there is an `a` tag, it MUST be a valid event coordinate |
| 114 | 114 | ||
| 115 | The event MUST then be stored for use later, when the invoice is paid. | 115 | The event MUST then be stored for use later, when the invoice is paid. |
| 116 | 116 | ||