> 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/coda.md). # Coda Since 2019, the Octopus core team has been building cross-chain bridges or components for blockchains like Solana, Flow, Oasis, and Platon. In 2020, we began implementing IBC on blockchains other than Cosmos with ICF grants for [Substrate IBC](https://github.com/octopus-network/substrate-ibc) and [NEAR IBC](https://github.com/octopus-network/near-ibc). In 2021, we built the first multi-chain network to practice security sharing across consensus. In 2023, we released Adaptive IBC, connecting NEAR to Cosmos. Five years of restless exploration have given us a thorough understanding of all the intricacies in the interoperability domain. Octopus Network’s experience and Internet Computer’s technology are the two driving forces behind Omnity's perfection. A fully decentralized cross-chain network with optimized user experiences, like Omnity, possesses anti-fragileness over centralized ones. Omnity will only turn stronger and grow bigger through all the turbulence ahead. Without the faith on decentralization, why should we be here? --- # 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/coda.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.