Overview of the Collateral Onboarding Process

Introduction

The Collateral Onboarding process is a crucial aspect of growing MakerDAO. Onboarding quality collateral assets to the Maker Protocol increases the demand for Dai, scales-up Dai supply, and ultimately helps mitigate risk while maintaining Dai stability. Moreover, a formalized and public collateral onboarding process upholds the DAO’s principles of complete transparency and accountability to the Maker community.

Diagram Overview of the Collateral Onboarding Process

High-Level Overview of the Collateral Onboarding Process

1. A Collateral Onboarding Application is completed and proposed to the MakerDAO community in the Maker Forum.

2. Collateral Onboarding Community Greenlight Polls

3. On-chain Collateral Management (CMON) and Off-chain Collateral Management (CMOFF) stakeholder alignment meetings.

  • These meetings take place on a weekly cadence. Stakeholders discuss, update collateral onboarding status in the spreadsheet and prioritize new collateral onboarding in accordance to progress made and Core Unit's capacity.

  • Collateral Maintenance discussions also take place for collateral that is already onboarded in the protocol. Collateral Maintenance tasks range from updating risk parameters, creating new ILKs for already available collateral (for example ETH-B, ETH-C), or discussing offboarding of underperforming collateral.

  • During the weekly Mandated Actors call, updates are provided on the progress of current domain and collateral onboarding work, as well as upcoming work.

5. Domain collateral assessments are created and published to the Maker Forum while awaiting the posting of a Governance Poll.

  • Once collateral is prioritized by the Domain Teams, the domain collateral assessments are schedule to be created by the MakerDAO Risk, Oracle, and Smart Contracts Domain Teams and contain in-depth evaluations of collateral types. The goal of the assessments is to provide information to help inform the MakerDAO governance community. During the analysis and assessment process, one or more Domain Teams, at their discretion, may make a decision to stop the collateral onboarding process due to information uncovered. For example, the risk assessment shows a highly illiquid market which would prevent the liquidation of the collateral.

  • Once all assessments are published, Governance Polls are created which allow MKR holders to signal their support or opposition to adding a collateral type to the Maker Protocol.

6. If the Governance Poll passes, the Domain Teams finalize their respective work and an Executive Vote is scheduled; if the Poll does not pass, a request for a new governance poll may be resubmitted in the future.

  • Typically, governance polls for collateral onboarding may be resubmitted only twice. Therefore, it is recommended that the community first investigates why a governance poll initially failed before proceeding with the resubmission.

7. Once the required work of MakerDAO Risk, Oracle, and Smart Contracts Domain Teams is done, an Executive Spell is prepared.

  • The Executive Spell is a smart contract created for each weekly Executive Vote. The smart contract contains logic that implements changes agreed to by voters in prior Governance polls. It’s important to note that the Executive Vote needs to pass in order to officially implement the changes in the Executive Spell to the Maker Protocol.

8. The Executive Vote date is announced once the Executive Spell is complete.

  • Collateral Onboarding Executive Votes will always occur on Fridays.

9. If the Executive Vote passes, the collateral asset is added to the Maker Protocol; if it fails the collateral type has officially been rejected from being added to the Maker Protocol.

  • As mentioned in step 6, governance polls for collateral onboarding may be resubmitted up to two times before not being eligible for resubmission. If a resubmitted governance poll passes, it will proceed to an Executive Vote once again.

  • If the Executive Vote passes, the collateral type(s) is added to the Maker Protocol, and the addition communicated on Maker social channels (Twitter, the Maker blog, and Discord).

Last updated