Objective:
To establish clear, comprehensive guidelines for submitting Polygon Improvement Proposals (PIPs) that uphold the principles of user safety, network safety, brand protection, ethics, funds safety, security, and legal compliance.
1. Purpose of a PIP
A PIP is a design document providing information to the Polygon community or describing a new feature, process, or improvement for the Polygon ecosystem. The proposal should ensure alignment with the ecosystem’s goals while maintaining high standards for security, usability, and compliance.
2. General Requirements for Submission
All PIPs must:
- Clearly outline the problem or opportunity being addressed.
- Include a detailed solution proposal with technical, operational, and ethical considerations.
- Ensure alignment with Polygon’s mission and values.
- Be presented in a transparent, accessible, and inclusive manner.
3. User Safety
Proposals must:
Prioritize end-user protection, minimizing risks such as loss of funds, exposure to scams, or misinformation.
Include an assessment of potential user risks and mitigation strategies.
Define mechanisms to recover from potential errors or failures (e.g., rollbacks, safeguards).
4. Network Safety
Proposals should:
Avoid introducing vulnerabilities that could destabilize the Polygon network.
Include rigorous testing and auditing plans for technical implementations.
Assess the scalability and performance implications of the proposal.
5. Brand Protection
All PIPs must:
Respect Polygon’s reputation and brand integrity.
Avoid misleading marketing or naming conventions that could harm trust.
Be reviewed for alignment with Polygon’s values and community standards.
6. Ethics
Proposals must:
Be equitable, inclusive, and aligned with principles of fairness.
Avoid promoting activities that could harm individuals, communities, or the broader crypto ecosystem.
Include a statement on ethical considerations, particularly for proposals with social, financial, or environmental impacts.
7. Funds Safety
PIPs impacting user or protocol funds must:
Clearly define mechanisms to safeguard funds, such as multisignature wallets or smart contract audits.
Include plans for transparent fund allocation and use.
Outline procedures for dispute resolution or recovering misplaced/lost funds.
8. Security
Proposals must:
Undergo a security review process, including third-party audits if applicable.
Address risks related to smart contracts, APIs, and other technical dependencies.
Provide documentation on security measures to be implemented.
9. Legal Compliance
All PIPs must:
Adhere to applicable laws and regulations across jurisdictions where Polygon operates.
Include a legal compliance section outlining how the proposal complies with regulatory requirements.
Avoid facilitating illicit activities such as money laundering, fraud, or sanctions evasion.
By adhering to these guidelines, PIP contributors can ensure that their proposals are robust, well-considered, and contribute positively to the growth and security of the Polygon ecosystem.