From dd8631b81e0742d7b60a9cea0abc83260f0ae6fd Mon Sep 17 00:00:00 2001 From: "Robert C. Martin" Date: Sat, 20 May 2023 07:53:39 -0500 Subject: [PATCH] Uncle Bob's Observations from the field --- 57.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/57.md b/57.md index cb1f126c..56b834f0 100644 --- a/57.md +++ b/57.md @@ -181,3 +181,6 @@ When an event includes a `zap` tag, clients SHOULD calculate the lnurl pay reque ## Future Work Zaps can be extended to be more private by encrypting `zap request` notes to the target user, but for simplicity it has been left out of this initial draft. + +## Observations from the field. +The 9735 Zap Receipt event contains a tag named `description`. The content of this tag appears to be the 9734 Zap Request event. The `pubkey` of the Zap Request identifies the sender of the zap. This is useful for clients that want to alert their users about who sent them zaps. However the `amount` tag of the Zap Request is not reliably included by the various wallet processors. Some do. Some don't. So clients may not be able to tell users the amount of the incoming zaps.