diff --git a/57.md b/57.md
index 1ffed5f5..8af3eb55 100644
--- a/57.md
+++ b/57.md
@@ -133,10 +133,11 @@ A reference implementation for the zapper is here: [zapper][zapper]
 
 Clients MAY fetch zap notes on posts and profiles:
 
-`{"kinds": [9735], "#p": [...]}`
+`{"kinds": [9735], "#e": [...]}`
 
 To authorize these notes, clients MUST fetch the `nostrPubkey` from the users configured lightning address or lnurl and ensure that the zaps to their posts were created by this pubkey. If clients don't do this, anyone could forge unauthorized zaps.
 
+Once authorized, clients MAY tally zaps on posts, and list them on profiles. If the zap request note contains a non-empty `content`, it may display a zap comment. Generally clients should show users the `zap request` note, and use the `zap note` to show "zap authorized by ..." but this is optional.
 
 ## Future Work