Event kinds

Communitator publishes up to three Nostr event kinds from one template. These integers are event-kind identifiers, not TCP ports or NIP numbers: a kind tells Nostr clients how to interpret the event, while a NIP number identifies the protocol document that defines it. Each event is created at apply time and signed by the member’s NIP-07 extension.

Kind 10002 — relay list (NIP-65)

Each valid main relay becomes an r tag.

["r", "wss://relay.example", "read"]

• A read-only relay includes read.
• A write-only relay includes write.
• A relay used for both directions has no third tag value.

The signed event is published after explicit user approval to the deduplicated union of configured blast destinations and reviewed template main relays. A relay in both groups is contacted once.

Kind 10063 — Blossom servers (NIP-B7)

Each valid server becomes a server tag.

["server", "https://media.example"]

The source application preserves the listed order. The event is published after explicit user approval to the deduplicated union of configured blast destinations and reviewed template main relays.

Kind 10050 — DM relays (NIP-17)

Each valid DM relay becomes a relay tag.

["relay", "wss://dm.example"]

The event is published after explicit user approval to the deduplicated union of configured blast destinations and reviewed template main relays.

Shared event fields

Every unsigned signer input includes:

• the numeric kind;
• the current Unix timestamp;
• the generated tags;
• an empty content string.

Signer identity is intentionally absent from that reviewed input. The browser extension returns a signed event containing its public key, ID, and signature; Communitator verifies those fields and the exact reviewed payload before it sends the standard EVENT message to any destination.