# Overview The advent of new Layer 1 and Layer 2 blockchains has accentuated the critical challenge of interoperability within the blockchain ecosystem. Despite numerous protocols being introduced to enable seamless cross-chain transfers of tokens and messages, a significant gap remains in the management of liquidity for omni-chain assets, which is predominantly left to the discretion of end users. This oversight imposes an undue complexity on users, necessitating them to navigate the intricacies of cross-chain liquidity independently. Liqua emerged as a pioneering protocol aimed at transforming liquidity management in the cross-chain domain, transcending the conventional focus on bridging services alone. Amidst the intricate landscape of blockchain interoperability, Liqua distinguishes itself by offering an innovative AI-powered solution for the efficient management of liquidity across disparate blockchains. Conventional cross-chain mechanisms often falter, plagued by inefficient liquidity utilization, constrained network coverage, and lackluster smart contract integrations on target chains. Liqua introduces a comprehensive and effective framework designed to optimize liquidity usage across a wide spectrum of blockchains. The protocol's intent-based routing and AI-based liquidity distribution significantly boost the efficiency and functionality of cross-chain transactions, marking a substantial advancement in the field. Additionally, Liqua features a Hierarchy Unified Liquidity Network, which further enhances its ability to manage and distribute liquidity across multiple chains seamlessly. --- # Agent Instructions: 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: ``` GET https://liqua-1.gitbook.io/liqua-whitepaper/overview.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.