PDIP 1 - Introducing a framework for governance structure and record

Authored by DeFi Ted & Flapjackson


This document describes the process for writing a PDIP and PCCP for the Paragons DAO Community


Right now we have no clear guidance when it comes to introducing changes or ideas to ParagonsDAO from the community. This model, as used by Synthetix, has proven to be successful in management of suggestions and proposals of change.


What is a PDIP

A PDIP stands for ParagonsDAO Improvement Proposal and is an adaptation of the EIP (Ethereum Improvement Proposal) process. The purpose of this framework is to ensure that a standard for implementing any core or fundamental changes to the DAO, its vision and roadmap are tabled in a consistent and transparent format. A PDIP is a document that provides the community about the proposed changes. The author of the PDIP is responsible for building and championing the proposal within the community while documenting any argument against the changes.

What is a PCCP

PCCP stands for the Paragons Configuration Change Proposal. PCCP documents outline the case for changing one or more of the modifying variables within an implemented PDIP. This allows a record of changes made to any PDIP configuration throughout the DAO’s history and the reasons for this change. The author of the PDIP is responsible for building and championing the proposal within the community while documenting any argument against the changes.

PDIP & PCCP Rationale

PDIP and PCCP are intended to be the two primary vehicles for proposing new features, collecting community feedback on large scale issues and for the documentation of all changes made to the ParagonsDAO.

It is highly recommended that a single PDIP is concentrated on a single key proposal or new idea. This gives the proposal its best chance for success, as it prevents conflating ideas and allows a single point of focus for voters from the ParagonsDAO Community.

Any PDIP or PCCP must meet a minimum criteria. It must be a clear and complete description of the proposed enhancement. The proposal must represent a net improvement with supporting analysis where required.

PDIP and PCCP WorkFlow

The following process applies to PDIPs and PCCPs

Parties involved in the process are the author, the PDIP editors, the Paragons Core Contributors and the Paragons DAO Community.

Authors should vet their ideas before starting the PDIP process to ensure the idea has some community support and hasn’t already been raised and rejected. The ParagonsDAO Discord is likely the best place to vet your ideas .

PDIP authors should write any PDIP in the style and format described here, lead discussions in the appropriate forums and build community awareness and consensus around the proposal. Following this the below process can be started:

Each step of the process is owned and requested by the PDIP author and reviewed by PDIP editors.

Once a PDIP process is drafted, authors should start a discussion related to their proposal on the ParagonsDAO Discourse page (see PDIP Discussions and Storage below) and include a link to the discussion in the ParagonsDAO Discord.

The PDIP editors will process these requests as per the below conditions:

Draft - This PDIP is a work in progress, ongoing discussions happening with the Paragons Council member/s and champion/s.

Feasibility - PDIP is assigned to a Core Contributor to undertake a feasibility study

Paragons Council Review Pending - PDIP is being formally reviewed for voting or if more is needed to make a decision.

Vote Pending - PDIP is currently up for vote with Paragons Council (PDIP to follow for Council)

Approved - PDIP has passed

Rejected - PDIP has failed to pass consensus

Implemented - PDIP has been completed as per outlines

The layout of a PDIP

  • Preamble; contains the PDIP number, title of the PDIP and champion details
  • Summary; Provide a simplified and short description of the proposal.
  • Abstract; a short description outlining clearly the issue being addressed
  • Motivation; this is an optional feature of the proposal is to change the roadmap, vision or DAO setup in any way.
  • Specification; The specifics and details of the solution or change being proposed against the Abstract
  • Rationale; a detailed analytical view for the reasons and motivations behind the proposed changes. It should be in line with the “show your working” theme and detail any other possible solutions considered and if there were objections raised before submitting.
  • Test Cases; Test cases can be added but are not required.
  • Copyright Waiver; All PDIP’s must be in the public domain

PDIP Discussions and Storage

PDIPs will have their discussions on our Discourse forums (https://discuss.paragonsdao.com) and once ratified via voting on Snapshot, all permanent storage of decided PDIPs will be located on IPFS, via a Skiff decentralised content system (https://skiff.org) and managed by the PDIP editors.

Additional Content

Graphs and other visual content can be used in a PDIP where it is required or useful for presentation.

PDIP Editors

Current list;

  • Defi Ted
  • InfoAddict
  • Obviously_obvious
  • JCrew
  • Strawman
  • FlapJackson

PDIP Editor Responsibilities

Each PDIP will need actions from the editors for the below:

  • Read and clarify that the PDIP is worded correctly with changes discussed being made
  • Title matches the Proposal outline
  • Language, grammar, spelling and structure is sound

In the event the PDIP is not complete and is sent back to the author:;

  • Assign clear instructions on the next steps, this could include issues to be addressed before resubmitting, suggested reformatting or additions that need to be made.

PDIP editors are champions of the standard and process within the PDIP framework, while maintaining standards for grammar, spelling and formatting mistakes.

PDIP editors are not required to provide judgement but serve as a clear and effective communicator between parties.


Copyright and related rights waived via CC0.


Approved. LFGoooooooo