An open repository for proposals, standards, and documentation governing the evolution of the Nervos Network blockchain.
Nervos Network RFCs is the official repository for the Request for Comments (RFC) process governing the Nervos blockchain. It is a collection of proposals, standards, and informational documents that define how the network evolves, including technical specifications for its consensus protocol, virtual machine, and economic model. It solves the problem of decentralized, transparent governance by providing a structured, community-driven path for proposing and accepting changes.
Blockchain core developers, protocol researchers, application builders, and community members who are contributing to or building on the Nervos Network and need to understand or influence its technical direction.
Developers and stakeholders choose this repository because it is the canonical, transparent source of truth for Nervos Network's technical evolution. It provides a clear, structured process for governance that fosters community consensus and ensures the network's development remains open and accountable.
This repository contains proposals, standards and documentations related to Nervos Network.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
The README emphasizes an 'open and community driven path' with discussion on Discord and Nervos Talk, ensuring all stakeholders can track evolution. This fosters trust and accountability in network upgrades.
It defines a clear RFC lifecycle with statuses like Draft, Proposal, and Active, as shown in the RFC table. This helps developers understand the maturity and adoption level of each standard.
RFCs must follow established keyword conventions from RFC 2119 and 6919, reducing ambiguity in requirements. This is explicitly stated in the process section for consistency.
It separates Standards Track for technical specs and Informational Track for background, as per the categories. This caters to both implementers needing precision and builders seeking context.
The README admits the process 'attempts to be as simple as possible at beginning and evolves,' leading to potential instability for contributors. Acceptance is based on 'rough consensus' which can be vague and slow.
While aiming for decentralization, RFC acceptance relies on maintainers and community review, with a centralized PR system. The README notes it's 'at this early stage,' implying governance isn't fully distributed yet.
It's exclusively for the Nervos Network, with no support for other blockchains. This limits its utility as a general governance tool, as evidenced by all RFCs being Nervos-specific.