How to Write and Submit Polygon Improvement Proposals (PIPs)?

Overseeing advancements and enhancements on the Polygon network requires a structured approach through Polygon Improvement Proposals (PIPs).

PIPs are necessary for suggesting and discussing changes, updates, and new features within the Polygon ecosystem.

To contribute effectively to the development of Polygon, individuals must understand the process of creating and submitting PIPs.

This guide will outline the steps involved in writing and submitting Polygon Improvement Proposals, empowering users to engage in the network’s growth and evolution.

What are Polygon Improvement Proposals (PIPs)?

Polygon Improvement Proposals (PIPs) are a structured framework within the blockchain network of Polygon that facilitates and coordinates upgrades based on community feedback.

The primary goal of the PIP framework is to provide a platform for the developer community to propose new features, gather technical feedback, and enhance self-governance.

Through a transparent and versioned repository, PIPs aim to increase accountability by maintaining a historical record of all feature proposals, including their revision history and implementation progress.

This mechanism encourages inclusion and consensus-building within the Polygon ecosystem.

How to Write Polygon Improvement Proposals?

Familiarizing Yourself with PIP Standards

Standards are crucial when it comes to writing and submitting Polygon Improvement Proposals (PIPs). Before entering into the process, take the time to thoroughly understand the PIP standards outlined in the official PIP repository. Familiarize yourself with the template, structure, and guidelines to ensure your proposal meets the necessary requirements for consideration.

Identifying Areas for Improvement

Some of the most successful PIPs address specific areas within the Polygon ecosystem that could be enhanced or optimized. When identifying areas for improvement, consider factors such as scalability, security, usability, and community impact. Dive deep into the Polygon network to pinpoint potential upgrades or modifications that could benefit the overall ecosystem.

Understanding the existing infrastructure and community needs is vital for crafting effective PIPs. Take the time to research past proposals, engage with the community to gather feedback, and identify areas that align with the long-term vision of Polygon.

By focusing on relevant and impactful improvements, your PIP stands a better chance of being well-received and implemented successfully.

There are various research tools and resources available to aid in the development of a PIP proposal. These include whitepapers, technical documentation, developer forums, and online communities. By leveraging these resources, developers can gain a deeper understanding of the technical aspects involved in their proposed improvement.

Key Elements of a Successful PIP

Some key elements of a successful Polygon Improvement Proposal (PIP) include a clear problem statement, detailed proposed solution, technical specifications, potential impact analysis, and community feedback. Ensuring these elements are well-defined and concise is crucial for a successful PIP submission.

Tips to Write a Clear and Effective Proposals

There’s a vital need for clear and effective writing when drafting a Polygon Improvement Proposal (PIP). Being concise, using technical terminology appropriately, and structuring your proposal logically can greatly increase the chances of it being well-received by the community and the Polygon development team.

  • Use simple and precise language to convey complex technical ideas.
  • Organize your proposal in a clear and coherent structure for easy comprehension.
  • Avoid unnecessary jargon or ambiguity in your writing to ensure clarity.

The quality of your writing can significantly influence the way your proposal is perceived and evaluated by the Polygon community. Any ambiguity or lack of clarity could affect the credibility and impact of your PIP.

How to Submit Polygon Improvement Proposal?

Preparing Your Proposal for Submission

Assuming you have written your Polygon Improvement Proposal (PIP) following the template and guidelines provided, the next step is to prepare the proposal for submission. Make sure your proposal is well-documented, includes a clear explanation of the problem you are addressing, proposed solution, technical specifications, and any relevant research or data to support your claims.

Navigating the PIP Submission Platforms

You will submit your PIP through the official Polygon Improvement Proposals repository on GitHub. To navigate the submission process smoothly, familiarize yourself with GitHub and the repository structure. Create a GitHub account if you don’t have one and follow the instructions provided in the repository on how to submit your proposal.


When you are ready to submit your PIP, fork the official repository, create a new file with your PIP number and title, write a detailed description of your proposal, and submit a pull request. Be prepared to respond to feedback and iterate on your proposal based on community input during the review process.

After Submission: What to Expect

The Review and Feedback Cycle

Expect your PIP to go through a rigorous review and feedback cycle once it is submitted. Members of the community and the Polygon core development team will scrutinize your proposal, provide feedback, and suggest improvements. This iterative process is vital for ensuring the quality and feasibility of the proposed changes.

Factors Influencing PIP Acceptance

Expect several factors to influence the acceptance of your PIP. These factors include:

  • The alignment of the proposal with Polygon’s goals and roadmap
  • Technical feasibility and implementation complexity
  • Community feedback and support
  • The potential impact on network security, scalability, and decentralization

The decision to accept a PIP is based on a combination of technical merit, community consensus, and strategic importance.

Another critical factor that influences PIP acceptance is the clarity and completeness of your proposal. A well-written PIP that addresses all relevant aspects and includes a clear rationale and implementation plan is more likely to be accepted.

It is imperative to ensure that your proposal is technically sound, easy to understand, and aligns with Polygon’s principles and protocols.

What is the Difference Between a PIP and a PRC?

When comparing between a Polygon Improvement Proposal (PIP) and a Polygon Request for Comments (PRC), it’s essential to note their key differences in scope and focus within the Polygon ecosystem.

PIPs encompass a wide range of proposals that aim to enhance the overall Polygon protocol. These proposals can include significant upgrades like protocol changes, blockchain advancements, and the introduction of new features. They serve as a platform for suggesting comprehensive improvements to the Polygon network as a whole.

On the other hand, PRCs specifically target the standardization of smart contracts based on the Polygon protocols. These proposals are centered around defining norms and guidelines for smart contract development and deployment within the Polygon ecosystem.

PRCs often focus on standardizing aspects such as token standards and other smart contract functionalities. They play a crucial role in establishing a uniform framework for developers to follow when building on the Polygon protocols.

Both PIPs and PRCs contribute significantly to the evolution and efficiency of the Polygon network, each addressing distinct yet complementary aspects of protocol enhancement and smart contract standardization.

PIP Editors and Their Responsibilities

PIP Editors are individuals responsible for overseeing and managing the submission and review process of Polygon Improvement Proposals, which are proposals for enhancing the Polygon blockchain network. These editors play a crucial role in ensuring the quality and integrity of proposed improvements to the network.

Their primary responsibilities include:

  • Soliciting and Reviewing Proposals: PIP Editors actively seek out proposals from the community and thoroughly review each submission to assess its technical feasibility, impact on the network, and alignment with Polygon’s objectives.
  • Facilitating Peer Review: They coordinate the peer review process by engaging subject matter experts to provide feedback and recommendations on the proposed improvements.
  • Ensuring Transparency and Accountability: PIP Editors maintain transparent communication with the community regarding the status of proposals, decisions made during the review process, and any updates or changes to the proposals.
  • Guiding Proposal Authors: They provide guidance and support to proposal authors, helping them refine and develop their ideas to meet the standards and requirements set by the Polygon community.

PIP Editors act as gatekeepers for proposed changes to the Polygon network, ensuring that only high-quality and relevant improvements are considered for implementation.

However, it is crucial to understand that PIP editors do not have the authority to determine if a specific PIP is approved or not. They only determine that the requested PIPs are meet the polygon standards.


From above, writing and submitting Polygon Improvement Proposals (PIPs) requires a thorough understanding of the process and a detailed proposal.

By following the guidelines, including providing a technical specification and actively engaging with the Polygon community, developers can increase the chances of their proposals being considered and accepted.

It is important to adhere to the PIP template, put forth a strong and clear argument for the proposed changes, and be open to feedback and collaboration.

By following these steps, developers can contribute to the ongoing development and growth of the Polygon ecosystem.


By Ashok Rathod

Life is all about solving problems. Ashok is a software developer, technology enthusiast, founder, and director of a reputed software development company. Eager to help brilliant minds, and entrepreneurs with MVP ( Minimum Viable Product ) development, and technology consultation. Ashok is an engineer, a strategist, an investor, an architect, and a blogger who love to share about technology.

Recent Posts