MIP12c2-SP8: BAL Collateral Onboarding
MIP12c2-SP: 8 Title: BAL Collateral Onboarding Author(s): Niklas Kunkel (@NiklasKunkel) Contributors: Charles St.Louis (@CPSTL), Will Remor (@williamr), Sam MacPherson (@hexonaut) Status: Formal Submission (FS) Date Proposed: 2020-10-07 Date ratified: <yyyy-mm-dd>
This proposal defines the documentation and work requirements for the onboarding of the BAL Collateral type to the Maker Protocol, explicitly highlighting the domain teams’ objectives and work requirements needed to get it implemented to the Maker Protocol. If this proposal is ratified, the BAL collateral type will be added to the Maker Protocol allowing anyone to lock BAL in a Maker Vault to generate Dai.
This subproposal contains the domain work products required for the BAL collateral asset to be added to the Maker Protocol. More specifically, it includes the risk parameters, oracle solutions, and the necessarily smart contracts required for the successful onboarding of BAL.
Risk Domain Work: The risk domain team’s work contains the following risk assessment for the BAL collateral type:
Smart Contracts Domain Work: The smart contracts domain team’s work required to get BAL added to the Maker Protocol includes an assessment of the general and technical information about the BAL token, a risk summary, formal verification considerations, audits & related documentation, a contract logic summary, administrative addresses, and lastly a contract risk summary. The full assessment can be viewed below:
Oracles Domain Work: The oracles domain team’s work required to get BAL added to the Maker Protocol, includes making sure the oracle price feeds to support the new collateral type are prepared. The full assessment can be viewed below:
The goal of this proposal is to provide transparency to the Maker Community as to what the domain teams’ (Risk, Smart Contracts, and Oracles) work consists of in order to successfully add the BAL collateral type to the Maker Protocol.