Step 1 of 4
This NIP now lives in NIP-01
NIP-20 was folded into NIP-01, so every relay is expected to answer with OK. Read NIP-01 for the current rules; this page keeps the walkthrough for old links.
NIP-20
MergedBehaviour
Deprecated: now part of NIP-01. Defined the OK message a relay sends back after you publish an event, saying whether it was stored and, if not, why.
Edit the form or the JSON: both stay in sync, the badge says whether the result is valid, and tapping any field explains it.
Select any field in the form or the JSON to see what it does.
Step 1 of 4
NIP-20 was folded into NIP-01, so every relay is expected to answer with OK. Read NIP-01 for the current rules; this page keeps the walkthrough for old links.
Ready. Press play or step forward to send the first message.
| # | From | To | Message |
|---|---|---|---|
| 1 | Client | Relay | Alice's client publishes a signed note to the relay. |
| 2 | Relay | Relay | The relay checks the id and signature, then its own rules: size limits, spam filters, membership, proof of work. |
| 3 | Relay | Client | Stored. The client can mark the note as published on this relay. |
| 4 | Relay | Client | Refused, with a prefixed reason. Here the client is sending too fast and should back off and retry later. |
No course chapter covers this NIP yet. The editor above is the quickest way in.
The OK message and its prefixes are now defined in NIP-01.
NIP-42 adds the "auth-required:" prefix for relays that need you to log in first.
NIP-13 proof of work is what the "pow:" prefix is about.
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
Moved to NIP-01.