Nostr Implementation Possibilities
Go to file
2022-07-10 15:33:07 -03:00
01.md Fix some typos and adds json type to code blocks 2022-06-21 08:07:05 -03:00
02.md update nip-02 to disallow null, only allow strings in tags. 2022-06-09 15:40:13 -03:00
03.md migrate nips from main nostr repo. 2022-05-01 07:48:57 -03:00
04.md migrate nips from main nostr repo. 2022-05-01 07:48:57 -03:00
05.md sneak filter.limit in nip-01. 2022-05-08 21:34:27 -03:00
06.md migrate nips from main nostr repo. 2022-05-01 07:48:57 -03:00
07.md publish NIP-07: window.nostr. 2022-05-06 20:54:45 -03:00
08.md migrate nips from main nostr repo. 2022-05-01 07:48:57 -03:00
09.md migrate nips from main nostr repo. 2022-05-01 07:48:57 -03:00
10.md nip10: fix small rendering bug on github 2022-05-26 09:35:53 -07:00
11.md migrate nips from main nostr repo. 2022-05-01 07:48:57 -03:00
12.md change NIP-12 so only single-letter tags are indexed. 2022-07-10 15:33:07 -03:00
13.md Proof of Work 2022-05-06 22:04:57 -03:00
14.md Nip-14 for subject tag 2022-05-24 07:33:11 -05:00
15.md nip15: clarify 2022-05-27 19:43:15 +03:00
16.md nip16: kind ranges instead of tags 2022-05-27 19:56:31 +03:00
README.md note kind 0 is on nip 1 too. 2022-06-20 14:51:21 -03:00

NIPs

NIPs stand for Nostr Implementation Possibilities. They exist to document what MUST, what SHOULD and what MAY be implemented by Nostr-compatible relay and client software.

Event Kinds

kind description NIP
0 Metadata 1, 5
1 Text 1
2 Recommend Relay 1
3 Contacts 2
4 Encrypted Direct Messages 4
5 Event Deletion 9

Please update this list when proposing NIPs introducing new event kinds.

Criteria for acceptance of NIPs

  1. They should be implemented somewhere at least as a prototype somewhere.
  2. They should make sense.
  3. Other rules will be made up when necessary.

License

All NIPs are public domain.