You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
William Casarin 6903ff5b2c nip25: make generic like an explicit + 2 years ago
01.md Fix some typos and adds json type to code blocks 2 years ago
02.md update nip-02 to disallow `null`, only allow strings in tags. 2 years ago
03.md migrate nips from main nostr repo. 3 years ago
04.md migrate nips from main nostr repo. 3 years ago
05.md sneak filter.limit in nip-01. 2 years ago
06.md migrate nips from main nostr repo. 3 years ago
07.md publish NIP-07: window.nostr. 2 years ago
08.md migrate nips from main nostr repo. 3 years ago
09.md migrate nips from main nostr repo. 3 years ago
10.md nip10: fix small rendering bug on github 2 years ago
11.md migrate nips from main nostr repo. 3 years ago
12.md change NIP-12 so only single-letter tags are indexed. 2 years ago
13.md Proof of Work 2 years ago
14.md Nip-14 for subject tag 2 years ago
15.md nip15: clarify 2 years ago
16.md nip16: small fix 2 years ago
25.md nip25: make generic like an explicit + 2 years ago
README.md NIP-25: Reactions 2 years ago

README.md

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
7 Reaction 25

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

When experimenting with kinds, keep in mind the classification introduced by NIP-16.

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.