# MIP#40

```
MIP#:40
Title: Builder Program
Author(s): Committee, Admin & MVClabs
Contributors:
Editor: N/P
Date Proposed: 2024.06.06
Date Ratified: 
Dependencies: MIP-1
Replaces: N/P
Exception to MIP: N/P
```

* <mark style="color:red;">**Vote Option:**</mark>
* Yes
* No

<mark style="color:red;">**Executive Summary:**</mark> &#x20;

MVC is on a mission to redefine the future of bitcoin and we're inviting YOU to be a cornerstone of this journey.

We're super excited to announce the formation of the \*\***Builder Program\*\***! This is your chance to be part of the revolution, to transform Bitcoin from being just digital gold to a multifunctional network that supports a multitude of web3 decentralized applications. 🎉🎉🎉

We're not just talking about change, we're making it happen! MVC is an irreversible process in the Bitcoin ecosystem, and as a DAO, building is truly decentralized. But to keep this ship sailing smoothly, we need developer all over the world to our vision.

Together, let's unlock Bitcoin's full potential and pave the way for a decentralized future brimming with possibilities.

**Content:**

<mark style="color:red;">**Theme & Slogan:**</mark>

"Ensuring Web3 happens in MVC & Bitcoin."

<mark style="color:red;">**What is the Reward Pool?**</mark>&#x20;

A funding pool of up to 250,000 SPACE is available per quarter.

<mark style="color:red;">**What Kind of Projects Do We Fund? (Funding Scope)**</mark>&#x20;

MVCDAO support a diverse range of projects. This includes, but is not limited to, BTCfi, dApps, GameFi, decentralized services, infrastructure improvements, and meta-contract synchronization.

<mark style="color:red;">**I have an Idea, how do I apply? (Application Process)**</mark>

Have an idea? Fill out the [form](https://forms.gle/7GMhUG9EQuCSwz6HA)[ ](https://forms.gle/bjjWMqgdAwRZdnSd8)with project details. Builder Program Judge Group or committee will mak review submissions and provide feedback by the following [form](https://docs.google.com/forms/d/e/1FAIpQLSdRxrUSIBP2sOqn-FM1FBaXqmXxOPblL0OwnSBo_zir9fKf3g/viewform?usp=pp_url).&#x20;

Feedback or interview may be requested by committee or Technical Judge Group members.&#x20;

<mark style="color:yellow;">**Application Instructions**</mark>

[https://docs.google.com/presentation/d/1sSts6cvLgjEt2z85EW871K8v8pPdXaj8c6YwRcqdcCs/edit?usp=sharing](https://docs.google.com/presentation/d/1sSts6cvLgjEt2z85EW871K8v8pPdXaj8c6YwRcqdcCs/edit?usp=sharing)

<mark style="color:red;">**Rules & Eligibility:**</mark>

Welcome, innovative minds and diligent builders! To ensure a smooth sail in the vast ocean of MVCDAO's builder program, please anchor down these golden rules:

<mark style="color:red;">**Major Criteria:**</mark>

1. **Completed Functionalities:**

Completed Functionalities: Rewards under the Proof of Building (PoB) program are allocated exclusively for functionalities that have been fully completed and implemented.

Funding for Planning Phase: Applications in the project planning phase is not eligible for funding under builder program.

2. **Completeness review:**

Every functionality you deliver will go under the review by our esteemed committee members or a specially appointed technical judge group. Beware incomplete tasks, or any performance hiccups will push your project out of the current quarter's PoB bounty. But don't fret! Fix those issues, pass the completeness test, and you're back in the game for the next round.

3. **Open-Sourcing Requirements:**

Projects that handle asset security, including but not limited to asset bridges, indexers, smart contract protocols, and implementations, must be fully open-sourced. Projects failing to adhere to open-source mandates will be ineligible for PoB rewards to mitigate the risk of user fund losses due to security vulnerabilities. Non-compliant projects must seek approval through the MIP process.

1. <mark style="color:red;">**The categroies dis-qualify for application:**</mark>

\-- NFT album series.

\-- Front-end and back-end application unrelated to MVC.

\-- Projects that plagiarize or infringe on other project codes.

\-- Applications solely focused on token issurance without pratical utility.

\-- Applications that infringe on user privacy or violate laws in most jurisdictions.

\-- Wallet: Given MVC's adequate support for wallet applications, further development of wallet applications exclusive to MVC is deemed non-essential. To emphasize user safety, wallet applications are excluded from the builder program to minimize potential risks to users and to prevent undue criticism of MVC DAO for insufficient review.

Proposals for wallet integration or enhancements should be directed to the DAO via general MIP on-chain proposal, prioritizing user safety and integration with well-known existing hot and cold wallets in the industry.

<mark style="color:red;">**General Rules:**</mark>

1. Participants are responsible for all taxes.
2. All rewards and grants are subject to applicable law.
3. Participants must not violate any laws or compromise unauthorized data.
4. Participation in the program is at the participant's own risk and cost.
5. Participants must sign a contract with their name and physical address before receiving rewards or grants.
6. Additional KYC procedures may be required at MVCDAO's discretion. Non-compliance will lead to forfeiture.
7. Participants must update MVCDAO of any contact information changes to maintain eligibility for rewards or grants.
8. Grant distribution takes place from the 16th to the 21st of each month.
9. Excessive inquiries \[equal or exceeding twice] regarding the grant distribution date before the 21st may lead to a 120-hour mute.
10. Dissemination of false information in public is prohibited; MVCDAO reserves the right to disclose applicant information for public verification if participants spread false information.
11. MVCDAO is not liable for losses due to incorrect recipient addresses.
12. MVCDAO reserves the right to modify or terminate the Program without notice.
13. Operational expenses for dapps should not be funded by rewards; the treasury is solely for MVC purposes. Each ecosystem operates independently for competitiveness and growth.

<mark style="color:red;">**Eligibility Criteria: Applicants ineligible for rewards or grants:**</mark>

1. Individuals below the legal age of majority in their country.
2. Individuals on sanctions lists or residing in countries with crypto bans list.

***

## Technical Judge Group

#### Objective <a href="#objective" id="objective"></a>

The mission of the Technical Judge group is to maximize the number of developers building on MVC.

**Initial technical judge group member**

The builder program will be assessed by technical judge group initially from MVClabs member from early contributor group + one Technical Committee members initially.

**Avoid conflict of interest:**

Judge group member should not have pose judgement on their own development project to avoid conflict of interest.

**Technical judge member Internal voting**

An internal vote limited to Technical Judge Group.

The collective vote of initial technical judge members will be communicated to the committee for evaluation.

If over 57% of the internal votes (Technical Judge member) support the project with it's costs weigh, it will be moved to the Committee member for further review, if there is less than 3 out of 7 objection within 48 hours, we will upload the project for DAO on-chain approval for seven days.

**Technical Judge member Role**

The following summarizes the basic budget and parameters of the Technical Judge group

* **Budget**: Justify the costs proposed by project applicant.
* **Grant Size**: \<Depends
* **Support**: Successful grants require 57% Technical Judge Group Members to adopt a proposal.

\------------------

#### General Guideline: <a href="#rubric-for-proposals" id="rubric-for-proposals"></a>

The Rubric for grading proposals may be based on the criteria in the table below.

| Reach Components                             | 0                                                     | 1                                                            | 2                                                                                  | 3                                                                                                 |                                                                                                        |
| -------------------------------------------- | ----------------------------------------------------- | ------------------------------------------------------------ | ---------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------ |
|                                              |                                                       |                                                              |                                                                                    |                                                                                                   |                                                                                                        |
| Developer Presence                           | Team has no developers                                | Team has a few developers                                    | Team has many developers                                                           | N/A                                                                                               |                                                                                                        |
| Developer Draw                               | Project unlikely to draw more developers to MVC       | Project likely to draw more developers to MVC                | Project likely to draw many developers to MVC                                      | Project likely to draw a large number of developers or a new desirable class of developers to MVC |                                                                                                        |
|                                              |                                                       |                                                              |                                                                                    |                                                                                                   |                                                                                                        |
| Merits                                       | 0                                                     | 1                                                            | 2                                                                                  | 3                                                                                                 | 4                                                                                                      |
|                                              |                                                       |                                                              |                                                                                    |                                                                                                   |                                                                                                        |
| Developer Commitment                         | No commitment attraction                              | Mercenary commitment attraction (stays until benefits end)   | Commitment attraction (1 to 3 months after rewards end )                           | Commitment attraction (1 year after rewards end)                                                  | Commitment attraction (2+ years after rewards end)                                                     |
| Likelihood of success                        | Clear flaw in design that cannot be easily remedied   | Difficult to see the project continuing for more than a year | Reasonable chance that the project has intermediate-to-long-term success (+1 Year) | Project is likely to generate long-term, sustainable value for the Optimism ecosystem             | Project has substantial likelihood to generate long-term, sustainable value for the Optimism ecosystem |
| Grant size                                   | Grant size significantly outweighs projected benefit  | Grant size is considerably larger than expected benefit      | Grant size is proportional to expected benefit                                     | Expected benefit outweighs grant size                                                             | Expected benefit meaningfully exceeds grant size                                                       |
| Team assessment                              | Team does not substantiate ability to deliver on plan | Team does not show significant ability to deliver on plan    | Team shows reasonable ability to deliver on plan                                   | Team shows significant ability to deliver on plan                                                 | Team exceeds what is required to deliver on plan                                                       |
|                                              |                                                       |                                                              |                                                                                    |                                                                                                   |                                                                                                        |
| Milestones                                   | 0                                                     | 1                                                            | 2                                                                                  |                                                                                                   |                                                                                                        |
|                                              |                                                       |                                                              |                                                                                    |                                                                                                   |                                                                                                        |
| Milestone Trackability                       | Not trackable                                         | Somewhat trackable                                           | Easily trackable                                                                   |                                                                                                   |                                                                                                        |
| Milestone Orientation                        | Not oriented toward brining more devs to MVC          | Oriented towards brining more devs to MVC                    | Oriented toward more devs and toward making project composable with MVC ecosystem  |                                                                                                   |                                                                                                        |
|                                              |                                                       |                                                              |                                                                                    |                                                                                                   |                                                                                                        |
| Other                                        | 0                                                     | 1                                                            | 2                                                                                  |                                                                                                   |                                                                                                        |
|                                              |                                                       |                                                              |                                                                                    |                                                                                                   |                                                                                                        |
| Demo included (binary yes/no)                | No demo included                                      | Demo included                                                | High quality demo included                                                         |                                                                                                   |                                                                                                        |
|                                              |                                                       |                                                              |                                                                                    |                                                                                                   |                                                                                                        |
|                                              | -2                                                    | -1                                                           | 0                                                                                  | 1                                                                                                 | 2                                                                                                      |
| Discretionary Factors (comment required)\*\* |                                                       |                                                              |                                                                                    |                                                                                                   |                                                                                                        |

\*\*Reviewers will have a discretionary score to apply to the overall rubric of (-2 to 2). An explanation may be included with the assignment of any discretionary score.

Grants from the treasury given directly to builders, projects and protocols are required by the MVCDAO to be vested in three months. There are two reasons:

1. This creates **long-term incentive alignment** with MVC. The Collective will be most successful with a community of builders and users who care about the MVCs vision and are on board with the work required to get there. Locking grants helps prevent grantees from treating the treasury as a short-term fix and aborting.
2. Space is not intended to fully fund for the cost of running a business after launch. Locking token grants helps communicate to interested parties that the primary purpose of Space is for incentive alignment, not for cash.

**Note:**

Adjustments of the emission schedule can be initiated by any committee member, with a minimum of 57% votes in favor \[At least 3 consent], or through an on-chain DAO proposal with consent \[60%]. This process enables MVCDAO to remain agile and responsive to its operational and strategic needs in the evolving environment.

\-------------------------------

* <mark style="color:red;">**Disclaimer & Remarks:**</mark>

**1) Disclaimer on Investment Intentions**

Due to regulatory compliance and legal purposes, in the Official MVC Channel and general real life conversation, Space cannot be acknowledged or discussed as an investment vehicle. Please respect the official channel policies and adhere to them, as they are mandatory for all members. Thank you for your understanding.

Decisions to acquire or use Space for speculative or investment purposes are solely at the discretion of the individual. MVCDAO explicitly disclaims any responsibility for losses that may arise from such actions. Members are urged to exercise caution and make informed decisions.

**2) No Assurance on Space Value**

Please note that MVCDAO does not make any commitments or guarantees regarding the value of the network gas: SPACE.

**3) No Investment Advise:**

This proposal is focused on enhancing the visibility and sustainability of the MVC network. It is important to note that the arranagement mentioned in this proposal do not constitute investment advice. Participants and all members should refrain from interpreting it as such.

**4) Conflict of interest declaration:**

The author of this proposal has not received any commission.

**5) Limitations of the Finance Department:**&#x20;

The finance department can't simply wave its magic wand and make every other department and builder program efficient, effective, and free from fraud.

**5A) Fraud: Not Guaranteed by the Finance Department:**&#x20;

It is not within the purview of the Finance Department to ensure the operational smoothness of other departments or to prevent third-party fraud. Various departments should conduct thorough due diligence to mitigate the risk of external fraud.&#x20;

**5B) Builder Program: Not Guaranteed by the Finance Department:**&#x20;

The subsequent operation of applications coming from the builder program is not monitored or endorsed by MVCDAO and the finance department. All members should exercise caution for any engagement with applications coming from the builder program in the future.

**6) MVC operates autonomously, independent of all ecosystems.**

**6A) Ecosystem Inquiry and Communication:**

While MVCDAO itself doesn't manage ecosystem communication and operates independently from all ecosystem, we're more than willing to facilitate connections and provide the necessary contact information to ensure community members can reach out to the right ecosystem representatives or channels for communication and inquiries.&#x20;

Just as the Ethereum Foundation operates separately from the ecosystem, we encourage inquiries to be directed to the specific ecosystem representatives for the most accurate and helpful responses, rather than directing inquiries directly to the Ethereum Foundation, or in our case, MVCDAO.

**6B) Ecosystem Competitiveness:**&#x20;

We're thrilled to witness the rapid evolution and diversification of the MVC ecosystem, particularly following the launch of the builder program. However, it's important to clarify that the MVC DAO budget is dedicated solely to MVC and does not extend to supporting the operational or competitive aspects of ecosystem projects, except for node operation.

Ecosystem projects are responsible for their own competitiveness and operational costs post-launch. While we celebrate the achievements and exciting news of ecosystem partners, MVC DAO do not ensure their market competitiveness.

**6C) Ecosystem Safety:**&#x20;

The safety of any ecosystem cannot be guaranteed by MVCDAO. We are not responsible for any losses incurred due to hacker attacks or interactions with ecosystem projects or partners.&#x20;

Members are advised to proceed with caution when engaging with any ecosystem or partner projects.

**6D) Supporting the Ecosystem:**&#x20;

We want to express our appreciation for the members' valuable support in boosting the exposure of the ecosystem. Your efforts are deeply appreciated.

However, MVC maintains neutrality and does not officially endorse any specific ecosystem entities, including early contributors, MVClabs, or participants in the builder program.

Should any member engage in activities such as organizing AMAs with ecosystem developers or offering assistance to any part of the ecosystem, we encourage the member to reach out directly to the involved ecosystem representative and their relevant channels for discussions regarding their policy on potential rewards.

To ensure clarity and prevent any future misunderstandings, we recommend establishing an agreement with the respective ecosystem if rewards are anticipated for support. Otherwise, it may be beneficial to consider such contributions as voluntary.
