nostr/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2024-12-22 16:35:52 -05:00
Code Issues Actions Packages Projects Releases Wiki Activity

NIP-20: pow suggestion

Browse Source
This commit is contained in:
William Casarin 2022-11-10 12:02:14 -08:00
parent a0b0a021a8
commit e7f74d21c4
1 changed files with 5 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
20.md
View File

@ -23,6 +23,8 @@ The `message` SHOULD start with `blocked:` if the pubkey or network address has
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 doesn't meet some specific criteria (created_at is too far off, 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 `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.
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.
@ -61,6 +63,9 @@ Event rejected, `created_at` too far off
["OK", "b1a649ebe8...", false, "invalid: event creation date is too far off from the current time. Is your system clock in sync?"] ["OK", "b1a649ebe8...", false, "invalid: event creation date is too far off from the current time. Is your system clock in sync?"]
Event rejected, insufficient proof-of-work difficulty
["OK", "b1a649ebe8...", false, "pow: difficulty 26 is less than 30"]
Future Extensions Future Extensions