This repository is the home of all RDDL Improvement Proposals (REPs), along with ideas for new ones and discussions around proposed or existing ones. The process to add or change a REP is the following:
- The REP life-cycle SHOULD follow the life-cycle defined in REP-2 (our variant of COSS).
- Non-cosmetic changes are allowed only on raw and draft specifications.
Short Name | Title | Type | Status | Editor |
---|---|---|---|---|
REP-1 | Collective Code Construction Contract | meta | stable | Jürgen Eckel |
REP-2 | Consensus-Oriented Specification System | meta | stable | Jürgen Eckel |
REP-3 | How to handle ALL pull requests | meta | stable | Jürgen Eckel |
REP-4 | HW-03 Requirements | standard | draft | Jürgen Eckel |
REP-5 | Machine Registry | standard | stable | Jürgen Eckel |
REP-6 | Machine Authentication - EdDSA | standard | raw | Jürgen Eckel |
REP-7 | Trust Anchor | standard | raw | Jürgen Eckel |
REP-8 | Trust Anchor Registry | standard | stable | Jürgen Eckel |
REP-9 | Hardware Compatibility | standard | stable | Jürgen Eckel |
REP-10 | Hardware Approval Process | standard | stable | Jürgen Eckel |
REP-11 | Proof of Productivity | standard | stable | Jürgen Eckel |
REP-12 | On-Chain Governance | standard | stable | Jürgen Eckel |
REP-14 | Security Concepts (Ante Handler vs Msg Server) | standard | draft | Lorenz Herzberger |
REP-16 | Quality Assurance - Exceeding the scope of unit testing | standard | draft | Jürgen Eckel |