mirror of https://github.com/lukechilds/nips.git
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.
fiatjaf
7f7da50636
|
2 years ago | |
---|---|---|
01.md | 2 years ago | |
02.md | 2 years ago | |
03.md | 3 years ago | |
04.md | 3 years ago | |
05.md | 2 years ago | |
06.md | 3 years ago | |
07.md | 2 years ago | |
08.md | 3 years ago | |
09.md | 3 years ago | |
10.md | 2 years ago | |
11.md | 3 years ago | |
12.md | 3 years ago | |
13.md | 2 years ago | |
14.md | 2 years ago | |
15.md | 2 years ago | |
16.md | 2 years ago | |
README.md | 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.
- NIP-01: Basic protocol flow description
- NIP-02: Contact List and Petnames
- NIP-03: OpenTimestamps Attestations for Events
- NIP-04: Encrypted Direct Message
- NIP-05: Mapping Nostr keys to DNS-based internet identifiers
- NIP-06: Basic key derivation from mnemonic seed phrase
- NIP-07:
window.nostr
capability for web browsers - NIP-08: Handling Mentions
- NIP-09: Event Deletion
- NIP-10: Conventions for clients' use of
e
andp
tags in text events. - NIP-11: Relay Information Document
- NIP-12: Generic Tag Queries
- NIP-13: Proof of Work
- NIP-14: Subject tag in text events.
- NIP-15: End of Stored Events Notice
- NIP-16: Event Treatment
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 |
Please update this list when proposing NIPs introducing new event kinds.
Criteria for acceptance of NIPs
- They should be implemented somewhere at least as a prototype somewhere.
- They should make sense.
- Other rules will be made up when necessary.
License
All NIPs are public domain.