diff options
| author | Oscar Merry <MerryOscar@users.noreply.github.com> | 2024-06-17 13:38:45 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-06-17 13:38:45 +0100 |
| commit | 45351b561dcc15b9d3c09b64967a5e30a80ddabe (patch) | |
| tree | e3bb8995aed591b519d042909eddd7d983bbe56e /57.md | |
| parent | 32004283da0f0893d7b697c9a0b1a1f8611e9929 (diff) | |
| parent | c576737ba42772a561c6ebfd9faf0baae6d19b17 (diff) | |
Merge branch 'nostr-protocol:master' into external-content-ids
Diffstat (limited to '57.md')
| -rw-r--r-- | 57.md | 2 |
1 files changed, 1 insertions, 1 deletions
| @@ -131,7 +131,7 @@ The following should be true of the `zap receipt` event: | |||
| 131 | - The `created_at` date SHOULD be set to the invoice `paid_at` date for idempotency. | 131 | - The `created_at` date SHOULD be set to the invoice `paid_at` date for idempotency. |
| 132 | - `tags` MUST include the `p` tag (zap recipient) AND optional `e` tag from the `zap request` AND optional `a` tag from the `zap request` AND optional `P` tag from the pubkey of the zap request (zap sender). | 132 | - `tags` MUST include the `p` tag (zap recipient) AND optional `e` tag from the `zap request` AND optional `a` tag from the `zap request` AND optional `P` tag from the pubkey of the zap request (zap sender). |
| 133 | - The `zap receipt` MUST have a `bolt11` tag containing the description hash bolt11 invoice. | 133 | - The `zap receipt` MUST have a `bolt11` tag containing the description hash bolt11 invoice. |
| 134 | - The `zap receipt` MUST contain a `description` tag which is the JSON-encoded invoice description. | 134 | - The `zap receipt` MUST contain a `description` tag which is the JSON-encoded zap request. |
| 135 | - `SHA256(description)` MUST match the description hash in the bolt11 invoice. | 135 | - `SHA256(description)` MUST match the description hash in the bolt11 invoice. |
| 136 | - The `zap receipt` MAY contain a `preimage` tag to match against the payment hash of the bolt11 invoice. This isn't really a payment proof, there is no real way to prove that the invoice is real or has been paid. You are trusting the author of the `zap receipt` for the legitimacy of the payment. | 136 | - The `zap receipt` MAY contain a `preimage` tag to match against the payment hash of the bolt11 invoice. This isn't really a payment proof, there is no real way to prove that the invoice is real or has been paid. You are trusting the author of the `zap receipt` for the legitimacy of the payment. |
| 137 | 137 | ||