Step 1 of 4
Now part of NIP-01
The kind ranges are defined in NIP-01's Kinds section.
NIP-16
Event Treatment
MergedBehaviour
Deprecated: merged into NIP-01. It introduced replaceable and ephemeral kind ranges that change how relays store events.
At a glance
- Status
- Folded into another NIP; kept only so old links work.
- Last changed
- Nov 16, 2023
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 this NIP works
Who does what
Step 1 of 6
Ready. Press play or step forward to send the first message.
Text version
| # | From | To | Message |
|---|---|---|---|
| 1 | Alice's client | Relay | Alice publishes kind 0. |
| 2 | Alice's client | Relay | Later she publishes a newer kind 0. |
| 3 | Relay | Relay | Same pubkey and kind, newer created_at: the relay drops v1. |
| 4 | Alice's client | Relay | A kind in 20000–29999, such as a typing indicator. |
| 5 | Relay | Bob's client | Live subscribers get it; nothing is stored. |
In the course
No course chapter covers this NIP yet. The editor above is the quickest way in.
Related NIPs
Replaced by
- NIP-01 Basic protocol flow description
These rules live in NIP-01 now.
Used by
See also
- NIP-33 Parameterized Replaceable Events
Addressable events (30000–39999), also merged into NIP-01.
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 spec10 words, quoted from the repository at commit 0046368.
Moved to NIP-01.