# RFC: Changes to our CP Framework and Governance Process

**URL:** <https://gov.centrifuge.io/t/rfc-changes-to-our-cp-framework-and-governance-process/5448>\
**Category:** Proposals\
**Tags:** governance-process, may, 2023, cp4\
**Created:** [May 22, 2023, 10:57am UTC](https://gov.centrifuge.io/t/rfc-changes-to-our-cp-framework-and-governance-process/5448 "2023-05-22T10:57:31Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![Rhano](https://dub1.discourse-cdn.com/flex013/user_avatar/gov.centrifuge.io/rhano/32/1014_2.png) [@Rhano](https://gov.centrifuge.io/u/Rhano)\
**Post date:** [May 22, 2023, 10:57am UTC](https://gov.centrifuge.io/t/rfc-changes-to-our-cp-framework-and-governance-process/5448/1 "2023-05-22T10:57:31Z")

</div>

Proposal type: CP4  
Authors: Governance and Coordination Group (@ImdioR @Rhano)  
Contributors: @Davidutro  
Technical/non-technical proposal: non-technical proposal  
Date proposed: 2023-05-22

### Short Summary

Improving/simplifying our current Governance Process.

### High-level objective

Making our Governance Process more clear for anyone who wants to submit a CP and remove ambiguity from the process.

### Background

Back in October, the GCG [proposed the first version of our Governance Process](https://gov.centrifuge.io/t/rfc-proposal-for-new-governance-process-and-framework/4683) that we are using today. Since then, [many CPs have been submitted](https://github.com/centrifuge/cps) and we have learned a lot about what is working and what can be improved.

### Detailed description of proposal

The GCG wants to propose the following changes to our Governance Process.

You can see the full proposal with a more detailed description of the changes and their implications [here](https://docs.google.com/document/d/12EowIF10pNmBdfrS2UvzsIr-6U5PR_4UMO1ZEvyOI-4/edit#heading=h.96f25g9zigx2).

#### Off-chain governance + templates

##### 🙋 Minimum time for RFC

Keep the minimum time for 7 days but add that we strongly encourage 14 days or more.

##### 🙋 Cooling-off period for a proposal

Keep the time as 15 days but count from when the OpenSquare snapshots ends and apply a cooling-off period for on-chain proposals as well.

##### 🙋 Forum posts for CPs

One CP = one Forum post. The first post generally created is the RFC and it should be updated whenever the proposal passes through the stages (i.e. when it moves forward to off-chain voting, on-chain voting and the outcome of these etc.). We also propose to utilise tags in the titles to indicate what phase a proposal is in.

##### 🙋 Redefine when OpenSquare snapshots are needed

OpenSquare snapshots are optional if a proposal is followed by an on-chain vote straight after.

##### 🙋 Batch proposals on OpenSquare

All proposals that are ready to proceed get batched on OpenSquare the 1st and 3rd Mondays of the month. However, if there are time sensitive/urgent proposals, we have the option to start the off-chain vote anytime.

##### 🙋 Quorum for OpenSquare snapshots

Re-introduce a quorum for OpenSquare snapshots of 4M CFG (currently ~1% of total supply).

##### 🙋 Add “Abstain” as an option in OpenSquare snapshots

Add the option “Abstain” to the OpenSquare Snapshots, in addition to “Yes” and “No”. Votes for “Abstain” count towards the quorum.

##### 🙋 Two simultaneous, mutually exclusive proposals (off-chain)

Add to the governance process that in case there are two mutually exclusive proposals running simultaneously in an OpenSquare snapshot, it will be the one with most “Yes” votes (in terms of CFG), that will be the one that moves forward/passes.

##### 🙋 Possibility of correcting typos/minor errors in CPs on GitHub

Allow fixing typos and information that is obviously wrong after a proposal has passed. The procedure would be to just go ahead and correct the mistakes, and then announce the change(s) in the forum post for that proposal so people can object to it if they think the change(s) will alter the original proposal. The GCG is responsible for maintaining the Proposal Repository on GitHub so any changes would need to go through GCG.

##### 🙋 Specify changes more clearly

Add to the templates of RFCs which other CPs they modify/impact.

#### Mandates and Groups

##### 🙋 Definition of a mandate (CP1)

We have expanded on the definition of what a mandate is and when it is required.

##### 🙋 Selecting/changing a facilitator of a mandated group (CP1.1)

Create a default process for how a facilitator is selected or changed and redefine CP1.1 to be used for this process.

#### CPs in general

##### 🙋 Rename proposal types to “Components”

Rename the proposal types (CP1, CP2, CP3, CP4 etc.) to _Components_ and allow CPs to implement/use multiple components in the same proposal. Remove the abbreviation of the proposal types/components in the title of a CP (e.g. GI, MR, RU etc.) as it will look messy if more are included in the same CP.

##### 🙋 Modify CP5 (POP)

Add to the documentation that the POP only applies to pools launching on Centrifuge Chain (not Tinlake) and replace OpenSquare Snapshot with **on-chain** voting(also change the visual for the flow of the onboarding process so it reflects this) in Stage 3.

##### 🙋 Add a visualisation of the flow of CPs

Add the flowchart below to our documentation.

 ![image](https://europe1.discourse-cdn.com/flex013/uploads/centrifuge1/original/2X/5/5b50972a0d943ecaf11a74a61e94f40f1c208b54.png)

* * *

The changes proposed above will modify the following CPs:

- [CP0](https://github.com/centrifuge/cps/blob/main/cps/CP0/CP0.md)
- [CP1 and CP1.1](https://github.com/centrifuge/cps/blob/main/cps/CP1/CP1.md)
- [CP2](https://github.com/centrifuge/cps/blob/main/cps/CP2/CP2.md)
- [CP4](https://github.com/centrifuge/cps/blob/main/cps/CP4/CP4.md)
- [CP5](https://github.com/centrifuge/cps/blob/main/cps/CP5/CP5.md)
- [CP32](https://github.com/centrifuge/cps/blob/main/cps/CP32.md)

### Change or improvement

This proposal, if passed, will improve many aspects of our governance.

- Better Flow of our Governance

- Better Quality of Proposals

- Better Structure of our Forum

### Responsible

Governance and Coordination Group (@ImdioR & @Rhano)

### Alignment to the mission of Centrifuge DAO

Having a robust, clear and decentralised governance process is crucial in our path towards our mission! It is one of the key pillars and improving it is an on-going process.

### Next steps

After this RFC has been open for input and discussion for minimum 7 days, it will be submitted to the Centrifuge Proposal Repository on GitHub and an OpenSquare snapshot vote will be created (only off-chain voting, no on-chain voting is required for this proposal).

If the proposal passes on OpenSquare, the changes will applied, effective immediately, and the relevant documentation will be updated.

---

_[View the full topic](https://gov.centrifuge.io/t/rfc-changes-to-our-cp-framework-and-governance-process/5448)._
