# DEX Market Structure ### Market Structure, Trends & TAM (”Intents” and “Solvers”) The DEX market is rapidly moving toward an aggregator-based ‘intents’ model, in which user-facing frontends (e.g. 1inch Fusion, Metamask, UniswapX, Cowswap, etc) allow third party ‘solvers’ to compete to fill trades by composing in multiple sources of liquidity. These solvers always algorithmically route in the DEX offering the best price. Since Clipper has best prices, it tends to win these trades. 95% of Clipper’s volume comes from 1inch and UniswapX. Clipper is the only onchain permissioned filler for UniswapX. The “big win” for Clipper would be processing the majority of all DeFi spot volume (\~$1 Trillion annually). This solely requires winning the market for ETH<>USD (and on other chains the native token of that chain). The more the DEX market moves toward a ‘solver’ model, the more possible this becomes, because solvers will algorithmically route to Clipper. ***One could can think of Clipper as a leveraged bet on the trend of Aggregators, Intents & Solvers.*** Note this is not financial advice and we give no assurances or predictions about SAIL price. ### Clipper Roadmap Clipper’s roadmap (proposed by and subject to approval by DAO governance) prioritizes: * Increasing volume by deploying new Solvers and on new Chains. * Increasing TVL by improving the LP UX, analytics, and integrating with third party vaults. * Full roadmap here: * --- # 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.admiraldao.xyz/community-governance/sail-primer/dex-market-structure.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.