lukechilds
/
nips
mirror of https://github.com/lukechilds/nips.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
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.
88 Commits
9 Branches
0 Tags
193 KiB
 
Tree: c274c65856
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'c274c65856'
${ noResults }
Mike Dilger c274c65856
Reword NIP-01 to clarify no line breaks. Existing language of "indentation" implies line breaks. 		2 years ago
01.md Reword NIP-01 to clarify no line breaks. Existing language of "indentation" implies line breaks. 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 stronger wording for relay deletion behavior 2 years ago
10.md Update 10.md 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: clarify about the signers of replaceable events 2 years ago
20.md NIP-20: server errors happen! 2 years ago
22.md add Giszmo, add comment in code example 2 years ago
25.md nip25: fix code example 2 years ago
26.md Changes based on feedback 2 years ago
28.md NIP-28: Public Chat (#38) 2 years ago
README.md NIP-20: Command Results 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
40 Channel Creation 28
41 Channel Metadata 28
42 Channel Message 28
43 Channel Hide Message 28
44 Channel Mute User 28
45-49 Public Chat Reserved 28
10000-19999 Replaceable Events Reserved 16
20000-29999 Ephemeral Events Reserved 16

Message types

Client to Relay

type description NIP
EVENT used to publish events 1
REQ used to request events and subscribe to new updates 1
CLOSE used to stop previous subscriptions 1

Relay to Client

type description NIP
EVENT used to send events requested to clients 1
NOTICE used to send human-readable messages to clients 1
EOSE used to notify clients all stored events have been sent 15
OK used to notify clients if an EVENT was successuful 20

Please update these lists 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.