Rocket Pool Improvement Proposals (RPIPs) describe standards for Rocket Pool, including core protocol specifications, high-level governance procedures, and contract standards.
Contributing
First review RPIP-1. Then clone the repository and add your RPIP to it. There is a template RPIP here. Then submit a Pull Request to Rocket Pool's RPIPs repository.
RPIP Statuses
- Draft - The first formally tracked stage of an RPIP in development. An RPIP is merged by an RPIP Editor into the RPIP repository when properly formatted.
- Review - An RPIP Author marks an RPIP as ready for and requesting review.
- Final - This RPIP represents the final standard. A Final RPIP exists in a state of finality and should only be updated to correct errata and add non-normative clarifications.
- Stagnant - Any RPIP in Draft or Review which becomes inactive is moved to Stagnant. An RPIP may be resurrected from this state by Authors or RPIP Editors through moving it back to Draft.
- Withdrawn - The RPIP Author(s) have withdrawn the proposed RPIP. This state has finality and can no longer be resurrected using this RPIP number. If the idea is pursued at later date, it is considered a new proposal.
- Living - An RPIP that is designed to be continually updated and not reach a state of finality.
- Obsolete - An Obsolete RPIP has been replaced, superseded or removed.
RPIP Types
RPIPs are separated into a number of types, and each has its own list of RPIPs.
Protocol (24)
Describes any change that affects the core Rocket Pool protocol as is currently defined via the smart contract implementations. Protocol RPIPs can be broken down into the following categories:
Core (21)
Improvements relevant to core protocol design which require core contract changes (e.g. RPIP-5).
RPRC (2)
Application-level standards and conventions, including non-core contract standards (e.g. RPIP-3).
Meta (20)
Describes a process surrounding Rocket Pool or proposes a change to (or an event in) a process. Meta RPIPs are like Core Protocol RPIPs but apply to areas other than the Rocket Pool protocol itself. They may propose an implementation, but not to Rocket Pool’s codebase; they often require community consensus. Examples include procedures, guidelines, and changes to the community decision-making process (i.e. governance).
Informational (8)
Describes a Rocket Pool design issue, or provides general guidelines or information to the Rocket Pool community, but does not propose a new feature.
Note that there is no Type reserved for Smart Node changes. Improvements to the Smart Node are not part of the RPIP process and are best discussed via an Issue and/or PR on the rocket-pool/smartnode repository.