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.
Robert C. Martin
99c5425c42
|
3 years ago | |
|---|---|---|
| 01.md | 3 years ago | |
| 02.md | 3 years ago | |
| 03.md | 3 years ago | |
| 04.md | 3 years ago | |
| 05.md | 3 years ago | |
| 06.md | 3 years ago | |
| 08.md | 3 years ago | |
| 09.md | 3 years ago | |
| 11.md | 3 years ago | |
| 12.md | 3 years ago | |
| README.md | 3 years ago | |
| e-and-p-tags.md | 3 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-08: Handling Mentions
- NIP-09: Event Deletion
- NIP-11: Relay Information Document
- NIP-12: Generic Tag Queries
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
- 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.