Pre-PIPs How-To: Process+Template

See below for how to follow Pre-PIPs and what their template looks like!

Remember that a Pre-PIP comes from the Push Foundation to the DAO, as a request for comment.


  1. Remember a Pre-PIP is a “PIP for comment” from the Foundation to the community. Pre-PIPs are a new option giving the greater Push community more of a say in technical, governance, and marketing work being done for Push by the Foundation.

  2. When a Pre-PIP has been approved for sharing with the community by the Foundation, it will be shared via the link below, in the forum.

  3. Pre-PIPs/RFCS(New way of the Push Foundation interacting with the community) - #2 by EC3

  4. Pre-PIPs can be commented on for 7 days and the Foundation must hold to this time period as the “RFC” period. This is the minimum and both the Foundation and the community can agree on longer, if necessary.

  5. Once the RFC period has passed, the Foundation submits a poll below the Pre-PIP to solicit final feedback from the community. This poll should always include the options: “for” or “against.” The Foundation is not required to implement all community input but the idea is if it is heavily signaled by the community that they do or do not support the proposal, this should be taken into account. This period lasts for 3 days aka 72 hours.

  6. When the temperature check is over, the Pre-PIP moves forward and the Foundation can begin implementing it. For now, we will not involve a Snapshot vote as that will be another hurdle for both parties and the point here is to move forward step-by-step, gradually letting Pre-PIPs involve into full PIPs, which can be and are voted on via Snapshot to be passed.

  7. After the proposal is done aka the technical work is completed, the Foundation should submit a 750 word or less comment on how the process went from their end and submit it for feedback on what can be done better!

Template: (You’ll notice it’s very similar, almost identical to the PIPs template, by design).

What is the Pre-PIP Template?

Each Pre-PIP should contain the following sections:

Pre-PIP: [the number from 1 onward]

Author(s): [a list of author(s) names, usernames]

Discussions: [Link to any Previous discussions on the topic in the proposal, if not applicable, not applicable]

Created: [date created on MM-DD-YYYY]

Simple Summary

Describe the outcome the proposed change intends to achieve. This should be non-technical and accessible to a casual community member.


A short (~200 words) description of the proposed change, the abstract should clearly describe the proposed change. This is what will be done if the proposal is implemented, not why it should be done or how it will be done. If the proposal proposes deploying a new contract, write, “We propose to deploy a new contract that will do x”.


This is the problem statement. This is the why of the proposal. It should clearly explain why the current state of the DAO / protocol is inadequate. You must explain why the change is needed, if the proposal proposes changing how something is calculated, you must address why the current calculation is inaccurate or wrong.



This is a high-level overview of how the proposal will solve the problem. The overview should clearly describe how the new feature will be implemented.


This is where you explain the reasoning behind how you propose to solve the problem. Why did you propose to implement the change in this way, what were the considerations and trade-offs. The rationale fleshes out what motivated the design and why particular decisions were made. It should describe alternate designs that were considered and related work. The rationale may also provide evidence of consensus within the community and should discuss important objections or concerns raised during the discussion.


Outline of implementation steps, including manpower, budget, measurable KPIs, milestones, and specific timelines. Proposals missing any of these elements will not be successful.

Who posts a Pre-PIP?

Pre-PIPs, going forward from May 20, 2024, will be posted by Ian(EC3), unless Richa and Harsh expressly request to post them.

Temperature Check

Include the forum poll here, giving the option, “for,” or “against.”

If you have any questions on Pre-PIPs, reach out to @EC3 or @SixtyKeys.


Remember Pre-PIPs mark a new age for not just Push DAO but the progressive decentralization of the entire Push ecosystem through directly involving the community in the foundation’s initiatives.

This is an important step forward, walking the walk towards further ecosystem decentralization by design, over time.


I would love to Contribute! :heart:


@NooberBoy with Pre-PIPs, one key way you can contribute is by leveraging your background/knowledge to provide valuable feedback here on the Forum to the Push Foundation on the proposed initiatives the Foundation seeks to implement in Push Protocol :wink::bell:


This is great. I can’t wait to get the Push Foundation more involved with the governance process of Push DAO. :purple_heart: :bell:


Yes Ser! @christiandike

1 Like