A profile list is an addressable set of pubkeys with optional membership metadata — a display name, badge image, description, and application form. Communities use them as per-section access control lists; the same event doubles as a displayable membership tier in user profiles.

An addressable event containing one or more pubkeys. When used as a community membership list, the d tag matches the section name from the community’s content tag.

Required Tags

Optional Tags

Content

Event Structure

{
  "kind": 30000,
  "pubkey": "<community-pubkey>",
  "tags": [
    ["d", "Chat"],
    ["name", "Chat Member"],
    ["image", "https://example.com/chat-badge.png"],
    ["form", "30168:<community-pubkey>:chat-application"],
    ["p", "<member-pubkey-1>"],
    ["p", "<member-pubkey-2>"],
    ["p", "<member-pubkey-3>"]
  ],
  "content": "Can participate in community chat and discussions",
  "created_at": 1234567890
}

Publishing permissions within a community section are determined by membership:

1. Client fetches the community’s "kind 10222" to get content sections

2. Client fetches the profile list (kind:30000) for the desired section

3. User can publish if their pubkey is in the list’s p tags

When a profile list includes a form tag, its value is either a NIP form reference (30168:<pubkey>:<form-id>) or a web URL. For a NIP form: user fetches the form template "kind 30168", fills out and submits a form response "kind 1069", then the community admin adds the user’s pubkey to the list. For a web URL, the community’s chosen flow applies. Apps targeting a specific community may ignore the form value and provide their own optimized UX. Membership is granted by adding a p tag — no separate badge events needed.

Communities can create multiple profile lists for different access levels:

Each list carries its own metadata (name, image, content description) and optional application form.

Profile lists double as displayable membership badges in user profiles. The name and image tags provide the visual representation; the content field describes what the membership grants. A single event serves as both access control list and profile badge — no duplicate events needed.

• "Community" — How profile lists are referenced in community sections

• "List" — General list and set patterns (kind 30000)

• "Forms" — Form-based membership requests (kind 30168, 1069)