Preamble
MIP13c3-SP#: 9
Author(s): Yaron Velner (@yaronvel)
Contributors: n/a
Status: Request for Comment (RFC)
Date Proposed: 2021-1-05
Date Ratified: <yyyy-mm-dd>
Declaration Statement: Onboarding a new collateral type backed by B.Protocol.
Declaration to Replace: n/a
Specification
Context and Motivation
- Maker, and the DeFi ecosystem in general, has conservative collateral ratios (CR), in order to mitigate potential failures in the liquidation process. High CRs narrows the potential user base, and the potential profit from stability fees (SF).
- B.Protocol introduces the concept of a backstop made of committed liquidators, who get priority in the liquidation process, in return to their commitment.
- B.Protocol is live since October 2020, backstopping over $18m of ETH-A collateral and $6m debt. Few successful liquidations were already done.
- In ETH-A collateral B.Protocol is an opt-in system, where users can decide to manage their Vault with, and give priority to the liquidators. B.Protocol liquidators in return share some of their proceeds with the users who give them the priority. In particular, it requires the user to interact with a new set of smart contracts.
- An experiment is proposed for a native integration between B.Protocol and the MakerDAO system, by on-boarding a new collateral type, namely WBTC-B or ETH-C, with lower CR than WBTC-A or ETH-B (respectively), which will be natively backed by a strong commitment from B.Protocol backstop.
Committed backstop design
For simplicity we describe a system with a single liquidator. Scaling the system for multiple liquidators, in a permissionless way, will be handled by B.Protocol, and it is not in the scope of this writeup (we presented some ideas on how to achieve fairness here).
We illustrate the protocol with an example of WBTC collateral, $5M ceiling, and 0 liquidation penalty, however, this is only for the sake of illustration, and it is not part of the declaration of intent
Initialization: the liquidator opens a Vault with $0.5M WBTC deposit, and 0 debt. We denote this liquidator’s Vault with lv. Liquidator can withdraw collateral or increase his debt, only if his net position (collateral minus debt) is over $0.5M (according to MakerDAO price feed).
Liquidation: when calling bite to an unsafe Vault v
, then if v==lv
, or lv does not have a net position of $0.5M, then v
is subject to a standard liquidation process (by the cat
or the dog
).
Otherwise, the entire position of v is forked and added to lv
. The user of v is losing all his collateral (which is effectively a maximum of 10% penalty). lv
get all the user collateral and all of the user debt.
The bite
function is callable by anyone.
Declaration Detail
Maker Governance declares its intention to experiment a native integration with B.Protocol. Namely, to on-board a new collateral that gives a priority(*) in liquidations to B.Protocol, in return to an on-chain commitment of B.Protocol backstop liquidators through an on-chain crypto-economic incentive (**), towards successful liquidations.
(*) If B.Protocol fails to liquidate a Vault, then the Vault will be liquidated by the standard Maker keepers, like today.
(**) Liquidators who fail to liquidate, will incur an economical cost.
Further, it is the governance intent that:
- The development work will be done by the B.Protocol team, to the satisfaction of the Maker’s smart contract team.
- The collateral oracle will be recommended by the oracle team.
- The risk parameters, namely, the CR, debt ceiling, and auction parameters (if still applicable) will be recommended by the risk team.
- Stability fee and liquidation penalty will be discussed again with the community, in the form of signal requests.