Proposal: Medianizer V2 access for DDEX

MIP10c9: Subproposal to Whitelist Oracle Access

Preamble

MIP10c9-SP#: 8
Author(s): Scott Winges
Contributors: Nik Kunkel
Type: Process Component
Status:
Date Proposed: <2020-09-09>
Date Ratified: <yyyy-mm-dd>

Specification

Introduction

DDEX used the Maker medianizer oracle v1 for ETH/USD price info prior to deprecation. The price is primarily used for determining the collateral status of loans, but is also used for several other information fields on the application. DDEX would use the v2 medianizer for the same purposes.

Oracle Name

  • ETH/USD

Customer(s)

Whitelist

- DDEX - 0xf39cCf729F6C8082ee1Ae598Fc757647c3ebddf0 - Medianizer

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? no
  • Is Oracle data written to storage? no
  • If Oracle data is stored, is it stored in a private variable? no
  • If Oracle data is stored, is the value accessible on-chain exclusively by the protocol? no

Fee

1 Like

Hi Scott,

Please fill out one of these templates and edit your original post.

Thank you,
Nik

2 Likes

Thanks Nik! Edited, adding a wbtc proposal too.