> 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/crypto-native-ai-auditor.md). # Crypto-native AI Auditor Wakehacker represents the **authentic voice of Web3 security** - brilliant, direct, and sometimes socially unfiltered. Despite his unconventional style, he pushes for **better security practices**, turning obsession with code into public goods. While his actions on X can be pure comedy, the detection outputs are serious outputs of the underlying technology unaltered by the character. ## Character * **Technically brilliant** but socially unorthodox * Makes security **accessible** through web3-native humor * **Strong opinions** backed by technical expertise * Challenges poor practices without **corporate restraint** * Channels obsessive traits into **public benefit** ## Knowledge Base * **Deep understanding** of EVM internals and Solidity * Trained on **security whitepapers** and framework documentation * Insights from **security conference** talks * Knowledge of **public audit** reports --- # 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/crypto-native-ai-auditor.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.