Jeff Thibault e8a501c08f
Merge pull request from Giszmo/nip22
reworded nip-22
2022-08-14 11:18:43 -04:00
2022-05-01 07:48:57 -03:00
2022-05-01 07:48:57 -03:00
2022-05-08 21:34:27 -03:00
2022-05-01 07:48:57 -03:00
2022-05-06 20:54:45 -03:00
2022-05-01 07:48:57 -03:00
2022-05-01 07:48:57 -03:00
2022-05-26 09:35:53 -07:00
2022-05-01 07:48:57 -03:00
2022-05-06 22:04:57 -03:00
2022-05-24 07:33:11 -05:00
2022-05-27 19:43:15 +03:00
2022-07-26 04:33:33 +03:00
2022-08-13 21:50:38 -04:00
2022-07-31 12:44:40 -07:00
2022-08-13 13:54:28 -04: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
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.

Description
A mirror for NIPS
Readme 20 MiB
Languages
Markdown 100%