> For the complete documentation index, see [llms.txt](https://docs.kima.network/kima-whitepaper-1/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kima.network/kima-whitepaper-1/introduction.md). # Introduction Blockchains are siloed. Web3 apps built within those ecosystems are constrained by their on-chain liquidity. Many of the solutions developed for these challenges - known as bridges - suffer from flaws and vulnerabilities: security, user experience, complexity, and poor capital efficiency. Kima addresses these challenges in a unique way, by creating a Web3 settlement layer, which enables interchain transactions. With this novel approach, liquidity can be transferred between chains in a safe, secure, and cost-effective manner - enabling the most reliable omnichain solution. There are two key concepts that distinguish the Kima solution: Its unique security is achieved by eliminating all known attack vectors (no smart contracts, no oracles, no external relayers) and adding multiple layers of security (such as using a Trusted Execution Environment (using Intel SGX) and decoupled validation). As a result, the protocol uses game theory and financial incentives to maintain the liquidity equilibrium and maximize capital efficiency. As a result, Kima's infrastructure simplifies and speeds up the creation of secure Omnichain applications. --- # 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.kima.network/kima-whitepaper-1/introduction.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.