> For the complete documentation index, see [llms.txt](https://docs.metapool.app/master/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.metapool.app/master/faq-frequently-asked-questions/faq-mpdao-and-governance/faq-initiatives.md).

# FAQ Initiatives

<details>

<summary>What Kind of Initiatives the community representatives should present?</summary>

Is expected that initiatives proposed to achieve Meta Pool vision and mission.

In this sense, initiatives can include: community activations, education programs, participation in events, and enhancing Meta Pool’s functionalities.&#x20;

</details>

<details>

<summary>How will the DAO track the initiatives?</summary>

A platform will be launched on metapool.app to present and manage initiatives in the Vote section.

</details>

<details>

<summary>Where can I see all the initiatives?</summary>

Visit metapool.app, and go to Vote -> Initiatives.

</details>

<details>

<summary>Is it better to present an initiative with a virtual or IRL activity?</summary>

You can choose which is better!&#x20;

Just remember, virtual events happen all the time, an IRL activity, such as a staking party can be a good idea..

</details>

<details>

<summary>How can I vote for an initiative?</summary>

You can vote using the voting power achieved by locking mpDAO tokens.

</details>

<details>

<summary>How much funding will receive an initiative?</summary>

The amount will vary depending on the amount of votes received and the amount of money available for the round.

</details>

<details>

<summary>Who can present an initiative?</summary>

Any community representative interested in doing so.

</details>

<details>

<summary>Is there any minimum amount of votes?</summary>

The voting process will be valid only if the total voting power is higher than the amount of participants times 100,000

</details>

<details>

<summary>How many initiatives can I present?</summary>

There is no limited number of initiatives that can be presented on every round.

We suggest that you put all the effort on the initiatives proposed, thinking a single well elaborated initiative can have better impact.

</details>

<details>

<summary>What information do I need to present for an Initiative?</summary>

The following is the information required for a initiative to be proposed:

* Title
* One liner description
* Description
* Goal
* Budget (USD)
* How will you achieve the selected goal?
* Execution Date
* Link to Document

</details>

<details>

<summary>What will happen if an accepted initiative is not done?</summary>

The core team will look for an explanation about what is happening with the initiative and find conciliation mechanisms to execute the initiative.

</details>

<details>

<summary>What will happen if the rewards received are not enough to finish the initiative?</summary>

An initiative will have 2 chances in a row to obtain enough fundings for its execution. The funding approved from the first voting will be saved for the next round.&#x20;

In case it doesn’t reach an enough number of votes, the funding approved will be lost and returned to its treasury for new initiatives.

</details>

<details>

<summary>How long the execution of an initiative could last?</summary>

The execution time is expected to last 4 weeks maximum.

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.metapool.app/master/faq-frequently-asked-questions/faq-mpdao-and-governance/faq-initiatives.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.