> For the complete documentation index, see [llms.txt](https://cybercentry.gitbook.io/cybercentry/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cybercentry.gitbook.io/cybercentry/whitepaper.md). # Whitepaper **Securing the Digital Landscape. Smarter, simpler and more accessible cyber security awaits!** **Leigh Cronian** – Founder and Managing Director Version: 1.3 Date: 17 May 2026 *** Leigh Cronian is the visionary behind Cybercentry. With extensive experience in cyber security, blockchain infrastructure, and autonomous AI systems, Leigh co-authored the **ERC-8126** standard with the Virtuals Protocol team and spearheaded the development of the live ERC-8126scan platform. Under Leigh’s leadership, Cybercentry evolved from a 2025 hackathon finalist into a fully tokenised, production-ready security layer for the entire on-chain AI agent economy, delivering real utility through $CENTRY and protecting agents across all EVM chains. This is cyber security built for the AI agent era, by someone who actually understands both the threats and the technology. --- # 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://cybercentry.gitbook.io/cybercentry/whitepaper.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.