10 October 2026 · 3 min read
DEX development, what changes when there is no custody
An AMM, a router and a front end against contracts you do not control. Cheaper in some ways, far more expensive in the ways that matter, and a different business entirely.
A decentralised exchange removes the thing that makes a centralised one hard: you never hold anybody's funds. It replaces it with something equally hard: code that cannot be patched after people trust it with money.
What a DEX is made of
- Pools and an AMM, or an on chain order book. Pricing is a formula and a reserve balance rather than matching.
- A router that finds a path between two assets across pools.
- Liquidity provider accounting: shares, fees earned, impermanent loss nobody enjoys explaining.
- A front end that connects a wallet, simulates, prices slippage and submits.
- Subgraphs or an indexer, because chains are terrible at answering "show me this user's history".
The costs invert
Custody disappears. In its place:
- Audits. Contracts holding pooled funds need review by people who do this full time, and that is usually more than the rest of the build.
- Immutability. A bug in a deployed contract is not a hotfix. It is a migration, if you are lucky, and a loss if you are not.
- Gas. Every user action costs real money, so each extra on chain step is a tax on your own conversion rate.
- Upgrade design. Proxy patterns, timelocks and admin keys all need to be decided before launch and all of them reintroduce trust you were trying to remove.
On a centralised venue the risk is operational and you can fix it on Tuesday. On a DEX the risk is final and your fix is a redeploy that nobody has to use.
Who it actually suits
- Listing assets that no centralised venue will touch.
- Users who will not deposit to a custodial platform under any circumstances.
- A token project that wants its own trading surface and already has the liquidity.
Who it does not suit: operators who want fee revenue from day one. Without liquidity a pool quotes terrible prices, and nothing you build in the interface changes that.
The honest middle
Many people asking for a DEX actually want the two parts they can describe: non custodial, and one screen to convert. An instant swap with routing to existing venues delivers both without deploying contracts that hold pooled funds, and it can run from day one.
If the requirement is genuinely on chain, the sequence is contracts and audit first, interface last. Building the interface first against unaudited contracts is how projects end up shipping the interface on time and the contracts never.
Questions
How much does DEX development cost
It is quoted per project, and the contract audit is usually the largest line rather than the build. A front end against existing, audited contracts is a much smaller job than a new AMM.
Is a DEX cheaper than a centralised exchange
Not meaningfully. You remove custody and add audits, gas economics and the permanence of deployed code. The money moves rather than disappearing.
Can you build a Uniswap style exchange
Yes. The usual honest version is a front end and router against established, audited contracts rather than new pool contracts nobody has reviewed.
What is impermanent loss and do I have to explain it
It is the loss a liquidity provider takes when pool prices diverge from the market. You do have to explain it, in the interface, before someone deposits. Venues that hide it lose providers permanently.
Does a DEX need KYC
Usually no at the protocol level, and that is the point. Whether your front end needs it is decided by local law, so ask a lawyer rather than a developer.
Should I launch a DEX or a swap
If you need non custodial plus a simple convert screen, a swap gets there now. If you need permissionless listing and on chain settlement, it has to be a DEX.