> For the complete documentation index, see [llms.txt](https://docs.projectcatalyst.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.projectcatalyst.io/previous-funds/fund11-docs/project-onboarding/funded-proposers-fp/key-dates.md). # Key dates * 14 Feb 2024 EOD utc - Deadline for Proof of Life Verifiers onboarding form * 15 Feb 2024 - F11 Results Announced * 15 Feb 2024 - Intro email to Funded Projects (FP) * 19 Feb 2024 - Deadline FP onboarding form * 20 Feb 2024 - FP Onboarding Celebration / Funded Projects Town Hall (9 AM/4 PM UTC time slots) * 20 Feb 2024 - 1 Mar 2024 - Meetings to provide Proof of Life (PoL) * 20 Feb 2024 - 1 Mar 2024 - Test Tx confirmation * By 19 Feb 2024 EOD UTC - FP to check if the number of milestones is correct in the Milestone Module * 16 Feb 2024\* - 23 Feb 2024 - Statement of Milestones formulation * 3 Mar 2024 EOD UTC - End of Onboarding (Statement of Milestone approval inc. approvals) \*The FP user account in the Milestone Module allowing FPs to submit their SoM is created once the FP has completed and submitted their onboarding form. --- # 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.projectcatalyst.io/previous-funds/fund11-docs/project-onboarding/funded-proposers-fp/key-dates.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.