mirror of
https://github.com/nostr-protocol/nips.git
synced 2024-09-19 19:46:46 +00:00
24 lines
1.2 KiB
Markdown
24 lines
1.2 KiB
Markdown
|
NIP-22
|
||
|
|
======
|
||
|
|
|
||
|
|
Unacceptable Event `created_at` time
|
||
|
|
---------------------------
|
||
|
|
|
||
|
|
`draft` `optional` `author:jeffthibault`
|
||
|
|
|
||
|
|
Relays may support notifying clients that the event they published has an unacceptable `created_at` time. A relay will will consider the `created_at` time unacceptable if the `created_at` time is more than **[limit]** before the event was received by the relay.
|
||
|
|
|
||
|
|
If a relay supports this NIP, the relay SHOULD send the client a `NOTICE` message saying the event was not stored because the timestamp was too old.
|
||
|
|
|
||
|
|
Client Behavior
|
||
|
|
---------------
|
||
|
|
|
||
|
|
Clients SHOULD use the `supported_nips` field to learn if a relay supports event `created_at` checks.
|
||
|
|
|
||
|
|
Motivation
|
||
|
|
----------
|
||
|
|
|
||
|
|
The motivation for this NIP is to prevent clients from saying they published an event *significantly* earlier than they actually did.
|
||
|
|
|
||
|
|
The event `created_at` field is just a unix timestamp (integer) so one could set it to a time in the past. For example, the `created_at` field could be set to a time 10 years ago even though it was created today and it could still be a valid event. This NIP aims to set a maximum amount of time elapsed between when an event was created and when it was *actually* published.
|