> For the complete documentation index, see [llms.txt](https://ottochains-organization.gitbook.io/ottochain-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ottochains-organization.gitbook.io/ottochain-documentation/abstract.md). # Abstract Ottochain stands as a revolutionary application-specific blockchain (Appchain) within the Octopus Network, poised to redefine the very essence of web3 and transform how communities perceive and interact with this groundbreaking technology. With its innovative features and forward-thinking approach, Ottochain has the potential to revolutionize the way applications are built, enhance the interrelationship between communities and their use cases, and provide unparalleled insights into the workings of application-specific blockchains. To do this, Ottochain is built from the ground up to deliver the best of experiences for end users, onboard communities and their various uniqueness, scale capacity across many ecosystems and provide developers with new, scalable and interoperable platform for their applications. *Note that, as with all complex systems under active development, the contents of this guide and the technology explained are both subject to change over time.* --- # 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://ottochains-organization.gitbook.io/ottochain-documentation/abstract.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.