MIP10c9-SP2 Proposal: Whitelist DeFi Saver on BATUSD Oracle

MIP10c9-SP#2: Subproposal to Whitelist DeFi Saver for BAT/USD Oracle Access

Preamble

MIP10c9-SP#: 2
Author(s): Nenad Palinkasevic, Nikola Klipa, Nikola Jankovic
Contributors: Nenad Palinkasevic, Nikola Klipa, Nikola Jankovic
Type: Process Component
Status: /
Date Proposed: <2020-05-15>
Date Ratified: <yyyy-mm-dd>

Specification

Introduction

DeFi Saver is a 3rd party MakerDAO management application created by Decenter. One of the included features is Automation - a system for automated MakerDAO CDP/Vault management based on user’s configuration.

The Automation system has recently experienced issues protecting some automated positions against liquidation on Black Thursday, where large price updates in MakerDAO bypassed users’ configurations and rendered the system unable to act, the cause of which was lack of access to the MakerDAO OSM for the data on next scheduled price update and the DeFi Saver team’s desire to maintain trustlessness of the system. Since then, the team has introduced an update that takes into account next scheduled price update in the OSM for better resilience, but in a non-trustless manner.

The Oracles v2 introduction post published by the Maker Foundation in September of 2019 outlined a future capability of Maker Governance to whitelist access to Oracle feeds and the more recent Governance actions have now fully ratified such a process, as described in Maker Improvement Proposal #10: Oracle Management.

DeFi Saver would use access to this Oracle to trustlessly verify the next MakerDAO price update in OSM.

Oracle Name

BAT/USD

Customer(s)

DeFi Saver - [email protected]

Whitelist

DeFi Saver - 0xeAa474cbFFA87Ae0F1a6f68a3aBA6C77C656F72c - OSM

Requirements

For each customer address to be whitelisted:

  • Is the contract source code verified on etherscan? Yes
  • Is the Oracle data used in a permissioned manner that would prevent parasitic behavior? Yes
  • Is Oracle data written to storage? No
  • If Oracle data is stored, is it stored in a private variable? n/a
  • If Oracle data is stored, is the value accessible on-chain exclusively by the protocol? n/a

Fee

In accordance with the Responsible Oracle Migration Proposal, fees are waived for the first year and determined by MKR Governance after that.

5 Likes

The Oracle Team has reviewed and confirmed all the information contained within this subproposal.

Preamble

MIP10c9-SP2

Author(s): Nik Kunkel

Contributors: Nenad Palinkasevic, Nikola Klipa, Nikola Jankovic

Type: Process Component

Status: Proposed

Date Proposed: 2020-05-17

Date Ratified: <yyyy-mm-dd>

Specification

Introduction

The Oracles v2 introduction post published by the Maker Foundation in September of 2019 outlined a future capability of Maker Governance to whitelist access to Oracle feeds and the more recent Governance actions have now fully ratified such a process, as described in Maker Improvement Proposal #10: Oracle Management.

DeFi Saver is a 3rd party MakerDAO management application created by Decenter. One of the included features is Automation - a system for automated MakerDAO CDP/Vault management based on user’s configuration.

DeFi Saver would use access to this Oracle to trustlessly verify the next MakerDAO price update in OSM.

Oracle Name

  • BAT/USD

Customer(s)

DeFi Saver - [email protected]

Whitelist

DeFi Saver - 0xeAa474cbFFA87Ae0F1a6f68a3aBA6C77C656F72c - OSM

Requirements

For each customer address to be whitelisted:

  • Is the contract source code verified on etherscan? yes

  • Is the Oracle data used in a permissioned manner that would prevent parasitic behavior? yes

  • Is Oracle data written to storage? no

  • If Oracle data is stored, is it stored in a private variable? n/a

  • If Oracle data is stored, is the value accessible on-chain exclusively by the protocol? n/a

Fee

In accordance with the Responsible Oracle Migration Proposal, fees are waived for the first year and determined by MKR Governance after that.

1 Like