# MIP41c4-SP20: Facilitator Onboarding, Starknet Engineering Core Unit

## Preamble

```
MIP41c4-SP#: 20
Author(s): @badgerofthe9d, Ohad Barta
Contributors: Derek Flossman, Maciek Kaminsky, Kris Kaczor, Marc-Andre Dumas, Ohad Barta, @badgerofthe9d
Tags: core-unit, cu-sne-001, facilitator, active
Status: Accepted
Date Proposed: 2021-08-09
Date Ratified: 2021-09-27  
Ratification Poll URL: https://vote.makerdao.com/polling/QmesWgnC?network=mainnet
Forum URL: https://forum.makerdao.com/t/mip41c4-sp20-facilitator-onboarding-for-starknet-engineering-core-unit-sne-001/9782
```

## Sentence Summary
MIP41c4-SP20 onboard @badgerofthe9d as facilitator for the Starknet Engineering Core Unit (SNE-001)

## Specification

### Motivation

I have a genuine interest and respect for the Maker protocol and DeFi in general. The decentralization of the financial system is a topic I have been passionate about since 2009. In 2011 I wrote two master's theses on the subprimes crisis and the lack of transparency in transactions and packaging of structured debt products. Ten years later, Maker protocol developed and showed incredible traction on a fundamental building block to solve some of those issues and allow a more open, transparent, and fair financial system.

I am (strangely) passionate about risk management and debt products. I started my career doing valuation of high yield debt portfolios in traditional finance, then built debt models for project finance, then built a risk management company for crypto assets, then built a lending product with a crypto custodian.

Maker protocol on layer 2, and specifically on Starknet, has a huge potential to help Maker scale through lower gas fees and faster minting/transactions. I also believe there is a massive opportunity to improve the user experience (liquidation, trading timelines, collateral ratio) with Starknet.

I am both grateful and motivated to be working with a team of Engineers familiar with both Maker and zk proofs to make it happen.

### Core Unit ID

SNE-001  

### Facilitator name and information

- Name: @badgerofthe9d
- Forum: @badgerofthe9d
- LinkedIn: NA
- ETH Address: TBD

### Facilitator Commitment

In addition to facilitating the Ways of Working, Team Rituals and the Core Unit Mandates as outlined in the [Starknet Engineering Core Unit MIP](https://forum.makerdao.com/t/mip39c2-spxx-adding-the-starknet-engineering-core-unit-secu/9745), the following describes my commitment and actions as the Protocol Engineering Core Unit Facilitator, to;

* Serve as a point of contact between the Starknet Engineering Core Unit, the Governance community and other facilitators to ensure a cohesive understanding of team deliverables and progress.
  * Represent the team in weekly community calls
  * Work with the community and act as a triage point to collate new community requests and share awareness with the team
  * Continue to be active on the Maker Forum and Rocket Chat as an easily reachable point of contact
* Help define and own the framework to define the exact scope of the Maker protocol that will be ported over Starknet, looking specifically at the dimensions below. My role is to assure the right people are having the right discussions to make this happen.
  * Necessary functions to be ported over
  * Methods to compute necessary system-level and asset-level risk metrics
  * Impact on risk governance, DAI peg, collateral management, collateral, surplus auctions, and emergency shutdown
  * Sequencing of the development
* Propose quantitative analyses to investigate vectors of improvements of the protocol once it will be on Starknet, specifically around liquidation process and oracles. Analyses will be presented to the community for discussion and will be focused on improving the user experience.

* Remove the administrative workload for the Protocol Engineering Core Unit to enable them to focus on the tasks they have committed to deliver.
  * Facilitate goal planning sessions, external team integrations & meetings, help with technical smart contract/module/documentation tasks
  * Communicate expectations for all ongoing tasks in/outside of the team
  * Maintain the team budget, accounting and overhead management
* Maintain planning documentation detailing accomplishments, current work, planned work and upcoming targets to ensure line of sight, clarity, transparency and broad project awareness.
  * Document quarterly objectives and key results to help steer planning and prioritization
  * Maintain an active team backlog of tasks detailing team progress
  * Maintain a community facing backlog representing workstreams
* Scale the team to deliver on the mandated objectives in alignment with the budget proposal.
  * Build specializations within the team to facilitate targetted focus and increase deliverables
  * Work with the team to streamline the interview and onboarding process

### Facilitator Credentials

* **Oracle and reference price logic:** Led the Research team at Merkle Data to build a reference price (out of 30 exchanges trade data) with a certainty index and a manipulation index. The reference price was calibrated to be stable during flash crashes and stress-tests. Consulted for an Oracle project on their filtering logic to define what the reference price is to distribute rewards.

* **Risk analytics:** Former CEO of Merkle Data, sold to Anchorage. Led a research and product team to build a risk and surveillance solution for managing intraday and daily risk. Built stress-test scenarios for spot and options portfolios.

* **Crypto product design** (flow of funds and information): Former head of payments at Anchorage. PM crypto-native credit card network built for Visa. Integrated Merkle Risk product to build the lending and margin product.

* **Smart contract trade execution:** Consulted for a Defi company to build an execution service across Defi protocols to abstract away from each smart contract's price update logic. 

* **Product Management and Technical project facilitation**: PM on dozen of projects in and outside of the crypto space.