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：基本协议流程描述
- NIP-02：联系人列表和昵称
- NIP-03：事件的OpenTimestamps证明
- NIP-04：加密的直接消息
- NIP-05：将Nostr键映射到基于DNS的Internet标识符
- NIP-06：基于助记种子短语的基本密钥派生
- NIP-07：Web浏览器的window.nostr功能
- NIP-08：处理提及
- NIP-09：事件删除
- NIP-10：客户端在文本事件中使用e和p标签的约定
- NIP-11：中继器信息文件
- NIP-12：通用标签查询
- NIP-13：工作证明
- NIP-14：文本事件中的主题标签
- NIP-15：存储事件通知结束
- NIP-16：事件处理
- NIP-19：bech32编码实体
- NIP-20：命令结果
- NIP-21：nostr：URL方案
- NIP-22：事件创建_at限制
- NIP-25：反应
- NIP-26：委托事件签名
- NIP-28：公共聊天
- NIP-33：参数化可替换事件
- NIP-36：敏感内容
- NIP-40：过期时间戳
- NIP-42：客户端向中继器的身份验证
- NIP-50：关键字过滤器
- NIP-56：报告
- NIP-65：中继器列表元数据
| kind | description | NIP |
|---|---|---|
| 0 | 元数据 | 1, 5 |
| 1 | 短文本笔记 | 1 |
| 2 | 推荐中继 | 1 |
| 3 | 联系人 | 2 |
| 4 | 加密直接消息 | 4 |
| 5 | 事件删除 | 9 |
| 7 | 反应 | 25 |
| 40 | 频道创建 | 28 |
| 41 | 频道元数据 | 28 |
| 42 | 频道消息 | 28 |
| 43 | 隐藏频道消息 | 28 |
| 44 | 频道静音用户 | 28 |
| 45-49 | 公共聊天保留 | 28 |
| 1984 | 报告 | 56 |
| 10002 | 中继列表元数据 | 65 |
| 22242 | 客户端认证 | 42 |
| 1000-9999 | 普通事件 | 16 |
| 10000-19999 | 可替换事件 | 16 |
| 20000-29999 | 临时事件 | 16 |
| 30000-39999 | 参数化可替换事件 | 33 |
| 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 |
| AUTH | used to send authentication events | 42 |
| 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 |
| AUTH | used to send authentication challenges | 42 |
Please update these lists when proposing NIPs introducing new event kinds.
When experimenting with kinds, keep in mind the classification introduced by NIP-16.
| name | value | other parameters | NIP |
|---|---|---|---|
| e | event id (hex) | relay URL, marker | 1, 10 |
| p | pubkey (hex) | relay URL | 1 |
| r | a reference (URL, etc) | 12 | |
| t | hashtag | 12 | |
| g | geohash | 12 | |
| nonce | random | 13 | |
| subject | subject | 14 | |
| d | identifier | 33 | |
| expiration | unix timestamp (string) | 40 |
- They should be implemented in at least two clients and one relay -- when applicable.
- They should make sense.
- They should be optional and backwards-compatible: care must be taken such that clients and relays that choose to not implement them do not stop working when interacting with the ones that choose to.
- There should be no more than one way of doing the same thing.
- Other rules will be made up when necessary.
All NIPs are public domain.