Build on Polkadot
Request of Commit (RFC)
With the release of Polkadot runtime 1.0, Polkadot's codebase is in the hands of the community. Anyone can open a Request For Commit (RFC) to propose and discuss changes to the network protocol, runtime logic, and public interfaces, and other technical matters.
To submit an RFC, follow the instructions here.
RFCs can only be approved and merged by III-Dan members of
Polkadot Technical Fellowship via
on-chain voting mechanism. Definitive approval or rejection is done by issuing the
RFC_APPROVE(xxxx, h) or RFC_REJECT(xxxx, h) on-chain remark from the Fellowship origin on the
Polkadot Collectives parachain, where xxxx is the RFC number and h is the hash of the raw
proposal text.
For example, the first RFC RFC-1 about Agile Coretime was proposed by Gavin Wood on the 30th of June 2023 and merged on the 12th of August 2023. Subsequently, the code for the Agile Coretime Broker pallet was added to the Substrate FRAME system.
Polkadot SDK
For more information about building on Polkadot, see the Builder's Guide.
The Polkadot Software Development Kit (SDK) includes all the tools needed to build on the Polkadot ecosystem. The main repositories include:
- Implementation of a node for the Polkadot network in Rust, using the Substrate framework
- The Substrate SDK
- Cumulus - Parachain Development Kit
The programming language used for development is Rust.