mirror of
https://github.com/nostr-protocol/nips.git
synced 2024-12-22 16:35:52 -05:00
NIP-20: More clarity around malformed vs invalid events
This commit is contained in:
parent
7569773ad6
commit
ff26b959f8
4
20.md
4
20.md
|
@ -21,7 +21,7 @@ The `message` SHOULD provide additional information as to why the command succee
|
||||||
|
|
||||||
The `message` SHOULD start with `blocked:` if the pubkey or network address has been blocked, banned or is not on a whitelist.
|
The `message` SHOULD start with `blocked:` if the pubkey or network address has been blocked, banned or is not on a whitelist.
|
||||||
|
|
||||||
The `message` SHOULD start with `invalid:` if the event doesn't meet some specific criteria (created_at is too far off, etc)
|
The `message` SHOULD start with `invalid:` if the event is invalid or doesn't meet some specific criteria (created_at is too far off, id is wrong, signature is wrong, etc)
|
||||||
|
|
||||||
The `message` SHOULD start with `pow:` if the event doesn't meet some proof-of-work difficulty. The client MAY consult the relay metadata at this point to retrieve the required posting difficulty.
|
The `message` SHOULD start with `pow:` if the event doesn't meet some proof-of-work difficulty. The client MAY consult the relay metadata at this point to retrieve the required posting difficulty.
|
||||||
|
|
||||||
|
@ -29,7 +29,7 @@ The `message` SHOULD start with `rate-limited:` if the event was rejected due to
|
||||||
|
|
||||||
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 is malformed and could not be parsed, a NOTICE message SHOULD be used instead of a command result.
|
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.
|
||||||
|
|
||||||
|
|
||||||
Examples
|
Examples
|
||||||
|
|
Loading…
Reference in New Issue
Block a user