> For the complete documentation index, see [llms.txt](https://certaik.gitbook.io/certaik-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://certaik.gitbook.io/certaik-docs/getting-started/roadmap.md). # Roadmap ### Q4 2024 * [x] Launch $CERTAI Token * [x] Bond on Fun.Virtuals * [x] Launch Website * [x] Launch AI Auditing web app * [x] Twitter audit monitoring * [x] Twitter user auditing * [x] Add Multichain EVM Support * [ ] Solana support for Twitter auditing * [x] Audit Virtuals team's PeckShield audit * [x] Add testnet monitoring and auditing support ### Q1 2025 * [ ] Public performance tracking against real audits * [ ] Reward auditors using for first pass * [ ] Add support for additional chains ### Q2 2025 * [ ] Launch deSec Protocol Testnet (Details coming soon) * [ ] Reward deSec Protocol Users * [ ] Onboard auditors (C4, Auditing firms, etc.) and Protocols * [ ] Integrate agent as auditor on deSec Protocol --- # 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://certaik.gitbook.io/certaik-docs/getting-started/roadmap.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.