NIP-20: server errors happen!

This commit is contained in:
William Casarin 2022-11-10 13:14:23 -08:00
parent ff26b959f8
commit c510e646d0

6
20.md
View File

@ -27,6 +27,8 @@ The `message` SHOULD start with `pow:` if the event doesn't meet some proof-of-w
The `message` SHOULD start with `rate-limited:` if the event was rejected due to rate limiting techniques. The `message` SHOULD start with `rate-limited:` if the event was rejected due to rate limiting techniques.
The `message` SHOULD start with `error:` if the event failed to save due to a server issue.
Ephemeral events are not acknowledged with OK responses, unless there is a failure. Ephemeral events are not acknowledged with OK responses, unless there is a failure.
If the event or `EVENT` command is malformed and could not be parsed, a NOTICE message SHOULD be used instead of a command result. This NIP only applies to non-malformed EVENT commands. If the event or `EVENT` command is malformed and could not be parsed, a NOTICE message SHOULD be used instead of a command result. This NIP only applies to non-malformed EVENT commands.
@ -67,6 +69,10 @@ Event rejected, insufficient proof-of-work difficulty
["OK", "b1a649ebe8...", false, "pow: difficulty 26 is less than 30"] ["OK", "b1a649ebe8...", false, "pow: difficulty 26 is less than 30"]
Event failed to save,
["OK", "b1a649ebe8...", false, "error: could not connect to the database"]
Client Handling Client Handling