From 9bc2d17a0f7fa90120c8f9a50181c4c27d3415ca Mon Sep 17 00:00:00 2001
From: Vitor Pamplona <vitor@vitorpamplona.com>
Date: Tue, 14 Jan 2025 18:26:49 -0500
Subject: [PATCH] Zapraiser

---
 57.md | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/57.md b/57.md
index 3f55e57b..e56825e9 100644
--- a/57.md
+++ b/57.md
@@ -183,6 +183,20 @@ When an event includes one or more `zap` tags, clients wishing to zap it SHOULD
 
 Clients MAY display the zap split configuration in the note.
 
+### Appendix H: `zapraiser` tag on other events
+
+Any event can include a `zapraiser` tag with the tag's value equal to the total amount of sats the author wishes to fundraise from zaps to its event. 
+
+```jsonc
+{
+    "tags": [
+        [ "zapraiser", "1000" ],  // 1000 sats
+    ]
+}
+```
+
+Clients MAY display fundraising information in any way they see fit.
+
 ## 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.