From 15514283f3a5c51e21e596ff413da2ccc4a70b6e Mon Sep 17 00:00:00 2001 From: William Casarin Date: Thu, 10 Nov 2022 10:07:13 -0800 Subject: NIP-20: Command Results When submitting events to relays, clients currently have no way to know if an event was successfully committed to the database. This NIP introduces the concept of command results which are like NOTICE's except provide more information about if an event was accepted or rejected. --- README.md | 2 ++ 1 file changed, 2 insertions(+) (limited to 'README.md') diff --git a/README.md b/README.md index d974dd3..8b3a994 100644 --- a/README.md +++ b/README.md @@ -18,6 +18,7 @@ NIPs stand for **Nostr Implementation Possibilities**. They exist to document wh - [NIP-14: Subject tag in text events.](14.md) - [NIP-15: End of Stored Events Notice](15.md) - [NIP-16: Event Treatment](16.md) +- [NIP-20: Command Results](20.md) - [NIP-22: Event created_at Limits](22.md) - [NIP-25: Reactions](25.md) - [NIP-28: Public Chat](28.md) @@ -58,6 +59,7 @@ NIPs stand for **Nostr Implementation Possibilities**. They exist to document wh | EVENT | used to send events requested to clients | [1](01.md) | | NOTICE | used to send human-readable messages to clients | [1](01.md) | | EOSE | used to notify clients all stored events have been sent | [15](15.md) | +| OK | used to notify clients if an EVENT was successuful | [20](20.md) | Please update these lists when proposing NIPs introducing new event kinds. -- cgit v1.2.3