nostr/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2024-09-16 02:03:39 +00:00
Code Issues Packages Projects Releases Wiki Activity
Nostr Implementation Possibilities
13 Commits 53 Branches 0 Tags 8.5 MiB
Markdown 100%
ad1eb96c21
Go to file
William Casarin ad1eb96c21 kind: recommend relay 
Signed-off-by: William Casarin <jb55@jb55.com>
2022-05-06 22:04:57 -03: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
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 change ~mandatory~ to optional, add NIP-10 to README 2022-05-05 11:06:03 -05: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
README.md kind: recommend relay 2022-05-06 22:04:57 -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
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.