> 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/tokenomics-and-governance/mpdao-governance/mpdao-grants/voting-timeline.md). # Voting Timeline The voting process follows a structured schedule for the upcoming voting round. Here’s how it works: * Open Call for Proposals: The submission period for proposals opens on March 2, 2025, and closes on April 11, 2025. During this time, community members are invited to submit their proposals for review. Submit your proposal here: * Proposal Review and Approval: Meta Pool’s core team will review all submitted proposals. This review process will take place from April 13, 2025, to April 20, 2025. The team will provide feedback and ensure the proposals align with the community’s goals. * Voting Period: The official voting period will run from April 21, 2025, to April 25, 2025. During this time, community members can vote for the proposals they believe will best support mpDAO’s growth and development. The dates are subject to change. --- # 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/tokenomics-and-governance/mpdao-governance/mpdao-grants/voting-timeline.md?ask=&goal= ``` `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.