---
tags: MIPs
---
### MIP0
- **MIP0c3: The MIP Lifecycle**
- _"Deferred: Assigned when a proposal has been deemed as not ready or not a priority but can be re-proposed at a later date. This status can be assigned during RFC or by a rejecting forum poll or **Signal Request**"._

### MIP4
- **MIP4c3: Amendment Process for MIPs Younger than 3 Months**
- _"Amendment Subproposals must be submitted to RFC for one week, for the Default Feedback Period. This is followed by a one week duration **Signal Request** thread, during which the Amendment proposal cannot be changed, fulfilling the 1 week frozen period."_
- _"Other Requirements: 7-day **Signal Request** Thread, passing with 51%."_

### MIP16
- **MIP16c2: Weekly Governance Cycle Breakdown**
- _"If a non-standard weekly poll (**"signal request"**) has been proposed, it will also be put in the weekly poll. To create a non-standard weekly poll requires an urgent and apparent reason from a timing perspective to justify it. It is important to note that a non-standard weekly poll cannot be used for long-term decisions and requires consensus from the Governance Facilitators before it can be accepted and published."_

### MIP24
- **MIP24c3: Emergency Response Procedure**
- _"Declare an emergency in the public forum providing sufficient detail regarding the issue and why immediate action is required. If time does not permit, a forum post will be created immediately after or in parallel to taking emergency action. Creating a **signal request** thread or governance poll is optional."_
- **MIP24c4: Urgent Response Procedure**
- _"The process will be initiated with a **signal request** thread in the public forum stating the need for expedited governance action and include the following:"_
- _"In order for the community to make a change to a system parameter, a **signal request** must reach a 50% majority and have a reasonable quorum of voters given recent participation."_
- _"In order for the community to make a change outside of the existing system parameters, a **signal request** must reach a 66% majority and have a reasonable quorum of voters given recent participation."_
- _"If the **signal** for an urgent response passes, Governance Facilitators will coordinate with necessary domain teams to expedite a governance poll for MKR holders or to advance an executive vote, at their discretion."_

### MIP48
- **MIP48c4: Stopping Distributions from the Keg**
- _"In some time-sensitive scenarios, the Governance Facilitators may deem a **Signal Request** appropriate for stopping or pausing payments from the Keg."_

### MIP61
- **MIP61c6: Modification of Parameters**
- _"Recognized Delegates are potentially conflicted in consideration of these proposals. There may be a temptation to approve increases in compensation and vote against decreases. Hence, a **Signal Request** is required to assess broader community sentiment and spotlight any positions on the MIP61c5 proposal staked out by Recognized Delegates. The **Signal Request** Poll must be posted at the start of the Frozen Period."_
- _"Requirements: 7-day **Signal Request** Thread, passing with 51%. If the **Signal Request** fails, then the proposal does not proceed to the Governance Cycle."_

### MIP67
- **MIP67c1: Proposal Submission Process**
- _"Initial engagement with the relevant structured finance CU (e.g. RWF-001), providing the CU with a reasonably detailed Proposal (not necessarily formalised yet as a MIP or **Signal Request**) that conforms with the Methodology and with the appropriate time to review its high-level pillars."_

### MIP68
- **MIP68c4: Debt Ceiling Gradual Increase Mechanism**
- _"This mechanism can be deactivated to prevent the automatic increase of the debt ceiling. Deactivation occurs if a valid **signal request** that specifically mentions deactivating MIP68c4 passes the on-chain poll stage."_

### MIP70
- **MIP70c5: Collateral onboarding cancelation procedure**
- _"The collateral onboarding can be canceled at any time by the community through a standard or urgent **signal request** process."_

### MIP73
- **MIP73c10: Collateral Onboarding Cancellation Procedure**
- _"The collateral onboarding can be canceled at any time by the community through a standard or urgent **signal request** process."_

### MIP74
- **MIP74c2: Urgent Cancellation of a Permissionless Open Market Operation**
- _"Any Permissionless Open Market Operation which is implemented can be shutdown by: (i) a **Signal Request** process which must last at least 1 week and..."_
- _"(ii) a shutdown process which does not require a **Signal Request** can be initiated by Facilitators of relevant Core Units. It is recommended, but not limited to, that Facilitators propose the shutdown to the on-chain poll and propose the immediate shutdown directly via Executive Vote only in the case of an emergency which is time-sensitive."_

### MIP76
- **MIP76c3: Operating Guidelines**
- _"Asset allocation changes can be made through **Signal Requests** followed by a three day on-chain vote ratification."_

### MIP78
- **MIP78c6: Modification of Compensation Parameters**
- _"Recognized Delegates are potentially conflicted in consideration of these proposals. For example, there may be a temptation to approve increases in compensation and vote against decreases. Hence, a **Signal Request** is required to assess broader Community sentiment and spotlight any positions on the MIP78c6 subproposal staked out by Recognized Delegates. The **Signal Request** Poll must be posted at the start of the Frozen Period."_
- _"Requirements: 7-day **Signal Request** Thread, passing with >50% of non-abstain votes. If the **Signal Request** fails, the proposal does not proceed to the Governance Cycle."_