> For the complete documentation index, see [llms.txt](https://docs.ston.fi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ston.fi/developer-section/dex/overview.md). # Overview (DEX) STON.fi DEX overview - decentralized exchange with AMM pools, liquidity provision, and yield farming on TON STON.fi DEX is a decentralized exchange protocol that enables permissionless token swaps and liquidity provision on the TON blockchain. ## Core Features ### Token Swaps * Direct token-to-token exchanges using liquidity pools * Constant Product Market Maker (x\*y=k) algorithm * Fees configurable per pool — see [Fees](/developer-section/dex/fees.md) ### Liquidity Provision * Add liquidity to earn trading fees * Receive LP tokens representing your pool share * Single-sided liquidity provision (v2 only) ### Yield Farming * Stake LP tokens in farms to earn additional rewards * Multiple farming pools available * Flexible staking and unstaking ## How It Works 1. **Swaps**: Users trade tokens through liquidity pools, paying a small fee 2. **Liquidity**: Providers deposit token pairs to earn a share of trading fees 3. **Farming**: LP token holders can stake in farms for additional yield ## Integration Options * **SDK**: High-level TypeScript/JavaScript interface * **Smart Contracts**: Direct on-chain interaction * **REST API**: HTTP endpoints for data queries ## Security * Non-custodial: Users maintain control of funds * Immutable pool contracts: Core logic cannot be changed * Time-locked upgrades: Router updates have 7-day delay * Open source: All contracts are publicly verifiable --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.ston.fi/developer-section/dex/overview.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.