diff --git a/MIP10/MIP10c14-Subproposals/MIP10c14-SP1.md b/MIP10/MIP10c14-Subproposals/MIP10c14-SP1.md new file mode 100644 index 000000000..f1bd8f66f --- /dev/null +++ b/MIP10/MIP10c14-Subproposals/MIP10c14-SP1.md @@ -0,0 +1,55 @@ +## Preamble + +``` +MIP10c14-SP#: 1 +Author(s): Deniz Omer +Contributors: Nik Kunkel +Status: Accepted +Date Proposed: 2020-05-24 +Date Ratified: 2020-07-4 +``` + +## Disclaimer +MIP10 is meant to handle all of the Oracle related actions. Unfortunately MIP10 has inconsistencies and doesn’t conform to the monthly governance cadence that the Maker Improvement Proposal framework is built around. This has generated a backlog of Oracle proposals. While MIP10 is refactored to conform to the regular MIP process, Oracle proposals such as this one will utilize the more liberal weekly governance cycle. While strictly speaking this makes them not subproposals, they are included in the subproposal archive as a point of provenance to serve as a paper trail. + +## Specification + +### Organization + +* Name: Kyber Network Reserves Limited +* Website: https://kyber.network/ +* Github: https://github.com/kybernetwork +* Email: hello@kyber.network +* Incorporated: British Virgin Islands +* Domiciled: British Virgin Islands +* Number of employees: 0 +* When was the organization founded? 21 March 2018 +* Who are the major investors in your organization? Kyber Network Reserves Limited is a wholly owned subsidiary of Jedha Holdings Private Limited, a Singapore-incorporated entity. Funding is from Jedha Holdings. +* How much funding has the organization raised either privately or through a token sale? Jedha Holdings Private Limited’s subsidiary, Kyber Network Private Limited, also a Singapore-incorporated entity, raised 200,000 Ethers (equivalent to USD52m based on ETH:USD pricing at the close of the token sale) in an ICO that was completed in September 2017 in Singapore. +* Please provide public references for the above where possible. (https://icodrops.com/kybernetwork/) + +### Introduction + +* Motivation for running a Light Feed + +As deeply passionate members of the Ethereum community we recognize the importance of trustless oracles in the functioning of a healthy DeFi landscape, and with more than two years of experience working on on-chain liquidity provision we want to take the next step and contribute to the further diversification of the trustless Oracles. We are really looking forward to the growth of both the DeFi space and MakerDAO. + +### Community + +* What has your organization contributed to the crypto community? + +The team’s main focus and contribution over the last 3 years has been building Kyber Network protocol, an on-chain liquidity protocol that aggregates liquidity from a wide range of reserves and enables token exchange in any decentralized application. It also contributed through grants to Ethereum teams at very early stages (ie. Instadapp) and is an active member of the Ethereum community +* Successful products, services, tools, libraries, thought-leadership + +Apart from Kyber Network, the various founders have been involved in: + - Oyente - an analysis tool for smart contracts + - PeaceRelay - a protocol to trustlessly connect EVM-compatible blockchains. + - Smartpool - a decentralized PoW mining pool using smart contracts + - Elastico - a sharding protocol for public blockchains. +* How will the Maker Community benefit from your inclusion as a Light Feed? + +The Kyber team have gained valuable experience building one of the largest liquidity providers to the DeFi space over the last three years, and their addition as a stakeholder to the trustless Oracles further contributes to the strengthening of the expertise and know-how within the MakerDAO ecosystem. + +### Changelog + - reformatted preamble + - added disclaimer diff --git a/MIP10/MIP10c14-Subproposals/MIP10c14-SP2.md b/MIP10/MIP10c14-Subproposals/MIP10c14-SP2.md new file mode 100644 index 000000000..d79d4b799 --- /dev/null +++ b/MIP10/MIP10c14-Subproposals/MIP10c14-SP2.md @@ -0,0 +1,53 @@ +## Preamble + +``` +MIP10c14-SP#: 2 +Author(s): Michael Wuehler +Contributors: Nik Kunkel +Status: Accepted +Date Proposed: 2020-05-28 +Date Ratified: 2020-07-04 +``` + +## Disclaimer +MIP10 is meant to handle all of the Oracle related actions. Unfortunately MIP10 has inconsistencies and doesn’t conform to the monthly governance cadence that the Maker Improvement Proposal framework is built around. This has generated a backlog of Oracle proposals. While MIP10 is refactored to conform to the regular MIP process, Oracle proposals such as this one will utilize the more liberal weekly governance cycle. While strictly speaking this makes them not subproposals, they are included in the subproposal archive as a point of provenance to serve as a paper trail. + +## Specification + +### Organization + +- Name: Infura +- Website: https://infura.io +- Github: https://github.com/infura +- Number of Employees: 26 +- Email: hello@infura.io +- Incorporated: Switzerland +- Domiciled: Switzerland +- When was the organization founded? 2014 +- Who are the major investors in your organization? Infura is a wholly owned operating unit of ConsenSys AG. +- How much funding has the organization raised either privately or through a token sale? ConsenSys AG is privately funded. +- Please provide public references for the above where possible. Not Available. + +### Introduction + +- Motivation for running a Light Feed + +Infura has been an infrastructure provider for Ethereum API access for 4 years. We are a well funded team with experienced DevOps engineers delivering reliable, always-on access to Ethereum. We are excited at the process Maker is taking at decentralizing what has become a systemically critical piece of the Web3 ecosystem, we want to contribute to this mission and have the skills and reputation to do so. + +### Community + +- What has your organization contributed to the crypto community? + +We are close partners with the client development teams and regularly provide feedback and contribute code based on our findings running nodes at scale. In addition, we have made several grants over the years to projects focused on improving the capabilities and efficiency of running node infrastructure. These include TurboGeth and VIPNode. We are extremely active in the conferences and Devcon, both in financially supporting them as well as participating in them. + +- Successful products, services, tools, libraries, thought-leadership + +Infura has always been a free service for developers to get an easy entry into Ethereum development. We also have Infura+, a premium offering for projects as they mature and get to the stage of depending on their infrastructure in production. In addition, we have supported IPFS for 4 years and have a premium IPFS product set to launch this year. We have built and open-sourced the Versus tool that allows anyone to compare performance of RPC endpoints. + +- How will the Maker Community benefit from your inclusion as a Light Feed? + +Infura will be a trusted addition to the existing oracle light feed providers. Our reputation will add to the already robust group of stakeholders. + +### Changelog + - reformatted preamble + - added disclaimer diff --git a/MIP10/MIP10c14-Subproposals/MIP10c14-SP3.md b/MIP10/MIP10c14-Subproposals/MIP10c14-SP3.md new file mode 100644 index 000000000..93090ca45 --- /dev/null +++ b/MIP10/MIP10c14-Subproposals/MIP10c14-SP3.md @@ -0,0 +1,52 @@ +## Preamble + +``` +MIP10c14-SP#: 3 +Author(s): Elvis Hee +Contributors: Nik Kunkel +Status: Accepted +Date Proposed: 2020-06-11 +Date Ratified: 2020-07-04 +``` + +## Disclaimer +MIP10 is meant to handle all of the Oracle related actions. Unfortunately MIP10 has inconsistencies and doesn’t conform to the monthly governance cadence that the Maker Improvement Proposal framework is built around. This has generated a backlog of Oracle proposals. While MIP10 is refactored to conform to the regular MIP process, Oracle proposals such as this one will utilize the more liberal weekly governance cycle. While strictly speaking this makes them not subproposals, they are included in the subproposal archive as a point of provenance to serve as a paper trail. + +## Specification + +### Organization + +* Name - Etherscan +* Website - https://etherscan.io/ +* Github - https://github.com/etherscan/ +* Number of Employees - 15 +* Email - info@etherscan.io +* Incorporated - 2016 +* Domiciled - Malaysia +* When was the organization founded? - 2015 +* Who are the major investors in your organization? - BoostVC, Coinbase, DCG +* How much funding has the organization raised either privately or through a token sale? - Etherscan is privately funded +* Please provide public references for the above where possible. - https://etherscan.io/aboutus + +### Introduction +* Motivation for running a Light Feed + +To provide independent transparency and decentralization for the ecosystem. + +### Community +* What has your organization contributed to the crypto community? + +Etherscan has been a block explorer in the Ethereum ecosystem for the past 4 years. +We have worked closely with countless projects in providing support to display on-chain and off-chain data. + +* Successful products, services, tools, libraries, thought-leadership + +The leading Ethereum Block explorer, analytics and api service provider for the eco-system. + +* How will the Maker Community benefit from your inclusion as a Light Feed? + +As a Light Feed we believe our ethos of neutrality and impartiality will help in providing a reliable source of pricing data. + +### Changelog + - reformatted preamble + - added disclaimer diff --git a/MIP10/MIP10c14-Subproposals/MIP10c14-SP4.md b/MIP10/MIP10c14-Subproposals/MIP10c14-SP4.md new file mode 100644 index 000000000..ed5dd2c82 --- /dev/null +++ b/MIP10/MIP10c14-Subproposals/MIP10c14-SP4.md @@ -0,0 +1,63 @@ +## Preamble + +``` +MIP10c14-SP#: 4 +Author(s): Kevin Owocki +Contributors: Kevin Owocki , Nik Kunkel +Status: Accepted +Date Proposed: 2020-06-10 +Date Ratified: 2020-07-04 +``` + +## Disclaimer +MIP10 is meant to handle all of the Oracle related actions. Unfortunately MIP10 has inconsistencies and doesn’t conform to the monthly governance cadence that the Maker Improvement Proposal framework is built around. This has generated a backlog of Oracle proposals. While MIP10 is refactored to conform to the regular MIP process, Oracle proposals such as this one will utilize the more liberal weekly governance cycle. While strictly speaking this makes them not subproposals, they are included in the subproposal archive as a point of provenance to serve as a paper trail. + +## Specification + +### Organization +- Name: Gitcoin +- Website: https://gitcoin.co +- Github: https://github.com/gitcoinco/web +- Number of Employees: 16 +- Email: Kevin@gitcoin.co +- Incorporated: A subsidiary of Consensys AG, based in Switzerland +- Domiciled: Switzerland +- Number of employees: 16 +- When was the organization founded? Gitcoin was founded in May 2017, and folded into the Consensys Mesh in November 2017. +- Who are the major investors in your organization? Consensys AG +- How much funding has the organization raised either privately or through a token sale? About $3mm from Consensys AG +- Please provide public references for the above where possible: + +https://gitcoin.co +https://media.consensys.net/gitcoin-joins-consensys-announces-pilot-projects-f5a0955de9d6 +https://gitcoin.co/results + +### Introduction +Gitcoin’s mission is to grow open source and help devs find new economic opportunities. + +There are many ways to do this, and gitcoin offers a few different products to enable this: + +- Virtual hackathons: Online & worldwide. Sponsors post prizes, and people compete to earn them by building stuff to the specifications. +- Grants: A better way to fund innovation in your ecosystem. Grantees can create a fundraising page for “the great work they’re already doing” in the space, then raise $$$ for that work. +- Ethical ads via CodeFund: An advertising network that respects your privacy. Codefund allows you to monetize your audience without selling them out. + + +### Community +- What has your organization contributed to the crypto community? + +We have delivered almost $5mm worth of funding to OSS devs in the Ethereum community. https://gitcoin.co/results + +- Successful products, services, tools, libraries, thought-leadership + +https://gitcoin.co/products +I've also given talks at ETHDenver, ETHBerlin, Devcon, etc. https://owocki.com/public-speaking/ + +- How will the Maker Community benefit from your inclusion as a Light Feed? + +We will be faithful & responsible stewards of the data passed into the MKR Oracle system. + +Note that DAI/SAI are some of the most used tokens on the Gitcoin platform! We have a rational economic incentive to keep the price data clean & good! https://gitcoin.co/leaderboard/tokens?cadence=quarterly&keyword=all&product=all + +### Changelog + - reformatted preamble + - added disclaimer diff --git a/MIP10/MIP10c14-Subproposals/MIP10c14-SP5.md b/MIP10/MIP10c14-Subproposals/MIP10c14-SP5.md new file mode 100644 index 000000000..50c689064 --- /dev/null +++ b/MIP10/MIP10c14-Subproposals/MIP10c14-SP5.md @@ -0,0 +1,56 @@ +## Preamble + +``` +MIP10c14-SP#: 5 +Author(s): Itamar Lesuisse +Contributors: +Status: Formal Submission +Date Proposed: 2020-07-02 +Date Ratified: +``` + +## Disclaimer + +MIP10 is meant to handle all of the Oracle related actions. Unfortunately MIP10 has inconsistencies and doesn't conform to the monthly governance cadence that the Maker Improvement Proposal framework is built around. This has generated a backlog of Oracle proposals. While MIP10 is refactored to conform to the regular MIP process, Oracle proposals such as this one will utilize the more liberal weekly governance cycle. While strictly speaking this makes them not subproposals, they are included in the subproposal archive as a point of provenance to serve as a paper trail. + +## Specification + +### Organization + +* Name: Argent Labs Limited +* Website: https://www.argent.xyz +* Github: https://github.com/argentlabs +* Email: hello@argent.xyz +* Incorporated: United Kingdom +* Domiciled: United Kingdom +* Number of employees: 23 +* When was the organization founded? 4 December 2017 +* Who are the major investors in your organization? Paradigm, Index Ventures, Creandum +* How much funding has the organization raised either privately or through a token sale? $16m in equity funding +* Please provide public references for the above where possible. References for funding: +[Cityam](https://www.cityam.com/sequoia-crypto-fund-paradigm-makes-first-europe-investment-with-london-startup-argent/) +[Companies House](https://beta.companieshouse.gov.uk/company/11093638/filing-history) +[Crunchbase](https://www.crunchbase.com/organization/argent) + +### Introduction + +**Motivation for running a Light Feed** + +We want to actively support important projects in the Ethereum ecosystem, making them more robust and reliable. Maker Oracles are significant infrastructure that we believe we have the resources and technical talent to contribute to. + +### Community + +**What has your organization contributed to the crypto community?** + +Argent has built a simple and safe wallet for consumers. This has pioneered non-custodial crypto without seed phrases or gas (we use meta-transactions), and with security measures such as daily transfer limits and whitelisting contacts. In addition Argent provides easy access to integrated Dapps, including Maker DSR and, soon, Maker Vaults. In recent months we've seen significant adoption of DAI from users in Latin America. Argent's smart contract architecture is open source. Aside from our core wallet, we also developed Hopper, an open source privacy mixer, before handing it over to the community for further development. + +**Successful products, services, tools, libraries, thought-leadership** + +* You can find our wallet here: [https://www.argent.xyz/](https://www.argent.xyz/). +* Our smart contracts are open source and available here: [https://github.com/argentlabs/argent-contracts/tree/master](https://github.com/argentlabs/argent-contracts/tree/master). +* Our blog: [https://www.argent.xyz/blog/](https://www.argent.xyz/blog/). +* Some recent talks: [https://www.youtube.com/playlist?list=PLv2mJCRJoTfPH1rYCWLMzs4j8Eu8kLHpb](https://www.youtube.com/playlist?list=PLv2mJCRJoTfPH1rYCWLMzs4j8Eu8kLHpb) + +**How will the Maker Community benefit from your inclusion as a Light Feed?** + +We comprise a strong technical team of experienced engineers and PhDs, who have been building secure crypto products for a mass audience for two years. The team would add geographic diversification too: it is based across Europe, from Northern Ireland to Bulgaria, Spain to Slovenia. \ No newline at end of file diff --git a/MIP10/MIP10c14-Subproposals/MIP10c14-SP6.md b/MIP10/MIP10c14-Subproposals/MIP10c14-SP6.md new file mode 100644 index 000000000..4fac6c3f6 --- /dev/null +++ b/MIP10/MIP10c14-Subproposals/MIP10c14-SP6.md @@ -0,0 +1,58 @@ +# MIP10c14: Subproposal to Appoint MyCrypto as a Light Feed for the Maker Oracles + +## Preamble +``` +MIP10c14-SP#6: +Author(s): Harry Denley +Contributors: Jordan Spence, Mia Alexander +Type: Process Component +Status: Proposed +Date Proposed: 2020-07-13 +Date Ratified: +``` + +## Specification + +### Organization +- Name: MyCrypto +- Website: https://mycrypto.com +- Github: https://github.com/MyCryptoHQ +- Number of Employees: 15-20 +- Email: jordan@mycrypto.com +- Incorporated: 2018 +- Domiciled: Delaware C Corp +- When was the organization founded? 2018 +- Who are the major investors in your organization?: Polychain, ShapeShift, BoostVC, Ausum Ventures, Mick Hagen, Chance Du, Lily Liu, Albert Ni +- How much funding has the organization raised either privately or through a token sale?: $4 Million +- Please provide public references for the above where possible: https://medium.com/mycrypto/our-first-funding-round-9acf048c9d05 + +### Introduction +- Motivation for running a Light Feed + +MyCrypto has provided infrastructure for the Ethereum blockchain for many years, and are one of the few teams to do so. We love the Maker team, and +our engineers are experienced, reliable, and eager to learn more and contribute to Maker’s goals in this arena! + +### Community +- What has your organization contributed to the crypto community? + +MyCrypto provides a client-side, open-source interface to the Ethereum blockchain that allows users to access and manage their ETH & +ERC20 tokens, and interact with smart contracts directly, among many other things. We also provide infrastructure with an Ethereum node, alongside +Infura and Etherscan. + +- Successful products, services, tools, libraries, thought-leadership + +MyCrypto.com (mycrypto.com) +MyCrypto Desktop App (download.mycrypto.com) +MyCrypto Beta (beta.mycrypto.com) +MyCrypto Overflow (overflow.mycrypto.com) +CryptoScamDB (cryptoscamdb.org) +MyCrypto Medium (medium.com/mycrypto) + +- How will the Maker Community benefit from your inclusion as a Light Feed? + +MyCrypto has a solid track record of providing valuable products, resources, and infrastructure to the community. Many don’t realize it but +we’ve been running our own infrastructure since 2017. This runs in our blood! We believe that we’d be a valuable addition to the others +who are participating. + +### Changelog +- List of updates diff --git a/MIP10/MIP10c14-Subproposals/placeholder.md b/MIP10/MIP10c14-Subproposals/placeholder.md deleted file mode 100644 index 48cdce852..000000000 --- a/MIP10/MIP10c14-Subproposals/placeholder.md +++ /dev/null @@ -1 +0,0 @@ -placeholder diff --git a/MIP10/MIP10c15-Subproposals/MIP10c15-SP1.md b/MIP10/MIP10c15-Subproposals/MIP10c15-SP1.md new file mode 100644 index 000000000..f02267262 --- /dev/null +++ b/MIP10/MIP10c15-Subproposals/MIP10c15-SP1.md @@ -0,0 +1,113 @@ +## Preamble + +``` +MIP10c15-SP#: 1 +Author(s): Nik Kunkel +Contributors: +Status: Formal Submission +Date Proposed: 2020-05-29 +Date Ratified: +``` + +## Disclaimer +MIP10 is meant to handle all of the Oracle related actions. Unfortunately MIP10 has inconsistencies and doesn’t conform to the monthly governance cadence that the Maker Improvement Proposal framework is built around. This has generated a backlog of Oracle proposals. While MIP10 is refactored to conform to the regular MIP process, Oracle proposals such as this one will utilize the more liberal weekly governance cycle. While strictly speaking this makes them not subproposals, they are included in the subproposal archive as a point of provenance to serve as a paper trail. + +## Specification + +### Introduction + +If ratified, this subproposal would appoint Kyber Network as a Light Feed. Feeds submit data to the Oracles for the prices of assets. They are an important part of ensuring that the Oracles are reliable and secure. Only entities with strong credentials that the community trusts should be permitted to be an Oracle Feed. + +### Organization + +The following information was provided by Kyber Network in their MIP10c14 application and verified by the Oracle Team to the best of its ability. + +> * Name: Kyber Network Reserves Limited +> * Website: https://kyber.network/ +> * Github: https://github.com/kybernetwork +> * Email: hello@kyber.network +> * Incorporated: British Virgin Islands +> * Domiciled: British Virgin Islands +> * Number of employees: 0 +> * When was the organization founded? 21 March 2018 +> * Who are the major investors in your organization? Kyber Network Reserves Limited is a wholly owned subsidiary of Jedha Holdings Private Limited, a Singapore-incorporated entity. Funding is from Jedha Holdings. +> +> * How much funding has the organization raised either privately or through a token sale? Jedha Holdings Private Limited’s subsidiary, Kyber Network Private Limited, also a Singapore-incorporated entity, raised 200,000 Ethers (equivalent to USD52m based on ETH:USD pricing at the close of the token sale) in an ICO that was completed in September 2017 in Singapore. +> +> * Please provide public references for the above where possible. (https://icodrops.com/kybernetwork/) + +### Light Feeds + +**Reputation** + +- Does the organization have a strong reputation in the crypto community? + +Yes, Kyber Networks has been one of the main contributors in the Ethereum space going as far back as 2017. They are one of only a handful of projects to be directly endorsed by Vitalik Buterin, the founder of Ethereum. Since their launch they’ve been one of the major liquidity providers in the DEX space and easily one of the most frequently used dapps. + +- What contributions has this organization made to the crypto ecosystem? + +The team’s main focus and contribution over the last 3 years has been building the Kyber Network protocol, an on-chain liquidity protocol that aggregates liquidity from a wide range of reserves and enables token exchange in any decentralized application. It also contributed through grants to Ethereum teams at very early stages (ie. Instadapp) and is an active member of the Ethereum community + +- Would including the organization as a Light Feed instill a sense of trust in the Oracles? + +It is the opinion of the Oracle Team that Kyber has a trustworthy reputation in the community and would further reinforce the reputation of the Maker Oracles. + +- Are there any public accusations of misconduct? How severe and numerous are they? Have they been confirmed? + +The Oracle Team was not able to find any record of confirmed cases of misconduct on account of the organization nor its executive staff. + +**Verification** + +- Were sufficient public-facing resources provided or found that confirm the information in the application? + +Yes, public records were able to verify most of the provided information. + +- Was the applicant honest with respect to: + +- the investors + +While the Oracle Team was not able to confirm that Kyber Network Reserves Limited is owned by Jedha Holdings Private Limited, it was able to confirm the existence and active status of Jedha Holdings Private Limited in Singapore through the Singaporean Accounting and Corporate Regulatory Authority (ACRA) with an address of 1 Upper Circular Road #050-01 Singapore 058400 and UEN 201803106C. + +- how much funding was raised + +The Oracle Team was able to confirm that 200,000 ETH was raised in an ICO in September 2017 + +- the number of employees + +The Oracle Team was not able to verify the number of employees. + +- the location of incorporation & domicile + +The Oracle Team was able to verify the entity is domiciled in the British Virgin Islands through records supplied by the British Virgin Islands Financial Services Commission. + +- Given the applicant's major investors, is there a risk adding this Light Feed would give a single investor too much influence over the Oracle protocol? + +No. + +- Given the incorporation and domicile location of the organization, is there a risk adding this Light Feed would give a single jurisdiction too much influence over the Oracle protocol? + +No. + +**Identity** + +- Did the Oracle Team get in contact with the organization to confirm their application? + +Yes, the Oracle Team spoke to representatives from the Kyber Networks team over video conference who are listed on the organization’s website. + +### Cost-Benefit + +- Given the ratio of Dark Feeds : Light Feeds, does the Maker Protocol benefit from adding another Dark/Light Feed at this time? + +Yes. + +- Given the extra cost of appointing a new Feed, does the benefit of the marginal security / marginal trust in the protocol exceed the cost? + +Yes. + +### Oracle Team Recommendation + +The Oracle Team recommends that Maker Governance ratify the proposal to appoint Kyber Network as a Light Feed for the Maker Oracles. Kyber Network has a strong brand and reputation in the ecosystem which are the primary requirements to look for in a potential Feed partner. The Oracle Team was able to verify the information provided by Deniz Omer in the MIP10c14 Light Feed application through government public records and cursory googling. No confirmed cases of misconduct related to the organization were found. + +### Changelog + - reformatted preamble + - added disclaimer \ No newline at end of file diff --git a/MIP10/MIP10c15-Subproposals/MIP10c15-SP2.md b/MIP10/MIP10c15-Subproposals/MIP10c15-SP2.md new file mode 100644 index 000000000..ded5752ef --- /dev/null +++ b/MIP10/MIP10c15-Subproposals/MIP10c15-SP2.md @@ -0,0 +1,111 @@ +## Preamble + +``` +MIP10c15-SP#: 2 +Author(s): Nik Kunkel +Contributors: +Status: Formal Submission +Date Proposed: 2020-05-29 +Date Ratified: +``` + +## Disclaimer +MIP10 is meant to handle all of the Oracle related actions. Unfortunately MIP10 has inconsistencies and doesn’t conform to the monthly governance cadence that the Maker Improvement Proposal framework is built around. This has generated a backlog of Oracle proposals. While MIP10 is refactored to conform to the regular MIP process, Oracle proposals such as this one will utilize the more liberal weekly governance cycle. While strictly speaking this makes them not subproposals, they are included in the subproposal archive as a point of provenance to serve as a paper trail. + +## Specification + +### Introduction + +If ratified, this subproposal would appoint Infura as a Light Feed. Feeds submit data to the Oracles for the prices of assets. They are an important part of ensuring that the Oracles are reliable and secure. Only entities with strong credentials that the community trusts should be permitted to be an Oracle Feed. + +### Organization + +The following information was provided by Infura in their MIP10c14 application and verified by the Oracle Team to the best of its ability. + +> * Name: Infura +> * Website: [https://infura.io](https://infura.io/) +> * Github: https://github.com/infura +> * Email: hello@infura.io +> * Incorporated: Switzerland +> * Domiciled: Switzerland +> * Number of employees: 26 +> * When was the organization founded? 2014 +> * Who are the major investors in your organization? -Infura is a wholly owned operating unit of ConsenSys AG. +> * How much funding has the organization raised either privately or through a token sale? ConsenSys AG is privately funded. +> * Please provide public references for the above where possible. Not Available. + +### Light Feeds + +**Reputation** + +- Does the organization have a strong reputation in the crypto community? + +Infura has been the bedrock of supplying connectivity to the Ethereum blockchain for tens of millions of cryptocurrency users. Serving as the networking layer for every day applications like MetaMask and many of the top dapps including the Maker Foundation, it’s no secret that Infura is a critical part of the Ethereum ecosystem and rightfully carries a reputation of reliability and ecosystem stalwart. Being a part of the Consensys brand which is responsible for shepherding Ethereum into enterprise partnership after enterprise partnership just further reinforces the credible forces behind Infura. + +- What contributions has this organization made to the crypto ecosystem? + +Infura is close partners with the client development teams and regularly provides feedback and contributes code based on its findings running nodes at scale. In addition, Infura has made several grants over the years to projects focused on improving the capabilities and efficiency of running node infrastructure. These include TurboGeth and VIPNode. Infurai is extremely active in conferences, including Devcon, both in financially supporting them as well as participating in them. + +- Would including the organization as a Light Feed instill a sense of trust in the Oracles? + +As noted above, the Oracle Team believes that Infura has a trustworthy reputation in the community and would further reinforce the reputation of the Maker Oracles. + +- Are there any public accusations of misconduct? How severe and numerous are they? Have they been confirmed? + +The Oracle Team was not able to find any record of confirmed cases of misconduct on account of the organization nor its executive staff. + +**Verification** + +- Were sufficient public-facing resources provided or found that confirm the information in the application? + +Yes, public records were able to verify most of the provided information. + +- Was the applicant honest with respect to: + +- the investors + +Infura was acquired by Consensys on 10/04/19. The Oracle Team was able to find a public announcement of an investment of $10 million USD by SK Group on 07/02/19 into Infura’s parent company Consensys. + +- how much funding was raised + +Outside of the $10 million USD investment by SK Group into Consensys, the Oracle Team was unable to identify any other public announcements of funding by neither Infura nor Consensys. + +- the number of employees + +The Oracle Team was able to verify through its network that the number of employees claimed by Infura in their application is highly likely to be correct. + +- the location of incorporation & domicile + +The Oracle Team was able to verify that Consensys AG is registered and domiciled in Zug, Switzerland at address Gartenstrasse 6, 6300 Zug via [Zefix](https://www.zefix.ch/en/search/entity/list/firm/1266173). + +- Given the applicant's major investors, is there a risk adding this Light Feed would give a single investor too much influence over the Oracle protocol? + +No. + +- Given the incorporation and domicile location of the organization, is there a risk adding this Light Feed would give a single jurisdiction too much influence over the Oracle protocol? + +No. + +**Identity** + +- Did the Oracle Team get in contact with the organization to confirm their application? + +Yes, the Oracle Team spoke to Michael Wuehler the CoFounder and Head of Operations at Infura over video conference who is listed on the company’s website. + +### Cost-Benefit + +- Given the ratio of Dark Feeds : Light Feeds, does the Maker Protocol benefit from adding another Dark/Light Feed at this time? + +Yes. + +- Given the extra cost of appointing a new Feed, does the benefit of the marginal security / marginal trust in the protocol exceed the cost? + +Yes. + +### Oracle Team Recommendation + +The Oracle Team recommends that Maker Governance ratify the proposal to appoint Infura as a Light Feed for the Maker Oracles. Infura's reputation within the industry as the backbone of connectivity to the Ethereum blockchain, present in everyday services like MetaMask, makes them a clear favorite to partner with to decentralize and secure Maker’s Oracles. Being owned by Consensys, itself founded and led by Ethereum cofounder Joe Lubin, just further cements the trustworthiness of Infura. The Oracle Team was able to verify the claims made by Infura in their application. + +### Changelog + - reformatted preamble + - added disclaimer \ No newline at end of file diff --git a/MIP10/MIP10c15-Subproposals/MIP10c15-SP3.md b/MIP10/MIP10c15-Subproposals/MIP10c15-SP3.md new file mode 100644 index 000000000..cbc091a74 --- /dev/null +++ b/MIP10/MIP10c15-Subproposals/MIP10c15-SP3.md @@ -0,0 +1,114 @@ +## Preamble + +``` +MIP10c15-SP#: 3 +Author(s): Nik Kunkel +Contributors: +Status: Formal Submission +Date Proposed: 2020-06-14 +Date Ratified: +``` + +## Disclaimer +MIP10 is meant to handle all of the Oracle related actions. Unfortunately MIP10 has inconsistencies and doesn’t conform to the monthly governance cadence that the Maker Improvement Proposal framework is built around. This has generated a backlog of Oracle proposals. While MIP10 is refactored to conform to the regular MIP process, Oracle proposals such as this one will utilize the more liberal weekly governance cycle. While strictly speaking this makes them not subproposals, they are included in the subproposal archive as a point of provenance to serve as a paper trail. + +## Specification + +### Introduction + +If ratified, this subproposal would appoint Etherscan as a Light Feed. Feeds submit data to the Oracles for the prices of assets. They are an important part of ensuring that the Oracles are reliable and secure. Only entities with strong credentials that the community trusts should be permitted to be an Oracle Feed. + +### Organization + +> * Name - Etherscan +> * Website - https://etherscan.io/ +> * Github - https://github.com/etherscan/ +> * Number of Employees - 15 +> * Email - info@etherscan.io +> * Incorporated - 2016 +> * Domiciled - Malaysia +> * When was the organization founded? - 2015 +> * Who are the major investors in your organization? - BoostVC, Digital Currency Group (DCG), Coinbase Ventures, +> * How much funding has the organization raised either privately or through a token sale? - Etherscan is privately funded +> * Please provide public references for the above where possible. - https://etherscan.io/aboutus + +### Light Feeds + +**Reputation** + +- Does the organization have a strong reputation in the crypto community? + +Yes. Etherscan has been a public utility going back many years. It has become the de-facto standard when referencing Ethereum transactions and is used by a diverse array of casual users as well as developers. + +- What contributions has this organization made to the crypto ecosystem? + +The team has developed a platform that embodies the ideas of decentralization and transparency that underpin the Ethereum blockchain. Users can track any on-chain activity, including the movement of tokens and the details surrounding pending and completed transactions. Projects verifying their smart contracts' source code on Etherscan is so engrained in the Ethereum ecosystem it's become not just a standard, but rather a requirement that users expect. + + +- Would including the organization as a Light Feed instill a sense of trust in the Oracles? + +Etherscan is a critical piece of infrastructure used daily by thousands of people around the world without which the quality of Ethereum ecosystem would not have become what it is today. It is the opinion of the Oracle Team that Etherscan has a trustworthy reputation in the community and would further reinforce the reputation of the Maker Oracles. + +- Are there any public accusations of misconduct? How severe and numerous are they? Have they been confirmed? + +The Oracle Team was not able to find any record of confirmed cases of misconduct on account of the organization nor its executive staff. + +**Verification** + +- Were sufficient public-facing resources provided or found that confirm the information in the application? + +Yes, public records were able to verify most of the provided information. + +- Was the applicant honest with respect to: + +- the investors + +The Oracle Team was able to verify Etherscan: + as a portfolio company on the [BoostVC website](https://www.boost.vc/portfolio). + as a portfolio company on the [Digital Currency Group (DCG) website](https://dcg.co/portfolio/). + as a portfolio company on the [Coinbase Ventures website](https://ventures.coinbase.com/). + +- how much funding was raised + +The Oracle Team was not able to find any public figures relating to the amount of funding raised in the 11/01/16 Seed round composed of BoostVC and Digital Currency Group nor of the amount invested by Coinbase Ventures more recently. + +- the number of employees + +The Oracle Team was not able to verify the number of employees. A cursory search through LinkedIn showed 7 profiles claiming to work at Etherscan that correspond to employees listed on the [Etherscan About Us page](https://etherscan.io/aboutus). + +- the location of incorporation & domicile + +The Oracle Team found multiple sources online citing that Etherscan.io was based out Kualu Lampur, Malaysia but was not able to find an entity registered under that name with the [Companies Commission of Malaysia](https://www.ssm-einfo.my/) + +- Given the applicant's major investors, is there a risk adding this Light Feed would give a single investor too much influence over the Oracle protocol? + +No. + +- Given the incorporation and domicile location of the organization, is there a risk adding this Light Feed would give a single jurisdiction too much influence over the Oracle protocol? + +No. + +**Identity** + +- Did the Oracle Team get in contact with the organization to confirm their application? + +Yes, the Oracle Team spoke to representatives from the Etherscan team over video conference who are listed on the organization’s website. + +### Cost-Benefit + +- Given the ratio of Dark Feeds : Light Feeds, does the Maker Protocol benefit from adding another Dark/Light Feed at this time? + +Yes. + +- Given the extra cost of appointing a new Feed, does the benefit of the marginal security / marginal trust in the protocol exceed the cost? + +Yes. + +### Oracle Team Recommendation + +The Oracle Team recommends that Maker Governance ratify the proposal to appoint Etherscan as a Light Feed for the Maker Oracles. +Having provided the infrastructure for a compelling web of decentralization and transparency of Ethereum since as far back as 2015, Etherscan has cemented itself as a core member of the Ethereum ecosystem that embodies its values. The Oracle Team was able to verify most of the information provided by Elvis in the MIP10c14 Light Feed application however was unable to confirm the amount of funding raised nor the existance of the legal entity in the claimed domicile. No confirmed cases of misconduct related to the organization were found. + +### Changelog + - reformatted preamble + - added disclaimer \ No newline at end of file diff --git a/MIP10/MIP10c15-Subproposals/MIP10c15-SP4.md b/MIP10/MIP10c15-Subproposals/MIP10c15-SP4.md new file mode 100644 index 000000000..2d1536945 --- /dev/null +++ b/MIP10/MIP10c15-Subproposals/MIP10c15-SP4.md @@ -0,0 +1,117 @@ +## Preamble + +``` +MIP10c15-SP#: 4 +Author(s): Nik Kunkel +Contributors: +Status: Formal Submission +Date Proposed: 2020-06-14 +Date Ratified: +``` + +## Disclaimer +MIP10 is meant to handle all of the Oracle related actions. Unfortunately MIP10 has inconsistencies and doesn’t conform to the monthly governance cadence that the Maker Improvement Proposal framework is built around. This has generated a backlog of Oracle proposals. While MIP10 is refactored to conform to the regular MIP process, Oracle proposals such as this one will utilize the more liberal weekly governance cycle. While strictly speaking this makes them not subproposals, they are included in the subproposal archive as a point of provenance to serve as a paper trail. + +## Specification + +### Introduction + +If ratified, this subproposal would appoint Gitcoin as a Light Feed. Feeds submit data to the Oracles for the prices of assets. They are an important part of ensuring that the Oracles are reliable and secure. Only entities with strong credentials that the community trusts should be permitted to be an Oracle Feed. + +### Organization +- Name: Gitcoin +- Website: https://gitcoin.co +- Github: https://github.com/gitcoinco/web +- Number of Employees: 16 +- Email: Kevin@gitcoin.co +- Incorporated: A subsidiary of Consensys AG, based in Switzerland +- Domiciled: Switzerland +- When was the organization founded? Gitcoin was founded in May 2017, and folded into the Consensys Mesh in November 2017. +- Who are the major investors in your organization? Consensys AG +- How much funding has the organization raised either privately or through a token sale? About $3mm from Consensys AG +- Please provide public references for the above where possible: + +https://gitcoin.co +https://media.consensys.net/gitcoin-joins-consensys-announces-pilot-projects-f5a0955de9d6 +https://gitcoin.co/results + +### Light Feeds + +**Reputation** + +- Does the organization have a strong reputation in the crypto community? + +Yes. Gitcoin dates back to 2017 and has had a strong presensce within the ecosystem for fostering collaberation and innovation. Most notably it has created a coordination platform for sustainable funding for open source initiatives. This is critical for the Ethereum community which is based on the principles of open source and distributed work between remote entities. + +- What contributions has this organization made to the crypto ecosystem? + +Most notably it has created a coordination platform for sustainable funding for open source initiatives. This is critical for the Ethereum community which is based on the principles of open source and distributed work between remote entities. Gitcoin Grants provide a unique combination of benefits including: + empowering developers to monetize their open source contributions + enabling projects to incentivize developers to learn and hack on their platform + allowing employers to vet potential candidates through real deliverables + creating a method for crowdsourcing features and applications desired by a community + +- Would including the organization as a Light Feed instill a sense of trust in the Oracles? + +It is the opinion of the Oracle Team that Gitcoin has a trustworthy reputation in the community and would further reinforce the reputation of the Maker Oracles. + +- Are there any public accusations of misconduct? How severe and numerous are they? Have they been confirmed? + +The Oracle Team was not able to find any record of confirmed cases of misconduct on account of the organization nor its executive staff. + +**Verification** + +- Were sufficient public-facing resources provided or found that confirm the information in the application? + +Yes, public records were able to verify most of the provided information. + +- Was the applicant honest with respect to: + +- the investors + +The Oracle Team was able to verify the acquisition by Consensys in November of 2017 through press releases issued by Consensys. + +- how much funding was raised + +The Oracle Team was not able to find any public figures relating to the amount of funding raised that would confirm or deny the $3M figure quoted by the applicant. + +- the number of employees + +The Oracle Team was able to verify the majority of employees through their LinkedIn profiles which were conveniently linked to in the [Gitcoin About Us page](https://gitcoin.co/about). A small number did not cite Gitcoin nor Consensys as their employer on LinkedIn but had other publically logged connections to Gitcoin that would indicate involvement. + +- the location of incorporation & domicile + +The Oracle Team was able to verify that Consensys AG is registered and domiciled in Zug, Switzerland at address Gartenstrasse 6, 6300 Zug via [Zefix](https://www.zefix.ch/en/search/entity/list/firm/1266173). + +- Given the applicant's major investors, is there a risk adding this Light Feed would give a single investor too much influence over the Oracle protocol? + +Not at the moment, though this is something the community needs to monitor moving forward as Token Sets (formerly Set Protocol), Infura, and Gitcoin are all owned at least in part by Consensys. + +- Given the incorporation and domicile location of the organization, is there a risk adding this Light Feed would give a single jurisdiction too much influence over the Oracle protocol? + +Not currently, but similar to the above. Since Consensys is domiciled in Switzerland the exposure to Swiss regulators increases the more Consensys-subsidiary Feeds get added. + +**Identity** + +- Did the Oracle Team get in contact with the organization to confirm their application? + +Yes, the Oracle Team spoke to the founder of Gitcoin over video conference who is listed on Gitcoin's website. + +### Cost-Benefit + +- Given the ratio of Dark Feeds : Light Feeds, does the Maker Protocol benefit from adding another Dark/Light Feed at this time? + +Yes. + +- Given the extra cost of appointing a new Feed, does the benefit of the marginal security / marginal trust in the protocol exceed the cost? + +Yes. + +### Oracle Team Recommendation + +The Oracle Team recommends that Maker Governance ratify the proposal to appoint Gitcoin as a Light Feed for the Maker Oracles. +Gitcoin is an established member of the Ethereum tribe on a mission to create sustainable funding for open source. Dai is an integral part of the Gitcoin platform. Since its inception grants totalling $2,214,536 Sai/Dai have been awarded accounting for over 70% of all awarded grants. There is a clear alignement of incentives between Gitcoin providing trusted pricing data to the MakerDAO Oracles and Gitcoin's dominating use of Dai on its platform. The Oracle Team was able to verify most of the information provided by Kevin in the MIP10c14 Light Feed application. No confirmed cases of misconduct related to the organization were found. + +### Changelog + - reformatted preamble + - added disclaimer \ No newline at end of file diff --git a/MIP10/MIP10c15-Subproposals/MIP10c15-SP5.md b/MIP10/MIP10c15-Subproposals/MIP10c15-SP5.md new file mode 100644 index 000000000..0b2d7b694 --- /dev/null +++ b/MIP10/MIP10c15-Subproposals/MIP10c15-SP5.md @@ -0,0 +1,98 @@ +## Preamble +``` +MIP10c15-SP#: 5 +Author(s): Nik Kunkel +Contributors: +Type: Process Component +Status: RFC +Date Proposed: 2020-07-02 +Date Ratified: +``` + +## Specification + +### Introduction + +If ratified, this subproposal would appoint Argent as a Light Feed. Feeds submit data to the Oracles for the prices of assets. They are an important part of ensuring that the Oracles are reliable and secure. Only entities with strong credentials that the community trusts should be permitted to be an Oracle Feed. + +### Organization + +The following information was provided by Argent in their MIP10c14 application and verified by the Oracle Team to the best of its ability. + +``` +Name: Argent Labs Limited +Website: https://www.argent.xyz +Github: https://github.com/argentlabs +Email: hello@argent.xyz +Incorporated: United Kingdom +Domiciled: United Kingdom +Number of employees: 23 +When was the organization founded? 4 December 2017 +Who are the major investors in your organization? Paradigm, Index Ventures, Creandum +How much funding has the organization raised either privately or through a token sale? $16m in equity funding +Please provide public references for the above where possible. References for funding: +[Cityam](https://www.cityam.com/sequoia-crypto-fund-paradigm-makes-first-europe-investment-with-london-startup-argent/) +[Companies House](https://beta.companieshouse.gov.uk/company/11093638/filing-history) +[Crunchbase](https://www.crunchbase.com/organization/argent) +``` + +### Light Feeds +**Reputation** +- Does the organization have a strong reputation in the crypto community? + + Argent is a premiere mobile wallet with integrations spanning from the Dai Savings Rate to Compound, Aave, Uniswap, Kyber, and more. It also features a novel Guardians mechanism to restore wallet access in the case of lost keys. It has experienced immense growth in the past year through paying users gas fees, a clever growth hack. + +- What contributions has this organization made to the crypto ecosystem? + + Argent has created a feature rich mobile wallet cover the end to end spectrum of fiat onboarding all the way to DeFi dapps interactions, all packaged up in an intuitive and easy to user interface. Argent has enabled crypto to be exposed to a whole new subset of individuals across the world whose only access to the internet is through their mobile phone. Where other wallets such as TrustWallet and Coinbase Wallet have stagnated, Argent has rapidly innovated and established itself as the premiere mobile wallet in just under a year by shipping new integrations almost monthly. + +- Would including the organization as a Light Feed instill a sense of trust in the Oracles? + + Argent is a respected and trusted organization in the Ethereum ecosystem and their inclusion as a Feed would incite users to trust Maker's Oracles more. + +- Are there any public accussations of misconduct? How severe and numerous are they? Have they been confirmed? + + Oracle Team was not able to find any evidence of malicious conduct. + +**Verification** +- Were sufficient public-facing resources provided or found that confirm the information in the application? +Yes Argent provided numerous sources backed by credible organizations. + +- Was the applicant honest with respect to: + - the investors + - how much funding was raised + + The Oracle Team found over a dozen sources via a simple [Google Search](https://www.google.com/search?q=argent+series+A&oq=argent+series+A&aqs=chrome..69i57.6186j1j4&sourceid=chrome&ie=UTF-8) confirming the investors as well as the amount raised + - the number of employees + + The Oracle Team found [25 individuals on LinkedIn](https://www.linkedin.com/search/results/people/?facetCurrentCompany=%5B%2211414677%22%5D) claiming to have current or past associations with Argent. + - the location of incorporation & domicile + + The Oracle Team was able to confirm the existence of Argent Labs Limited registered in the United Kingdom at address 9th Floor 107 Cheapside, London, United Kingdom, EC2V 6DN through the [U.K. Companies House Register](https://beta.companieshouse.gov.uk/company/11093638) with Company Number 11093638 and registered on 4 December 2017 as stated in Argent's application. + + - Given the applicant's major investors, is there a risk adding this Light Feed would give a single investor too much influence over the Oracle protocol? + + The Oracle Team finds no issue with including Argent whose major investors include Paradigm, Index Ventures, and Creandum, and whose largest shareholders are Julien Gregoire Georges Niset (Cofounder & Chief Science Officer), Gerald Goldstein (Cofounder), and Itamar Lesuisse (Cofounder & CEO) are all employees of Argent Limited. + + - Given the incorporation and domicile location of the organization, is there a risk adding this Light Feed would give a single jurisdiction too much influence over the Oracle protocol? + + No. + +**Identity** +- Did the Oracle Team get in contact with the organization to confirm their application? + + Yes, the Oracle Team spoke to Itamar over video conference who is listed on LinkedIn as the CEO. This is further confirmed by the [U.K. Companies House register](https://beta.companieshouse.gov.uk/company/11093638/officers) + +### Cost-Benefit +- Given the ratio of Dark Feeds : Light Feeds, does the Maker Protocol benefit from adding another Dark/Light Feed at this time? + + Yes, the Maker Protocol currently has 15 Dark Feeds and 9 Light Feeds. Adding another Light Feed would further balance the ratio. + +- Given the extra cost of appointing a new Feed, does the benefit of the marginal security / marginal trust in the protocol exceed the cost? + +Yes, the Maker Protocol currently has 24 Feeds. Adding another Feed would marginally increase Oracle security and resiliency. + +### Oracle Team Reccomendation +- Was the applicant honest with the data they provided? + +The Oracle Team did not find any inconsistencies in the information provided by the applicant. \ No newline at end of file diff --git a/MIP10/MIP10c15-Subproposals/placeholder.md b/MIP10/MIP10c15-Subproposals/placeholder.md deleted file mode 100644 index 48cdce852..000000000 --- a/MIP10/MIP10c15-Subproposals/placeholder.md +++ /dev/null @@ -1 +0,0 @@ -placeholder diff --git a/MIP10/MIP10c9-Subproposals/MIP10c9-SP1.md b/MIP10/MIP10c9-Subproposals/MIP10c9-SP1.md new file mode 100644 index 000000000..17f806f97 --- /dev/null +++ b/MIP10/MIP10c9-Subproposals/MIP10c9-SP1.md @@ -0,0 +1,52 @@ +## Preamble + +``` +MIP10c9-SP#: 1 +Author(s): Nenad Palinkasevic, Nikola Klipa, Nikola Jankovic +Contributors: Nik Kunkel +Status: Accepted +Date Proposed: 2020-05-17 +Date Ratified: 2020-07-04 +``` + +## Disclaimer +MIP10 is meant to handle all of the Oracle related actions. Unfortunately MIP10 has inconsistencies and doesn’t conform to the monthly governance cadence that the Maker Improvement Proposal framework is built around. This has generated a backlog of Oracle proposals. While MIP10 is refactored to conform to the regular MIP process, Oracle proposals such as this one will utilize the more liberal weekly governance cycle. While strictly speaking this makes them not subproposals, they are included in the subproposal archive as a point of provenance to serve as a paper trail. + +## 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](https://blog.makerdao.com/the-first-maker-improvement-proposals-mips-ratification-vote-passes-governance-cycle-has-begun/), as described in [Maker Improvement Proposal #10: Oracle Management](https://github.com/makerdao/mips/blob/master/MIP10/mip10.md). + +[DeFi Saver](https://defisaver.com/) is a 3rd party MakerDAO management application created by [Decenter](https://www.decenter.com/). 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 + +- ETH/USD + +### Customer(s) + +DeFi Saver - nikola.jankovic@decenter.com + +### 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. + +### Changelog + - reformatted preamble + - added disclaimer diff --git a/MIP10/MIP10c9-Subproposals/MIP10c9-SP2.md b/MIP10/MIP10c9-Subproposals/MIP10c9-SP2.md new file mode 100644 index 000000000..c960f25b8 --- /dev/null +++ b/MIP10/MIP10c9-Subproposals/MIP10c9-SP2.md @@ -0,0 +1,52 @@ +## Preamble + +``` +MIP10c9-SP#: 2 +Author(s): Nenad Palinkasevic, Nikola Klipa, Nikola Jankovic +Contributors: Nik Kunkel +Status: Accepted +Date Proposed: 2020-05-17 +Date Ratified: 2020-07-4 +``` + +## Disclaimer +MIP10 is meant to handle all of the Oracle related actions. Unfortunately MIP10 has inconsistencies and doesn’t conform to the monthly governance cadence that the Maker Improvement Proposal framework is built around. This has generated a backlog of Oracle proposals. While MIP10 is refactored to conform to the regular MIP process, Oracle proposals such as this one will utilize the more liberal weekly governance cycle. While strictly speaking this makes them not subproposals, they are included in the subproposal archive as a point of provenance to serve as a paper trail. + +## 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](https://blog.makerdao.com/the-first-maker-improvement-proposals-mips-ratification-vote-passes-governance-cycle-has-begun/), as described in [Maker Improvement Proposal #10: Oracle Management](https://github.com/makerdao/mips/blob/master/MIP10/mip10.md). + +[DeFi Saver](https://defisaver.com/) is a 3rd party MakerDAO management application created by [Decenter](https://www.decenter.com/). 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 - nikola.jankovic@decenter.com + +### 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. + +### Changelog + - reformatted preamble + - added disclaimer diff --git a/MIP10/MIP10c9-Subproposals/MIP10c9-SP3.md b/MIP10/MIP10c9-Subproposals/MIP10c9-SP3.md new file mode 100644 index 000000000..d25865c15 --- /dev/null +++ b/MIP10/MIP10c9-Subproposals/MIP10c9-SP3.md @@ -0,0 +1,52 @@ +## Preamble + +``` +MIP10c9-SP#: 3 +Author(s): Nenad Palinkasevic, Nikola Klipa, Nikola Jankovic +Contributors: Nik Kunkel +Status: Accepted +Date Proposed: 2020-05-17 +Date Ratified: 2020-07-04 +``` + +## Disclaimer +MIP10 is meant to handle all of the Oracle related actions. Unfortunately MIP10 has inconsistencies and doesn’t conform to the monthly governance cadence that the Maker Improvement Proposal framework is built around. This has generated a backlog of Oracle proposals. While MIP10 is refactored to conform to the regular MIP process, Oracle proposals such as this one will utilize the more liberal weekly governance cycle. While strictly speaking this makes them not subproposals, they are included in the subproposal archive as a point of provenance to serve as a paper trail. + +## 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](https://blog.makerdao.com/the-first-maker-improvement-proposals-mips-ratification-vote-passes-governance-cycle-has-begun/), as described in [Maker Improvement Proposal #10: Oracle Management](https://github.com/makerdao/mips/blob/master/MIP10/mip10.md). + +[DeFi Saver](https://defisaver.com/) is a 3rd party MakerDAO management application created by [Decenter](https://www.decenter.com/). 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 + +- BTC/USD + +### Customer(s) + +DeFi Saver - nikola.jankovic@decenter.com + +### 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. + +### Changelog + - reformatted preamble + - added disclaimer diff --git a/MIP10/MIP10c9-Subproposals/MIP10c9-SP4.md b/MIP10/MIP10c9-Subproposals/MIP10c9-SP4.md new file mode 100644 index 000000000..6cce927e1 --- /dev/null +++ b/MIP10/MIP10c9-Subproposals/MIP10c9-SP4.md @@ -0,0 +1,52 @@ +## Preamble + +``` +MIP10c9-SP#: 4 +Author(s): Zhao Yang, Tianchi Zhu, Jie liu +Contributors: Nik Kunkel +Status: Accepted +Date Proposed: 2020-06-03 +Date Ratified: 2020-07-04 +``` + +## Disclaimer +MIP10 is meant to handle all of the Oracle related actions. Unfortunately MIP10 has inconsistencies and doesn’t conform to the monthly governance cadence that the Maker Improvement Proposal framework is built around. This has generated a backlog of Oracle proposals. While MIP10 is refactored to conform to the regular MIP process, Oracle proposals such as this one will utilize the more liberal weekly governance cycle. While strictly speaking this makes them not subproposals, they are included in the subproposal archive as a point of provenance to serve as a paper trail. + +## Specification + +### Introduction + +[MCDEX](https://mcdex.io) is a decentralized derivatives trading platform for perpetual contracts and futures. Currently, the perpetual contract is provided with fully on-chain AMM and off-chain order book. Both of the trading mode are based on margin account which is create through depositing collaterals into the contract. The PNL (profit and loss) is calculated based on the price read from oracle called mark price which is critical for keeping the whole system work. + +Therefore, instead of using mark price from a single oracle, we read price from a primary oracle source and validate it with prices from different on-chain data sources. An update causing the price gap between primary price and validating prices exceeding a threshold (5% by default) would never success. The administrator could then decide to switch to another data source or stop the perpetual to prevent further loss. + +Currently, MCDEX uses single price from Chainlink and intent to introduce Medianizer as a validator. There may be more sources in the future and a switch between them could happen at any time. + +### Oracle Name + +ETH/USD + +### Customer(s) + +MCDEX - [contact@mcdex.io](mailto:contact@mcdex.io) + +### Whitelist + +MCDEX - 0x12Ee7E3369272CeE4e9843F36331561DBF9Ae6b4 - 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? yes +- Is Oracle data written to storage? yes +- If Oracle data is stored, is it stored in a private variable? yes +- If Oracle data is stored, is the value accessible on-chain exclusively by the protocol? yes + +### Fee + +In accordance with the Responsible Oracle Migration Proposal, fees are waived for the first year and determined by MKR Governance after that. + +### Changelog + - reformatted preamble + - added disclaimer diff --git a/MIP10/MIP10c9-Subproposals/MIP10c9-SP5.md b/MIP10/MIP10c9-Subproposals/MIP10c9-SP5.md new file mode 100644 index 000000000..de0d22a97 --- /dev/null +++ b/MIP10/MIP10c9-Subproposals/MIP10c9-SP5.md @@ -0,0 +1,60 @@ +## Preamble + +``` +MIP10c9-SP#: 5 +Author(s): Brendan Chou +Contributors: +Status: Formal Submission +Date Proposed: 2020-07-21 +Date Ratified: +``` + +## Disclaimer + +MIP10 is meant to handle all of the Oracle related actions. Unfortunately MIP10 has inconsistencies and doesn’t conform to the monthly governance cadence that the Maker Improvement Proposal framework is built around. This has generated a backlog of Oracle proposals. While MIP10 is refactored to conform to the regular MIP process, Oracle proposals such as this one will utilize the more liberal weekly governance cycle. While strictly speaking this makes them not subproposals, they are included in the subproposal archive as a point of provenance to serve as a paper trail. + +## Specification + +### Introduction +The dYdX team plans to use the oracle in an ETH-USD Inverse Perpetual trading pair (https://github.com/dydxprotocol/perpetual). They are currently using the BTC-USD oracle for a BTC-USD Vanilla Perpetual (https://trade.dydx.exchange/perpetual/BTC-USDC) which has been live in production for months. + +### Oracle Name + +ETH/USD + +### Customer(s) + +dYdx - brendan@dydx.exchange + +### Whitelist + +dYdX - 0x538038E526517680735568f9C5342c6E68bbDA12 - Medianizer + +### Requirements + +For each customer address to be whitelisted: + +* Is the contract source code verified on etherscan? +Yes https://etherscan.io/address/0x538038E526517680735568f9C5342c6E68bbDA12#code + +* Is the Oracle data used in a permissioned manner that would prevent parasitic behavior? +Yes, the only contract intended to use this data is the same type of contract already using the BTC-USD data, which prevents public read-access of the data. +https://github.com/dydxprotocol/perpetual/blob/master/contracts/protocol/v1/impl/P1Getters.sol#L198 + +* 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. + +## Changelog + +* reformatted into MIP10c9 format +* answered the Requirements questions \ No newline at end of file diff --git a/MIP10/MIP10c9-Subproposals/placeholder.md b/MIP10/MIP10c9-Subproposals/placeholder.md deleted file mode 100644 index b3a425249..000000000 --- a/MIP10/MIP10c9-Subproposals/placeholder.md +++ /dev/null @@ -1 +0,0 @@ -placeholder \ No newline at end of file diff --git a/MIP12/MIP12c2-Subproposals/MIP12c2-SP1.md b/MIP12/MIP12c2-Subproposals/MIP12c2-SP1.md new file mode 100644 index 000000000..b698ec7ec --- /dev/null +++ b/MIP12/MIP12c2-Subproposals/MIP12c2-SP1.md @@ -0,0 +1,57 @@ +## Preamble + +``` +MIP12c2-SP: 1 +Title: Domain work requirements for onboarding the ZRX collateral type +Author(s): Cyrus Younessi (@DonutJr), Niklas Kunkel (@NiklasKunkel), Mariano Conti (@nanexcool) +Contributors: Charles St.Louis (@CPSTL) +Status: Obsolete +Date Proposed: 2020-06-03 +Date ratified: n/a +``` + +## Specification + +### Summary + +This proposal defines the documentation and work requirements for the onboarding of the ZRX collateral type to the Maker Protocol, explicitly highlighting the domain teams' objectives and work requirements needed to get it implemented to the Maker Protocol. + +### Proposal Details + +This subproposal contains the domain work products required for the ZRX collateral asset to be added to the Maker Protocol. More specifically, it includes the risk parameters/risk evaluation, oracle solutions, and necessarily smart contracts needed for ZRX. + +1. **Risk Domain Work:** The risk domain team's work contains a risk construct/risk evaluation for the ZRX collateral type: + 1. [[ZRX] MIP12c2-SP1 Collateral Onboarding Risk Evaluation](https://forum.makerdao.com/t/zrx-mip12c2-sp1-collateral-onboarding-risk-evaluation/2730) + +2. **Smart Contracts Domain Work:** The smart contracts domain team's work required to get ZRX added to the Maker Protocol includes an assessment of the collateral type-token contracts[,](https://etherscan.io/token/0xdd974d5c2e2928dea5f71b9825b8b646686bd200) work products for the operational collateral adapter, medianizer, oracle security module, and deploying the executive vote code (spell). More specifically, this includes: + + 1. Perform a review of the ZRX ERC20 contract to determine if they conform to the standard and can indeed be used with the existing smart contract collateral adapters. + 2. Perform the testing on the Kovan testnet, confirming that adapters and auction contracts ork well with the Maker Protocol. + 3. Create the spells to include the collaterals on our Kovan deployment. + 4. Finally, the team will deploy the smart contracts and build the executive vote spells for the Ethereum Mainnet. + +3. **Oracles Domain Work:** The oracles domain team's work required to get ZRX added to the Maker Protocol, includes making sure the oracle price feeds to support the new collateral type are prepared. More specifically, this includes: + + 1. Add support for ZRX to [setzer](https://github.com/makerdao/setzer) + 2. Add support for ZRX to [omnia](https://github.com/makerdao/oracles-v2) + 3. Deploy release candidate to the Kovan testnet for testing + 4. Coordinate Feeds to upgrade to latest release candidate + 5. Deploy Oracle smart contracts + - [Median](https://github.com/makerdao/median) + - [Oracle Security Module (OSM)](https://github.com/makerdao/osm) + 6. Update Relayers to include ZRX + +### Motivation + +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 add the ZRX collateral type to the Maker Protocol. + +### Relevant Information + +- [[ZRX] - MCD collateral application (MIP6)](https://forum.makerdao.com/t/zrx-mcd-collateral-application/2312) +- [Collateral Status Index](https://forum.makerdao.com/t/collateral-status-index/2231) + +**Relevant Definitions:** + +- **Spell:** A spell is an un-owned object that performs one action or a series of atomic actions (multiple transactions) one time only to the Maker protocol. +- **OSM:** ensures that new price values propagated from the Oracles are not taken up by the system until a specified delay has passed ([OSM Documentation](https://docs.makerdao.com/smart-contract-modules/oracle-module/oracle-security-module-osm-detailed-documentation)). +- **Median:** provides Maker's trusted reference price. In short, it works by taking the median of a set of price updates posted by governance appointed Feeds. ([Median Documentation)](https://docs.makerdao.com/smart-contract-modules/oracle-module/median-detailed-documentation). diff --git a/MIP12/MIP12c2-Subproposals/MIP12c2-SP2.md b/MIP12/MIP12c2-Subproposals/MIP12c2-SP2.md new file mode 100644 index 000000000..e1e5782c3 --- /dev/null +++ b/MIP12/MIP12c2-Subproposals/MIP12c2-SP2.md @@ -0,0 +1,59 @@ +## Preamble + +``` +MIP12c2-SP: 2 +Title: Domain work requirements for onboarding the KNC collateral type +Author(s): Cyrus Younessi (@DonutJr), Niklas Kunkel (@NiklasKunkel), Mariano Conti (@nanexcool) +Contributors: Charles St.Louis (@CPSTL) +Status: Obsolete +Date Proposed: 2020-06-03 +Date ratified: n/a +``` + +--- + +## Specification + +### Summary + +This proposal defines the documentation and work requirements for the onboarding of the [KNC collateral type](https://etherscan.io/token/0xdd974d5c2e2928dea5f71b9825b8b646686bd200) to the Maker Protocol, explicitly highlighting the domain teams' objectives and work requirements needed to get it implemented to the Maker Protocol. + +### Proposal Details + +This subproposal contains the domain work products required for the KNC collateral asset to be added to the Maker Protocol. More specifically, it includes the risk parameters/risk evaluation, oracle solutions, and necessarily smart contracts needed for KNC. + +1. **Risk Domain Work:** The risk domain team's work contains the following risk construct/risk evaluation for the KNC collateral type: + 1. [[KNC] MIP12c2-SP2 Collateral Onboarding Risk Evaluation](https://forum.makerdao.com/t/knc-mip12c2-sp2-collateral-onboarding-risk-evaluation/2732) + +2. **Smart Contracts Domain Work:** The smart contracts domain team's work required to get KNC added to the Maker Protocol includes an assessment of the collateral type-token contracts[,](https://etherscan.io/token/0xdd974d5c2e2928dea5f71b9825b8b646686bd200) work products for the operational collateral adapter, medianizer, oracle security module, and deploying the executive vote code (spell). More specifically: + + 1. Perform a review of the KNC ERC20 contract to determine if they conform to the standard and can indeed be used with the existing smart contract collateral adapters. + 2. Perform the testing on the Kovan testnet, confirming that adapters and auction contracts ork well with the Maker Protocol. + 3. Create the spells to include the collaterals on our Kovan deployment. + 4. Finally, the team will deploy the smart contracts and build the executive vote spells for the Ethereum Mainnet. + +3. **Oracles Domain Work:** The oracles domain team's work required to get KNC added to the Maker Protocol, includes making sure the oracle price feeds to support the new collateral type are prepared. More specifically, this includes: + + 1. Add support for KNC to [setzer](https://github.com/makerdao/setzer) + 2. Add support for KNC to [omnia](https://github.com/makerdao/oracles-v2) + 3. Deploy release candidate to the Kovan testnet for testing + 4. Coordinate Feeds to upgrade to latest release candidate + 5. Deploy Oracle smart contracts + - [Median](https://github.com/makerdao/median) + - [Oracle Security Module (OSM)](https://github.com/makerdao/osm) + 6. Update Relayers to include KNC + +### Motivation + +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 add the KNC collateral type to the Maker Protocol. + +### Relevant Information + +- [MIP6 MCD Application: Kyber Network [KNC]](https://forum.makerdao.com/t/knc-mip6-mcd-application-kyber-network-knc/2458) +- [Collateral Status Index](https://forum.makerdao.com/t/collateral-status-index/2231) + +**Relevant Definitions:** + +- **Spell:** A spell is an un-owned object that performs one action or a series of atomic actions (multiple transactions) one time only to the Maker protocol. +- **OSM:** ensures that new price values propagated from the Oracles are not taken up by the system until a specified delay has passed ([OSM Documentation](https://docs.makerdao.com/smart-contract-modules/oracle-module/oracle-security-module-osm-detailed-documentation)). +- **Median:** provides Maker's trusted reference price. In short, it works by taking the median of a set of price updates posted by governance appointed Feeds. ([Median Documentation)](https://docs.makerdao.com/smart-contract-modules/oracle-module/median-detailed-documentation). diff --git a/MIP12/MIP12c2-Subproposals/placeholder.md b/MIP12/MIP12c2-Subproposals/placeholder.md deleted file mode 100644 index b3a425249..000000000 --- a/MIP12/MIP12c2-Subproposals/placeholder.md +++ /dev/null @@ -1 +0,0 @@ -placeholder \ No newline at end of file