diff options
| author | Vitor Pamplona <vitor@vitorpamplona.com> | 2023-05-24 12:20:53 -0400 |
|---|---|---|
| committer | Vitor Pamplona <vitor@vitorpamplona.com> | 2023-05-24 12:20:53 -0400 |
| commit | 5834c054398b39404868746db973ea7f373d1392 (patch) | |
| tree | 9c3edc9ce0b9a2d2b90ca1bd3c8fa5c6f386302a /57.md | |
| parent | 2f8be7c32b7b624ed65b3238d3ada9f2f8859777 (diff) | |
Dropping lud06 and lud16 from the zap tag
Diffstat (limited to '57.md')
| -rw-r--r-- | 57.md | 10 |
1 files changed, 5 insertions, 5 deletions
| @@ -166,16 +166,16 @@ A client can retrieve `zap receipt`s on events and pubkeys using a NIP-01 filter | |||
| 166 | - The `invoiceAmount` contained in the `bolt11` tag of the `zap receipt` MUST equal the `amount` tag of the `zap request` (if present). | 166 | - The `invoiceAmount` contained in the `bolt11` tag of the `zap receipt` MUST equal the `amount` tag of the `zap request` (if present). |
| 167 | - The `lnurl` tag of the `zap request` (if present) SHOULD equal the recipient's `lnurl`. | 167 | - The `lnurl` tag of the `zap request` (if present) SHOULD equal the recipient's `lnurl`. |
| 168 | 168 | ||
| 169 | ### Appendix G: `zap` tag on zapped event | 169 | ### Appendix G: `zap` tag on other events |
| 170 | 170 | ||
| 171 | When an event includes one or more `zap` tags, clients SHOULD calculate the lnurl pay request based on their value instead of the profile's field. The tag's second argument is a `lud06` address, a `lud16` identifier or a `hex` string of the receiver's pub key. An optional third argument specifies the type of the previous value: `lud06`, `lud16` or `pubkey`. An optional fourth parameter specifies the weight (a generalization of a percentage) assigned to the respective receiver. Clients should parse all weights, calculate a sum, and then a percentage to each receiver. If weights are not present, CLIENTS should equally divide the zap amount to all receivers. If weights are only partially present, receivers without a weight should not be zapped (`weight = 0`). | 171 | When an event includes one or more `zap` tags, clients wishing to zap it SHOULD calculate the lnurl pay request based on their value instead of the event author's profile field. The tag's second argument is the `hex` string of the receiver's pub key and third argument is the relay to download the receiver's metadata (Kind-0). An optional fourth parameter specifies the weight (a generalization of a percentage) assigned to the respective receiver. Clients should parse all weights, calculate a sum, and then a percentage to each receiver. If weights are not present, CLIENTS should equally divide the zap amount to all receivers. If weights are only partially present, receivers without a weight should not be zapped (`weight = 0`). |
| 172 | 172 | ||
| 173 | ```js | 173 | ```js |
| 174 | { | 174 | { |
| 175 | "tags": [ | 175 | "tags": [ |
| 176 | [ "zap", "LNURL..", "lud06", "1" ], // 25% | 176 | [ "zap", "82341f882b6eabcd2ba7f1ef90aad961cf074af15b9ef44a09f9d2a8fbfbe6a2", "wss://nostr.oxtr.dev", "1" ], // 25% |
| 177 | [ "zap", "pablo@f7z.io", "lud16", "1" ], // 25% | 177 | [ "zap", "fa984bd7dbb282f07e16e7ae87b26a2a7b9b90b7246a44771f0cf5ae58018f52", "wss://nostr.wine/", "1" ], // 25% |
| 178 | [ "zap", "460c25e682fda7832b52d1f22d3d22b3176d972f60dcdc3212ed8c92ef85065c", "pubkey", "2" ] // 50% | 178 | [ "zap", "460c25e682fda7832b52d1f22d3d22b3176d972f60dcdc3212ed8c92ef85065c", "wss://nos.lol/", "2" ] // 50% |
| 179 | ] | 179 | ] |
| 180 | } | 180 | } |
| 181 | ``` | 181 | ``` |