From df577ccd111fcf794a401478c3b97a02c8e020da Mon Sep 17 00:00:00 2001
From: "Nostr.Band" <124499563+nostrband@users.noreply.github.com>
Date: Mon, 20 Jan 2025 21:31:48 +0100
Subject: [PATCH] Make description_hash verification optional

https://njump.me/nevent1qyw8wumn8ghj7cn4vd4k2apwvdhhyctrd3jjuum0vd5kzmp0qy88wumn8ghj7mn0wvhxcmmv9uq3samnwvaz7tmrv4kxcctj9ehx7um5wgh8w6twv5hsz3thwden5te0v33rgetxda382uejd9k8garhx4nk76mrwa3kkvm0dd3hydphxe58z6md09ckgat009ukgmr0xf4rw6tfvajks6mevshxcmmrv9kz7qgnwaehxw309ahkvenrdpskjm3wwp6kytcqyznz66q53w6tqa38w2088z7028jcvelnvpl3dcv9c3pmnq0ay44nzjc7wxd
---
 57.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/57.md b/57.md
index 3f55e57b..c37126e8 100644
--- a/57.md
+++ b/57.md
@@ -132,7 +132,7 @@ The following should be true of the `zap receipt` event:
 - `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).
 - The `zap receipt` MUST have a `bolt11` tag containing the description hash bolt11 invoice.
 - The `zap receipt` MUST contain a `description` tag which is the JSON-encoded zap request.
-- `SHA256(description)` MUST match the description hash in the bolt11 invoice.
+- `SHA256(description)` SHOULD match the description hash in the bolt11 invoice.
 - 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.
 
 The `zap receipt` is not a proof of payment, all it proves is that some nostr user fetched an invoice. The existence of the `zap receipt` implies the invoice as paid, but it could be a lie given a rogue implementation.