REP stands for RSS3 Evolution Proposal, a detailed documentation proposed by the RSS3 Community.
This repository tracks all REPs proposed by the RSS3 Community.
| REP Number | Title | Proposer(s) | Type | Status |
|---|---|---|---|---|
| REP-1 | Purpose and Guidelines | henry@rss3.io | Process | Living |
| REP-11 | Protocol Upgrade | BruceXC, HenryQW, KallyDev, Nya Candy, polebug, pseudoyu, Thomas | Protocol | Final |
| REP-16 | Staking Rewards Taxation Adjustment | Albert, HenryQW | Core | Final |
| REP-20 | Data Availability Layer Integration | Albert, HenryQW | Core | Final |
| REP-26 | Chip Mechanism Upgrade | BruceXC | Core | Final |
| REP-33 | Node State Transition | KallyDev, BruceXC | Core | Final |
| REP-38 | Demotion and Slashing Mechanism | Polebug | Core | Draft |
| REP-40 | Whitepaper Updates | pseudoyu | Core | Candidate |
| REP-43 | Introducing Payment Processor for Request Fees | Nya Candy | Core | Review |
- Fork the repository by clicking the "Fork" button in the top right, then clone your fork.
- Duplicate
REPs/REP-Template.mdand rename it toREPs/REP-XXXX.md(whereXXXXis the next available Pull Request number). - Fill in the REP template with your proposal, remember to add links to relevant discussions on the RSS3 Forum.
- Run
npm run format. - Submit a Pull Request to RSS3 Network's
mainbranch.
RSS3 Evolution Proposals are collectively maintained by the RSS3 Community. All work under this repository is marked with CC0 1.0.
By marking the work with a CC0 public domain dedication, the creator is giving up their copyright and allowing reusers to distribute, remix, adapt, and build upon the material in any medium or format, even for commercial purposes.