NIP-7D: Forum Threads
NIP-7D defines simple forum threads: a kind 11 root thread with a title, and NIP-22 kind 1111 comments as replies, avoiding deep arbitrary reply trees.
Forums need a root topic, not only social replies
A forum thread is different from a note that happens to get replies. It needs a topic, a title and a reply model that keeps discussion attached to the root. NIP-7D gives that shape with kind 11 threads.
Replies use NIP-22 kind 1111 comments. The NIP recommends replying to the root kind 11 event rather than building arbitrary nested reply hierarchies. That keeps forum clients readable.
This is deliberately small. It does not define a whole community system, moderation model or voting system. It defines the thread object.
Kind 11 roots and kind 1111 comments
A thread is kind 11. It should include a title tag and can carry opening content. A reply is a NIP-22 comment, kind 1111, pointing back to the root thread with uppercase root tags.
The example uses K and E tags to identify the root kind and event. The NIP's simplicity is the main feature: clients can build a forum list, open a thread and display comments without mapping the entire social graph.
Because it relies on NIP-22, NIP-7D belongs near comments, forums and community pages.
Forum threads were broken out from group work
hodlbod broke chat and threads out from NIP-29 in November 2024. In April 2025, fiatjaf changed subject to title. In May 2026, sanity cleanup touched the file.
That history explains why NIP-7D feels small. It is not trying to carry all group behavior; it is the thread primitive separated from the broader group protocol.
For readers, the important point is that forum threads are a basic discussion shape that can be combined with other moderation or community standards.
The UI should keep replies attached to the root
A forum client should show thread title, root content, author, reply count and kind 1111 comments. It should avoid turning the view into an endlessly nested social reply tree unless it has a clear forum reason.
NIP-7D can sit beside NIP-29 groups, NIP-72 legacy communities or standalone forum clients. The same thread object can be indexed and displayed by several contexts.
A clean implementation lets a user discover threads by title, open one discussion and reply without learning event-kind mechanics.
Small thread objects still need moderation context
A thread can be spammed, brigaded or duplicated. NIP-7D does not solve moderation; it gives the discussion object that other systems can moderate.
If clients disagree on reply scoping, a forum can fragment. Implementers should follow NIP-22 root tagging carefully.
Direct sources
The links below are part of the article, not decoration. Start with the official NIP, then read the file history, implementation references and adjacent standards before treating the page as product guidance.
