From d14602cea5163bf67210469826c4a2c2044845cf Mon Sep 17 00:00:00 2001
From: Egge <80262989+Egge7@users.noreply.github.com>
Date: Sun, 9 Apr 2023 07:34:26 +0200
Subject: [PATCH] added pubkey zap-tag

---
 57.md | 10 +++++++++-
 1 file changed, 9 insertions(+), 1 deletion(-)

diff --git a/57.md b/57.md
index 17042ea4..ddb91a8b 100644
--- a/57.md
+++ b/57.md
@@ -168,7 +168,15 @@ A client can retrieve `zap receipts` on events and pubkeys using a NIP-01 filter
 
 ### Appendix G: `zap` tag on zapped event
 
-When an event includes a `zap` tag, clients SHOULD calculate the lnurl pay request based on it's value instead of the profile's field. An optional third argument on the tag specifies the type of value, either `lud06` or `lud16`.
+When an event includes a `zap` tag, clients SHOULD calculate the lnurl pay request endpoint based on it's value. A third argument on the tag specifies the type of value, either `pubkey`, `lud06` or `lud16`.
+
+- `lud06` : Calculate lnurl pay request endpoint according to [lud06](https://github.com/lnurl/luds/blob/luds/06.md)
+- `lud16` : Calculate lnurl pay request endpoint according to [lud16](https://github.com/lnurl/luds/blob/luds/16.md)
+- `pubkey`: Find either a lud06 or lud16 property in this pubkeys metadata and calculate lnurl pay request endpoint accordingly
+
+#### Client best-practices
+
+When creating zap-able events clients SHOULD default to the pubkey-type, as this allows events to stay zap-able for a long time, even if users choose to change their wallet or provider.
 
 ```json
 {