Skip to content

Add Live Event Consent (kind:30316) to NIP-53 #2006

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Add Live Event Consent (kind:30316) to NIP-53 #2006

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 20 additions & 0 deletions 53.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down