Kind 10: Group Chat Threaded Reply

Overview

Kind 10 events represent threaded replies in group chat contexts. This kind is part of the relay-based groups system defined in NIP-29. It allows for organized conversation threads within group chats, similar to how threading works in forum or chat applications.

Note: As mentioned in NIP-29, this kind is deprecated in favor of the more comprehensive relay-based groups system.

Specification

Property	Value
Kind Number	10
Event Range	Regular
Defined in	NIP-29
Status	Deprecated

Content Format

The content field contains the message text of the reply. It can be plain text or include markdown formatting, though specific formatting support depends on client implementation.

Schema

"content": "This is a reply to a message in the group chat thread."

Tags

Tag Name	Description	Format	Required
h	Group identifier	["h", "<group-id>"]	Yes
e	Event being replied to	["e", "<event-id>", "<relay-url>", "<marker>"]	Yes
previous	Timeline references	["previous", "<event-id-prefix>"]	Recommended

Client Behavior

Clients should:

1. Display threaded replies in a hierarchical or nested format to indicate the reply relationship
2. Include appropriate tags when creating threaded replies
3. Include timeline references as per NIP-29 recommendations (at least 3 references)
4. Check that replies have appropriate timeline references when displaying content

Relay Behavior

Relays should:

1. Verify the sender has permission to post in the group
2. Reject events that contain timeline references to events not in their database
3. Prevent late publication (messages with timestamps from the distant past)
4. Apply any group-specific moderation rules

Use Cases

• Creating organized discussion threads within group chats
• Replying to specific messages in a conversation
• Maintaining context in busy group chat environments

Example

{
  "id": "4376c65d2f232afbe9b882a35baa4f6fe8667c4e684749af565f981833ed6a65",
  "pubkey": "79dff8f82963424e0bb02708a22e44b4980893e3a4be0fa3cb60a43b946764e3",
  "created_at": 1671217411,
  "kind": 10,
  "tags": [
    ["h", "pizza-lovers-123"],
    ["e", "fe964e758903fc8186283d82b5f7029f0478d9daf9ea9a9ee8f7d620c4c99e98", "wss://groups.example.com"],
    ["previous", "a6c49604"],
    ["previous", "e8b10582"],
    ["previous", "9f27804c"]
  ],
  "content": "I totally agree, Hawaiian pizza is actually quite delicious!",
  "sig": "908a15e46fb4d8675bab026fc230a0e3542bfade63da02d542fb78b2a8513fcd0092619a2c8c1221e581946e0191f2af505dfdf8657a414dbca329186f009262"
}

References

• NIP-29: Relay-based Groups
• NIP-10: Text Notes and Threads (for general threading concepts)

Related Kinds

• Kind 9: Chat Message - Simple chat messages
• Kind 40-42: Public Chat - More structured public chat system

Notes

• This kind is marked as deprecated in NIP-29 documentation and the more comprehensive relay-based groups system should be used instead.
• The previous tag is a timeline reference mechanism to prevent messages from being broadcast to external relays out of context.
• Relays are expected to reject events that contain timeline references to events not in their database.