Nervos Network RFCs

Nervos Network RFCs

Telegram Group

本资源库包含了与 Nervos Network 相关的提案、标准和文档。

RFC(请求评论)的过程旨在为新协议、改进内容和最佳实践提供一个开放的、社区驱动的路径,以便所有相关人员都能对 Nervos network 的发展方向充满信心。

发布在这里的 RFCs 暂时不会被成为正式的标准,直到它的状态切换成标准。


不是所有的 RFCs 都是标准,主要会分成两类:

  • Standards Track(标准协议) - 这部分 RFC 是 Nervos network 中协议、客户端和应用程序需要遵循的标准。
  • Informational(信息) - 任何和 Nervos network 相关的内容。


1The Nervos Network Positioning PaperThe Nervos TeamInformationalDraft
2Nervos CKB: A Common Knowledge Base for Crypto-EconomyJan XieInformationalDraft
3CKB-VMXuejie XiaoInformationalDraft
4CKB Block Synchronization ProtocolIan YangStandards TrackProposal
5Privileged architecture support for CKB VMXuejie XiaoInformationalDraft
6Merkle Tree for Static DataKe WangStandards TrackProposal
7P2P Scoring System And Network SecurityJinyang JiangStandards TrackProposal
8SerializationBoyu YangStandards TrackProposal
9VM SyscallsXuejie XiaoStandards TrackProposal
10Eaglesong (Proof-of-Work Function for Nervos CKB)Alan SzepieniecStandards TrackProposal
11Transaction FilterQuake WangStandards TrackProposal
12Node DiscoveryLinfeng Qian, Jinyang JiangStandards TrackProposal
13Block TemplateDingwei ZhangStandards TrackProposal
14VM Cycle LimitsXuejie XiaoStandards TrackProposal
15Crypto-Economics of the Nervos Common Knowledge BaseKevin Wang, Jan Xie, Jiasun Li, David ZouInformationalDraft
17Transaction valid sinceJinyang JiangStandards TrackProposal
19Data StructuresXuejie XiaoInformationalDraft
20CKB Consensus ProtocolRen ZhangInformationalDraft
21CKB Address FormatCipher WangStandards TrackProposal
22CKB Transaction StructureIan YangInformationalDraft
23Deposit and Withdraw in Nervos DAOJan Xie, Xuejie Xiao, Ian YangStandards TrackProposal


The RFC process attempts to be as simple as possible at beginning and evolves with the network.

1. 和社区讨论你的想法

Before submiting a RFC pull request, you should proposal the idea or document to Nervos RFCs Chatroom or Nervos RFCs Mailing List.

2. 提交你的 RFC

After discussion, please create a pull request to propose your RFC:

Copy 0000-template as rfcs/0000-feature-name, where feature-name is the descriptive name of the RFC. Don't assign an number yet.

Nervos RFCs should be written in English, but translated versions can be provided to help understanding. English version is the canonical version, check english version when there's ambiguity.

Nervos RFCs should follow the keyword conventions defined in RFC 2119, RFC 6919.

3. 审查 / 接受

The maintainers of RFCs and the community will review the PR, and you can update the RFC according to comments left in PR. When the RFC is ready and has enough supports, it will be accepted and merged into this repository.

An Informational RFC will be in Draft status once merged and published. It can be made Final by author at any time, or by RFC maintainers if there's no updates to the draft in 12 months.

4. (Standards Track) 提交你的标准

A Standards Track RFC can be in 1 of 3 statuses:

  1. Proposal (Default)
  2. Standard
  3. Obsolete

A Standards Track RFC will be in Proposal status intially, it can always be updated and improved by PRs. When you believe it's rigorous and mature enough after more discussions, you should create a PR to propose making it a Standard.

The maintainers of RFCs will review the proposal, ask if there's any objections, and discuss about the PR. The PR will be accepted or closed based on rough consensus in this early stage.


本资源库是符合 MIT 许可条款