# What is Fly solving? ## Complexity and Fragmentation Most of the liquidity not on Ethereum in DeFi is spread across over 50 chains and hundreds of DEXs. As a result, DeFi remains fragmented, each with their own interfaces, DEXs, liquidity pools, unique features, and in some cases different wallet requirements. This creates a steep learning curve, especially for new users or those unfamiliar with multi-chain environments, resulting in a complicated and often frustrating user experience where it becomes difficult to both find the token you need or the DEX with the best price and liquidity. ## Slippage and Inefficient Liquidity With liquidity scattered across chains, users can often encounter significant slippage, high transaction costs, and sub-optimal execution prices during swaps. Identifying the most efficient liquidity paths can be time-consuming and inefficient, further impacting trade outcomes. ## Poor User Experience Many current DeFi platforms often fall short in delivering a seamless on or cross-chain experience, from unintuitive interfaces to linking users to upwards of 15-20 other protocol options to assist in their transactions, creating complex transaction flows, which leads to friction, frustration, and ultimately, abandonment of platforms. ## Gas Fee Optimization Gas fees can start to become burdensome when conducting cross-chain transactions, or even when conducting multiple same-chain swaps, particularly when inefficient routing leads to suboptimal trade execution. This is a barrier to DeFi adoption, especially for users who frequently perform cross-chain activities. --- # 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://docs.fly.trade/fly/what-is-fly-solving.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.