MIP5: Emergency Voting System

MIP5: Emergency Voting System


MIP#: 5
Title: Emergency Voting System
Author(s): Rune Christensen (@Rune23) and Charles St.Louis (@CPSTL)
Contributors: @LongForWisdom
Type: Process
Status: <Assigned by MIP Editor>
Date Proposed: 2020-04-06
Dependencies: n/a
Replaces: n/a

Sentence Summary

MIP5 defines emergency changes to the protocol and Governance Facilitator role and how they should be handled in practice.

Paragraph Summary

This proposal defines an emergency voting system. Emergency votes are executive votes that can be initiated by any community member.

Component Summary

MIP5c1: Governance Facilitator Emergency Votes
This component addresses the emergency removal of an individual from the Governance Facilitator role.

MIP5c2: An Emergency State Change
This component addresses emergency state changes to the protocol and how they are to be handled by the Governance Facilitators.


This standard is being proposed in order to allow the community to overcome the constraints of the governance cycle (MIP3) in special situations where it is time critical to make changes or remove a part of the operating system.

Specification / Proposal Details

MIP5c1: Governance Facilitator Emergency Votes

A governance facilitator emergency vote encodes one or more website URLs into an on-chain voting contract (spell), as well as containing logic that stops any payment stream to the existing governance facilitators. If the executive vote gets the most MKR votes and becomes the active proposal the existing Governance facilitators are then removed. The list of website URLs then corresponds to a list of one or more new Interim Governance facilitators and their governance platforms that will replace the current governance facilitators. The current governance cycle is canceled, and the new Interim Governance Facilitators initiate a new governance cycle on the following 1st Monday of the month.

MIP5c2: An Emergency State Change

An emergency executive vote that contains state change logic. For example, changing the DSR or removing a collateral type. These types of votes can in some cases be used to reduce risk in the system, help stabilize the peg, or fix critical technical issues. However, they are also very dangerous and must be used carefully as they can potentially be attacks that, for example, drain all the collateral from the system.

Governance Facilitators can ignore an emergency state change, or either declare support for an emergency state change by adding it as an irregularly scheduled executive vote on their governance portals, or declare it a governance attack, potentially encouraging users to trigger an emergency shutdown in response.

1 Like

@charlesstlouis are there any MIP sets on the roadmap that will address mechanics of Emergency Shutdown or is this the MIP that is closely related to the topic?

Specifically, interested in process for triggering ES, designing parameters, executing smart contract that may put ES into effect.

1 Like

@Rich_Cuellar-Lopez This is a good question, @LongForWisdom should have a salary raise, because there is lot of work for him right now… From what i can see, it’s going to be a mess up in the forum. @LongForWisdom already started to make some cleaning, but well. If you guys need help, just buzz me up !

1 Like

Hey @Rich_Cuellar-Lopez, there are no MIP Sets on the short-term roadmap for Emergency Shutdown (ES). However, that doesn’t mean it cannot be proposed : )

In terms of resources defining and describing MCD ES, here is a good list:

Besides the above documentation, I have also been working on a more detailed piece for MCD ES.


The most updated version of MIP5 can be found here: https://github.com/makerdao/mips/tree/master/MIP5

1 Like