> For the complete documentation index, see [llms.txt](https://docs.amara.exchange/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.amara.exchange/core-innovations/unified-liquidity-layer.md). # Unified Liquidity Layer Most decentralized exchanges are siloed. Spot swaps live in one protocol, perpetuals live in another, and users are forced to move between them. This separation fragments liquidity, splits user activity, and limits capital efficiency. Amara takes a different approach. The protocol combines both perpetual trading and spot swaps under one system, giving users access to two distinct liquidity models through a single platform. * The **perpetual engine** (forked from GMX) is backed by a vault-style pool. This pool holds collateral such as USDC, DIONE, and synthetic assets, which traders use to open long and short positions. * The **spot swap module** (forked from PancakeSwap) uses traditional AMM pairs. Liquidity providers deposit token pairs into pools, and traders swap against them at algorithmically determined prices. By housing both engines in one protocol, Amara delivers a unified liquidity layer. Traders can move seamlessly between swaps and leverage trades without leaving the platform. Liquidity providers can choose the model that fits their strategy, whether vault-based exposure or AMM-style pools. The result is deeper markets, more consistent activity, and a stronger overall trading environment. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.amara.exchange/core-innovations/unified-liquidity-layer.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.