> For the complete documentation index, see [llms.txt](https://omnity.gitbook.io/litepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://omnity.gitbook.io/litepaper/novel-solutions/zero-off-chain-components.md). # Zero Off-chain Components According to an old Chinese saying, for someone traveling 100 miles, quitting at 90 miles is the same as stopping halfway. Achieving complete decentralization from a state of near-complete decentralization involves overcoming significant challenges. Omnity is the first cross-chain system that does not rely on any off-chain components. Even in a worst-case scenario, where Omnity's DAO ceases operation, users could still redeem their assets to the settlement chain by recharging the canisters with less than 1 USD. Blockchains connected by Omnity have varying security assumptions and levels. Being an open and permissionless network, Omnity is designed to adapt to an environment where execution chains keep coming and going. Users will bear the risk of depositing assets in each execution chain and leaving them there. At the same time, Omnity ensures the isolation of each blockchain's security risks. Therefore, the maximum loss an execution chain fork could cause is capped at the total assets stored on that chain. --- # 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://omnity.gitbook.io/litepaper/novel-solutions/zero-off-chain-components.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.