mirror of
https://github.com/nostr-protocol/nips.git
synced 2025-03-16 21:20:29 -04:00
b616aefbf2
A proposed recommendation for using 'e' and 'p' tags in nostr clients.
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.
Languages
Markdown
100%