MIP10c9-SP10: Whitelist Yearn Finance on BTCUSD Oracle

MIP10c9-SP10: Subproposal to Whitelist Yearn Finance on BTCUSD Oracle

Preamble

MIP10c9-SP#: 10
Author(s): Artem K
Contributors:
Type: Process Component
Status:
Date Proposed: 2020-09-16
Date Ratified:

Specification

Introduction

Yearn’s core product is Vaults which allow depositing certain assets which are then delegated to Strategies which farm and recycle the rewards back into the base asset. A more complex product is Delegated Vaults which leverage a certain asset to borrow another asset and delegate it to a Vault.

We are currently building our second Maker-based vault that will leverage WBTC-A ilk in a similar manner to our yWETH vault that uses ETH-A ilk. It will maintain a Maker Vault and delegate the drawn DAI to the yearn DAI Vault. To make the strategy able to rebalance and unwind, we require access to the next OSM price.

We’ll be using a permissioned proxy contract should new strategies requiring the OSM emerge. It is controlled by yearn’s governance.

Oracle Name

BTC/USD

Customer(s)

yearn finance - Andre Cronje ([email protected])

Whitelist

yearn finance - 0x82c93333e4E295AA17a05B15092159597e823e8a - 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? not stored
- If Oracle data is stored, is the value accessible on-chain exclusively by the protocol? not stored

Fee

yearn finance - ROMP

7 Likes

I support this 300%

@NikKunkel can we fastrack this through signals like we did for Eth price feed?

Assuming @Oracles approves (and submits the required PR), it meets the cutoff to go on-chain on Monday anyway, no fast tracking required.

3 Likes