MIP40c3-SP#: 28 Author(s): Author(s): Louis Baudoin (@louismerkle), Ohad Barta Contributors: Derek Flossman, Maciek Kaminsky, Kris Kaczor, Marc-Andre Dumas, Ohad Barta, Louis Baudoin Tags: core-unit, cu-sne-001, budget, dai-budget Status: Formal Submission Date Applied: 2021-08-09 Date Ratified: N/A
MIP40c3-SP28 adds the budget for StarkNet Engineering Core Unit.
I am proposing this budget for the StarkNet Engineering Core Unit to be able to succeed in its mandate, specifically; to build a bridge to StarkNet that is upgradeable through governance. This is referred to as phase I in the main proposal (MIP39c2-SP28).
StarkNet Engineering Core Unit
This budget for phase I secures a team of 2 Senior Engineers, one Data Scientist (part-time), and one Facilitator. The team size is expected to increase in phase II once the roadmap for enabling minting on StarkNet is clearer and syndicated with the community.
- Duration: 3 months
- Total amount for Maker foundation: $210,375
- Headcount: 4 (including one part-time)
The budget asked is $210,375 for six months, which represents 50% of the total budget. The distribution of the budget across profiles is shown below. The salaries used are taken from Maker internal salary grids and guidelines.
The payment of all the non-salary items will be done upon starting the project. The payment of the salaries will be done either bi-weekly or monthly. The budget will be split evenly between the Maker and Starkware.
Salaries: The has 2 full-time Senior Engineers with prior knowledge of Solidity, validity proofs, or both. 1 part-time Data Scientist, and 1 full-time Team Facilitator (for a total of 4 members).
Bug bounty: Bug Bounties allow us to support whitehat involvement in the work we do. Payout amounts will be assessed and determined by the team.
Gas cost: Rough estimate, based on gas cost needed by other Core Units, taking into account the scope of phase I.
Audit: We will work with one of the firms Maker has worked with before (Gauntlet, PwC, Certora, Quantstamp, Trail of Bits, Consensus, OpenZepplin and Peckshield).
No MKR vesting is proposed for phase I. A MKR vesting based on deliverables will be proposed for phase II.
Travel: Our team is remote, yet we are not excluding the option to meet in person if we assess it is needed.