Kind 30002: Relay Sets

Overview

Relay Sets events (kind 30002) allow users to create and manage categorized groups of relays for different purposes. This parameterized replaceable event kind enables users to define multiple relay groups that they can easily select from during various operations. Unlike the standard Read/Write Relays (kind 10002), Relay Sets allow for more granular organization of relays by specific use cases, topics, or functions.

Specification

Property	Value
Kind Number	30002
Event Range	Parameterized Replaceable
Defined in	NIP-51

Content Format

The content field can contain encrypted private relay entries using NIP-04 encryption. The encrypted content follows the same structure as the public tags but is only visible to the creator. It can also contain a description or notes about the relay set.

Schema

For encrypted private relay entries:

"content": "<NIP-04 encrypted JSON array of tags>"

For descriptive content:

"content": "This relay set is for Bitcoin-focused content and discussion."

Tags

Tag Name	Description	Format	Required
d	Set identifier	["d", "<set-name>"]	Yes
relay	Relay URL with read/write flags	["relay", "<url>", "<read-flag>", "<write-flag>"]	Yes
title	Human-readable title	["title", "<title-text>"]	No
description	Description of the set	["description", "<description-text>"]	No
image	Image URL for the set	["image", "<image-url>"]	No

Client Behavior

Clients should:

1. Allow users to create, view, and manage multiple relay sets
2. Use the d tag parameter to distinguish between different relay sets
3. Display the set's title, description, and image when available
4. Provide a UI for selecting relay sets for different operations
5. When a relay set is selected:
   • Connect to relays with "read" flag for reading content
   • Publish to relays with "write" flag when creating content
6. Support switching between relay sets contextually
7. Consider providing UI for importing relay sets from other users
8. When processing encrypted relay entries, decrypt using NIP-04 and the user's keys
9. Maintain the order of relays as specified in the event

Relay Behavior

Relays should:

1. Handle kind 30002 events as parameterized replaceable events with the d tag as discriminator
2. Store these events to allow clients to retrieve the user's relay sets
3. Not attempt to interpret or enforce relay set selection (this is client-side functionality)

Use Cases

• Creating topic-specific relay groups (e.g., "Bitcoin Relays", "Art Relays")
• Defining geographic relay sets (e.g., "EU Relays", "Asia Relays")
• Managing relays for different social contexts (e.g., "Work", "Friends", "Family")
• Building specialized relay sets for specific functions
• Supporting workflow-specific relay configurations
• Creating relay redundancy for important content
• Enabling context-switching between relay environments

Example

{
  "id": "ce83925c097ef69dd4c1876ea754e173028fff68fc101f0f0eae78ae434cc772",
  "pubkey": "854043ae8f1f97430ca8c1f1a090bdde6488bd5115c7a45307a2a212750ae4cb",
  "created_at": 1699597889,
  "kind": 30002,
  "tags": [
    ["d", "bitcoin-relays"],
    ["title", "Bitcoin Discussion Relays"],
    ["description", "Relays focused on Bitcoin content and discussions"],
    ["image", "https://example.com/bitcoin-icon.png"],
    ["relay", "wss://nostr.bitbang.social", "read", "write"],
    ["relay", "wss://nostr.bitcoiner.social", "read", "write"],
    ["relay", "wss://filter.nostr.bitcoin.faith", "read", ""]
  ],
  "content": "My curated set of Bitcoin-focused relays with good content and minimal noise.",
  "sig": "a9a4e2192eede77e6c9d24ddfab95ba3ff7c03fbd07ad011fff245abea431fb4d3787c2d04aad001cb039cb8de91d83ce30e9a94f82ac3c5a2372aa1294a96bd"
}

Relay Flags

In the relay tags, the read/write flags indicate the recommended usage:

• read: When present, indicates the relay should be used for reading content
• write: When present, indicates the relay should be used for publishing content

These flags can be used in various combinations:

• ["relay", "wss://example.com", "read", "write"] - Use for both reading and writing
• ["relay", "wss://example.com", "read", ""] - Use for reading only
• ["relay", "wss://example.com", "", "write"] - Use for writing only
• ["relay", "wss://example.com", "", ""] - Not currently used (unusual)

References

• NIP-51: Lists
• NIP-65: Relay List Metadata
• NIP-04: Encrypted Direct Messages

Related Kinds

• Kind 10002: Relay List Metadata - Standard relay list
• Kind 10006: Blocked Relays - Relays clients should never connect to
• Kind 10007: Search Relays - Relays optimized for search queries

Notes

• Relay Sets are parameterized lists, allowing users to have multiple sets with different d tag values
• The d tag is required for parameterized replaceable events to work correctly
• Relay URLs should follow the format wss://hostname[:port] or ws://hostname[:port]
• Multiple relay sets can co-exist, each with a different d value
• Title, description, and image tags help with UI presentation and set identification
• This kind allows for more granular and contextual relay management than the standard kind 10002
• Clients might implement UI for quickly switching between relay sets (e.g., dropdown selectors)