MIP10c9-SP21: Subproposal to whitelist Set for AAVE/USD Oracle Access

Core Units Oracles
,
#1

MIP10c9-SP21: Subproposal to whitelist Set Protocol for AAVE/USD Oracle Access

Preamble

MIP10c9-SP#: 21
Author(s): Alex Soong
Contributors: Alex Soong
Status: Formal Submission
Date Proposed: 2020-12-31
Date Ratified: <yyyy-mm-dd>

Specification

Introduction

Net asset value (NAV) issuance allows Set users to issue Sets based on the prices of the component tokens within a Set. To enable NAV issuance for a wider variety of Set compositions, we are requesting access to additional Maker oracles.

Oracle Name

AAVE/USD

Customer(s)

Alex Soong - [email protected]

Whitelist

AAVE Oracle Proxy - 0x8b1C079f8192706532cC0Bf0C02dcC4fF40d045D - Median (0xe62872DFEbd323b03D27946f8e2491B454a69811)

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.

3 Likes
Maker Relay Ep. 27 - en español (Feliz 2021)
Maker Relay Ep 27- Happy 2021
#2

After reviewing the provided OracleProxy contract the Oracle Domain Team has concluded the Oracle data is not stored in memory and is accessible exclusively by authorized parties. The contract also includes a function to change to new Oracle address which will facilitate migration should the need arise.

#3

This topic was automatically closed 91 days after the last reply. New replies are no longer allowed.