> For the complete documentation index, see [llms.txt](https://docs.octora.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.octora.xyz/documentation/introduction/why-octora.md). # Why Octora? On public blockchains, wallet activity is visible by default. For traders and liquidity providers, that transparency can be useful in some contexts—but it also creates a structural disadvantage. If a wallet builds strong LP strategies over time, those positions can become easy to observe, map, and copy. For liquidity providers, privacy matters because: * strategy entry points can become legible * wallet histories can be clustered and monitored * successful positioning can attract copy-trading behavior * users may want execution privacy without leaving the on-chain liquidity ecosystem Octora exists to explore a different model: private execution for LP workflows. Rather than asking users to abandon on-chain venues, Octora aims to make participation more privacy-aware while preserving a familiar liquidity workflow. --- # 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://docs.octora.xyz/documentation/introduction/why-octora.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.