Step 1 of 5
Start a thread
A thread is a kind 11 event. The content is the opening post, written like any note.
NIP-7D
Forum Threads
DraftEvents
Forum-style discussions: a kind 11 event with a title starts a thread, and every reply is a NIP-22 comment pointing at that thread.
At a glance
- Status
- In use and still allowed to change.
- Kinds
- Tags
- E
- K
- title
- Last changed
- May 28, 2026
Try it
Edit the form or the JSON: both stay in sync, the badge says whether the result is valid, and tapping any field explains it.
How the parts connect: A forum discussion
Not signed yet · Demo keys only. These personas' secret keys are public on purpose.
Explain
Select any field in the form or the JSON to see what it does.
How this NIP works
In the course
No course chapter covers this NIP yet. The editor above is the quickest way in.
Related NIPs
Builds on
- NIP-22 Comment
Replies to threads are NIP-22 kind 1111 comments.
- NIP-01 Basic protocol flow description
Threads are ordinary signed events from NIP-01.
See also
- NIP-C7 Chats
NIP-C7 is the chat-style counterpart: short messages instead of titled threads.
Specification
Specification text is quoted in English from the nostr-protocol/nips repository. Our explanations and the interface are translated. Source on GitHub at commit 0046368
Read the spec76 words, quoted from the repository at commit 0046368.
A thread is a kind 11 event. Threads SHOULD include a title.
{
"kind": 11,
"content": "Good morning",
"tags": [
["title", "GM"]
]
}
Replies to kind 11 MUST use NIP-22 kind 1111 comments. Replies should
always be to the root kind 11 to avoid arbitrarily nested reply hierarchies.
{
"kind": 1111,
"content": "Cool beans",
"tags": [
["K", "11"],
["E", <event-id>, <relay-url>, <pubkey>]
]
}