diff --git a/53.md b/53.md
index d64f3ef300..a5bb4282c7 100644
--- a/53.md
+++ b/53.md
@@ -61,6 +61,26 @@ Clients MAY only display participants if the proof is available or MAY display p
 
 This feature is important to avoid malicious event owners adding large account holders to the event, without their knowledge, to lure their followers into the malicious owner's trap.
 
+#### Live Event Consent
+
+Event `kind:30316` "Live Event Consent" provides a standardized mechanism for participants to publish their agreement to join a Live Event. Participants publish consent events containing the same cryptographic proof used in the `p` tag.
+
+```jsonc
+{
+  "kind": 30316,
+  "tags": [
+    ["d", "<live-event-d-tag>"],
+    ["a", "30311:<organizer_pubkey>:<event_d_tag>", "<optional-relay-hint>"],
+    ["proof", "<hex-encoded-signature>"],
+    ["p", "<organizer_pubkey>"]
+  ],
+  "content": "<optional consent message>",
+  // other fields...
+}
+```
+
+Event owners can discover consent events by querying for `kind:30316` events with an `a` tag matching their Live Event. The proof from the consent event can then be included in the Live Event's `p` tag.
+
 ### Live Chat Message
 
 Event `kind:1311` is live chat's channel message. Clients MUST include the `a` tag of the activity. An `e` tag denotes the direct parent message this post is replying to.