diff options
| author | hodlbod <jstaab@protonmail.com> | 2024-09-03 13:56:56 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-09-03 13:56:56 -0700 |
| commit | c02b161d9ed8f2edb7633b467ad2dd25252ed55c (patch) | |
| tree | 0a9198bac9d1976cf0744c30516400ee5cff26aa /57.md | |
| parent | 378dfaa5dbf44bd1f17fd70f8727b636b7c99239 (diff) | |
| parent | c8dc1eadffe0ff894ec39e291c5b28bb18e6db9e (diff) | |
Merge pull request #1477 from kehiy/jsonc
format(all): JSON formatting
Diffstat (limited to '57.md')
| -rw-r--r-- | 57.md | 2 |
1 files changed, 1 insertions, 1 deletions
| @@ -171,7 +171,7 @@ A client can retrieve `zap receipt`s on events and pubkeys using a NIP-01 filter | |||
| 171 | 171 | ||
| 172 | When an event includes one or more `zap` tags, clients wishing to zap it SHOULD calculate the lnurl pay request based on the tags 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 the 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 | When an event includes one or more `zap` tags, clients wishing to zap it SHOULD calculate the lnurl pay request based on the tags 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 the 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`). |
| 173 | 173 | ||
| 174 | ```js | 174 | ```jsonc |
| 175 | { | 175 | { |
| 176 | "tags": [ | 176 | "tags": [ |
| 177 | [ "zap", "82341f882b6eabcd2ba7f1ef90aad961cf074af15b9ef44a09f9d2a8fbfbe6a2", "wss://nostr.oxtr.dev", "1" ], // 25% | 177 | [ "zap", "82341f882b6eabcd2ba7f1ef90aad961cf074af15b9ef44a09f9d2a8fbfbe6a2", "wss://nostr.oxtr.dev", "1" ], // 25% |