Consider this unspecified airdrop proposal: it simply expresses an intent. If it goes through, there is nothing that can be done based on this, considering there is no specification: the community will need to specify the intent into a proper proposal and vote on it again.
To avoid frustrating situations like these, a common understanding of what an implementable proposal must include is necessary.
We’ll provide all necessary information to the community, that I’d like to see rise up to the occasion! Not only can you get involved in the establishment of the PSPIP, but doing so will also help you develop critical expertise on ParaSwap’s governance process.
Once the PSP-IP is established, the Content Producers who actively contributed to it will be able to step up to become Governance Scribes - here to support individuals and DAOs to help them write qualitative proposals and to update the community with frequent governance recaps.
Keep in mind that while the PSPIP framework must be clear and include everything needed for implementation, the challenge is also to keep it as lightweight and simple as possible to facilitate participation.
We will formalize the PSPIP with four main steps:
- (you are here /now) Launching the process with the base proposed doc
- (this week → up to the CC#2) Feedback, discussion and iterations on the requirements and how to uphold them
- (in the wake of the CC#2) Initial framework proposed: the Scribes can collect feedback and keep improving on the proposed framework
- (soon) ⇒ Scribes submit the first framework as PSPIPΔ0. If the proposal passes, all following proposals will need to respect the framework it specifies.
A number to identify the proposal, based on the order of submission and name (=snapshot vote title).
Ex: PSP-IPΔ0: ParaSwap Improvement Proposal Framework
One or multiple choice: Front-end upgrade, smart contract development, marketing and communication, security, PSP token upgrade, PSP liquidity incentives, PSP staking policy, parameter update, integrations, and synergies.
Clear and layman-accessible one or two-line summary of the proposal.
Comprehensive overview of the issue being addressed and the solution proposed (~ 100w).
What are the main goals of the proposal? What is it trying to accomplish?
What the proposal requires to come to life: PSP budget, additional development on the ParaSwap product, external development, etc.
How will success be measured? What metrics will be used to evaluate the success of the proposed implementation?
With this proposal implemented, what are the next steps to consider? Does this proposal include any new parameter the DAO can adjust? Does it call for a revision of another subcomponent of the system?
What happens if this proposal goes through? A high-level overview of the main steps required for its implementation.
This topic is open for everyone to share their envisioned improvements to the proposed framework. Changes to the framework must be confirmed by a governance vote.