Polygon Feature Requests (PFRs)
The guidance provided herein does not constitute a proscribed process and is not part of the PIP governance framework. It is intended to provide a helpful set of standards that any stakeholder in the Polygon ecosystem can use to put forward high-level ideas.
Overview
Anyone can author a PFR. The views/opinions expressed in the document are the author’s own and do not necessarily have any authority in the Polygon Ecosystem.
The PFR provides a template for stakeholders to identify problems and propose solutions to improve Polygon protocols. The general spirit of PFRs is to explore high-level, directional topics that can be discussed and informally reviewed by a wide range of stakeholders.
These documents aim to describe requirements early in the development cycle and, therefore, do not require full technical specifications. Once there is consensus on a general direction, the Polygon Improvement Proposal (PIP) framework can be used to specify the implementation of PFRs.
Due to the informal nature of PFRs, citation and quoting should be done with caution, as the documents can be subject to change or removal at any time.
Rational
A PFR-based convention can streamline the ideation and evaluation process for high-level directional discussions and protocol improvements, ensuring that good ideas can outcompete bad ones in an open marketplace of ideas. Thus, the ecosystem can better adapt to emerging challenges and opportunities.
Template
The template below covers all the key factors that should be considered by an author when drafting a Polygon Feature Request:
- Overview
- A short description of the feature and what it aims to solve.
- Rational
- Problem Statement - what is the specific problem or pain point this feature addresses?
- Proposal
- Proposed solution - How does the feature work? Provide details or mockups where possible.
- Considerations
- Benefits - provide context on all the benefits this feature will provide.
- Drawbacks/tradeoffs - provide context on all the potential tradeoffs and drawbacks of the proposed feature.
- References
- Adhering to formal academic citation standards is not required. Pragmatic, inline, and cross-linked references are encouraged.
- Copyright
- PFR authors are encouraged to waive all copyrights and related rights under CC0 1.0 Universal.
Feedback and Evolution
As authors of this document, we accept that it will not be perfect and may take several iterations to refine. We encourage and welcome you to provide any feedback you may have on PFRs in general.