nostr/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2024-12-22 00:25:50 -05:00
Code Issues Actions Packages Projects Releases Wiki Activity
A mirror for NIPS
4 Commits 65 Branches 0 Tags 8 MiB
Markdown 100%
39c7f54db6
Go to file
Robert C. Martin 39c7f54db6 mend
2022-05-04 12:00:51 -05:00
01.md migrate nips from main nostr repo. 2022-05-01 07:48:57 -03:00
02.md migrate nips from main nostr repo. 2022-05-01 07:48:57 -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 migrate nips from main nostr repo. 2022-05-01 07:48:57 -03:00
06.md migrate nips from main nostr repo. 2022-05-01 07:48:57 -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
11.md migrate nips from main nostr repo. 2022-05-01 07:48:57 -03:00
12.md migrate nips from main nostr repo. 2022-05-01 07:48:57 -03:00
e-and-p-tags.md mend 2022-05-04 12:00:51 -05:00
README.md add criteria for acceptance. 2022-05-02 09:30:30 -03:00

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 5
1 Text 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.