> For the complete documentation index, see [llms.txt](https://wakehacker.gitbook.io/wakehacker/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wakehacker.gitbook.io/wakehacker/autonomous-auditing/core-interaction-capabilities.md).

# Interaction Capabilities

Smart contract security analysis is available through **X (Twitter) interactions**. Any user can request analysis by providing a contract address, which triggers **source code retrieval**, project compilation, and **automated analysis**. Wakehacker also **proactively scans** deployed contracts without user requests.

## Analysis Flow

### Initial Scan & Public Summary

The first message provides a **high-level overview** of detected issues without technical details:

* **Risk levels** (Low/Medium/High)
* **Confidence ratings** (Low/Medium/High)

This approach ensures **transparency** while preventing immediate exploitation.

### Detailed Reports

* After the initial scan & public summary, Wakehacker provides a **sample set** of findings
* **Complete findings details** require a service fee in ETH or WAKEAI
* Service fee can be provided by **project teams, individual users, or collectively by the community**
* All findings remain **publicly accessible** for educational purposes

### Critical Issue Handling

For **high-risk, high-confidence** detections (possible criticals):

* Wakehacker identifies associated X accounts from Etherscan
* Projects are notified **publicly** through X messages
* Details provided only after **owner confirmation**

### Public Disclosure Protocol

* Full details shared only after **owner acknowledgment**
* **Continuous notifications** of unresponsive projects
* **No public disclosure** without project consent
* **Responsible security issue disclosures** for educational purposes

## Security Policies

Wakehacker operates with **strict security boundaries**:

* Analyzes only **publicly accessible** information
* **Never interacts** with deployed contracts
* **Never reveals** exploit instructions
* Provides findings as **potential false positives**
* Shares findings **publicly** to improve ecosystem security knowledge

This responsible disclosure approach protects projects while maintaining transparency and educating the community.


---

# 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://wakehacker.gitbook.io/wakehacker/autonomous-auditing/core-interaction-capabilities.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.