# Why DEX? Currently the asset classes and liquidity on the blockchain are severely fragmented. To trade every markets, users often need multiple wallets, with different coins, on different chains alongside multiple sites and terminals. For example, traders use a different terminal for each chain to trade tokens, they need another liquid venue to buy major coins, prediction markets happen on a different chain and platform - et cetera. Managing assets across this ecosystem can be complex, expensive and time-consuming. As a result, many users continue to rely on centralized exchanges simply because they're easier to use aggregating all these asset classes in one place. #### DEX is the solution. We combines the simplicity of a centralized exchange with the transparency and ownership of decentralized finance. Instead of switching between platforms, DEX brings everything together in one place. One account. One portfolio. Every market. Users can access crypto, perpetual futures, prediction markets, tokenized stocks, yield opportunities, and onchain assets through a single seamless experience. #### Why it matters Decentralized infrastructure has never been more powerful. Protocols like Hyperliquid, Polymarket, AAVE, and other leading onchain applications have transformed what's possible. We're finally in a time where everything that can be done on a CEX, can be done in DeFi where you actually own the coins and execute the trades yourself. DEX abstracts away unnecessary complexity so users can focus on what matters: discovering opportunities, managing risk, and trading the markets they care about. --- # 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://about.dex.org/welcome-to-dex/why-dex.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.