Skip to main content

How to Propose

Polygon Improvement Proposals, or PIPs, are a way for the Polygon community to propose and develop solutions to improve the Polygon protocols. PIPs are an important part of the Polygon development process and provide a way for developers, researchers, and users to contribute to the future of the Polygon network.

In this guide, we will cover the basics of how to write and submit a PIP for consideration. Whether you're a seasoned Polygon developer or just starting to explore blockchain development, this guide will provide you with the information and resources you need to get started with PIPs and make your voice heard in the Polygon community.

So before you begin crafting your proposal, ask yourself the following questions that will help you decide whether your idea is a PIP or a forum post!

Is it a PIP or an advertisment?

Do not use the PIP framework to promote your project!

Is the proposal unique?

Make sure that your proposed PIP is not a duplicate of a previous proposal.

Why are you writing a PIP?

A Polygon Improvement Proposal (PIP) is a document that outlines changes or improvements to the Polygon network.

PIPs can be written for a variety of valid reasons, including addressing technical issues, improving scalability, adding new features, enhancing security, and standardizing processes.

OK, I have checked the PIP framework, and consulted with the above questions. What now?

A Polygon Improvement Proposal (PIP) is a design document that proposes new features, improvements, or standards for the Polygon protocols. The following is a guide on how to write and submit a PIP:

  1. Choose a topic: Choose a topic that you want to propose a change for. It could be a new feature, an improvement, or a novel standard.

  2. Research and gather information: Gather information about the topic, including relevant background information, technical details, and any relevant existing solutions or standards.

  3. Write the PIP: We suggest using the PIP template provided in the GitHub repository. The template includes sections for introduction, motivation, specification, and rationale.

  4. Gather feedback: Share your PIP with the Polygon community on the Polygon community Forum and get feedback from experts, developers, and users. You can do this by sharing the PIP on forums, social media, or by reaching out to relevant individuals.

  5. Submit the PIP: Submit the PIP to the Polygon Improvement Proposal repository on Github.

  6. Revise and finalize: Revise your PIP based on the feedback you receive and finalize it.

  7. Community review: The Polygon community will review the PIP and provide feedback. You may need to revise the PIP based on the feedback received.

  8. Approval: If the PIP is approved, it will be included in the Polygon protocol.

Polygon Improvement Proposal (PIP) vs Polygon Request for Comments (PRC)

Polygon Improvement Proposal (PIP) and Polygon Request for Comments (PRC) are similar in that they both serve as a standard for proposing improvements and additions to the Polygon protocols. However, there is a subtle difference in the scope of the proposals they represent.

PIPs are broader in scope and can encompass proposals for improvements to the Polygon protocols, such as changes to the protocol, upgrades to the blockchain, and new

Here are some tips that will help you with moving the PIP forward!

  • Use the Polygon Community Forum to engage with the community.
  • Reach out to projects that are relevant to your proposal and ask them for feedback and ideas!

Tip: Under the Verified Group in the Polygon Forum you will find a wide range of dApps and projects deployed on Polygon PoS.

  • Write an article about the relevance of the PIP, explain your rationale, inspiration and how it can be used to improve the protocol/community.
  • Engage in the discussion taking place in the Forum. Great minds work better together!