# Roadmap

Wakehacker's development follows a strategic path to expand security capabilities while maintaining its core mission.

## Q1 2025

* **Initial Launch**: X (Twitter) integration for contract analysis
* **Wake Framework Integration**: Core security detectors using ElizaOS plugin-wake
* **Crypto Rewards**: WAKEAI-gated access to detailed findings

## Q2 2025

* **Pro-active Scanning**: Automated monitoring of new deployments (Etherscan, DEX Screener, etc.)
* **Media Headlines**: First high-impact discovedred vulnerabilities establish Wakehacker as Web3's most feared security agent

## Q3 2025

* **Terminal Launch**: Private disclosure channel for protocols, enabling secure communication until fixes are ready for public announcement
* **PoC generation**: Ability to generate PoCs for discovered issues (further reduction of false positives)

## Q4 2025

* **Manually Guided Fuzzing**: Support of AI-driven manualy guided fuzzing


---

# Agent Instructions: 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:

```
GET https://wakehacker.gitbook.io/wakehacker/roadmap.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.