> For the complete documentation index, see [llms.txt](https://docs.latch.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.latch.io/overview/latch-introduction.md). # Latch Introduction Latch is a blockchain interoperability protocol designed to unify yield, liquidity, and chains. By building a unified crypto UX, we are committed to accelerating the adoption of the on-chain financial system. #### **Why Go On-chain?** The on-chain financial system powered by decentralized blockchain and crypto offers unique values (vs. traditional finance): * Open and permissionless on a global scale * More transparent * More efficient * Trust-minimizing #### **The Problem** However, navigating through the on-chain financial system is quite complex and unintuitive. The ever-increasing numbers of chains, tokens, and assets are fragmenting the user & developer experiences. #### **The Solution** To address fragmentation issues and achieve interoperability, the Latch Protocol is building on liquid staking/re-staking, cross-chain liquidity management, and intent settlement infrastructures. Our first product is Smart Savings built on Gravity Chain, aiming to achieve: * **Omni-chain Yield:** Deposit your idle tokens on any chain, select a preferred vault, and earn yields & points with ease * **On-demand Liquidity:** Unlock liquidity to your staked savings on all chains instantly * **Universal Balance:** Enjoy a unified savings balance that can be spent on all chains, and in all supported dApps More features to come in future iterations. Stay tuned for updates. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.latch.io/overview/latch-introduction.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.