AMM DEX Development on Uniswap V2/V3 with Audit

When we took on the first AMM DEX for a DeFi client, a miscalculation of price impact led to a $50k loss within an hour. Since then, we double-check every formula and rely only on battle-tested patterns. Building an AMM DEX is not just writing a smart contract—it's a complex system: pricing math, MEV protection, pool economics, and UX. In this article, we break down how to build a DEX from scratch: from the constant product formula to mainnet deployment. We've already delivered DEXs for 10+ projects, with total value locked exceeding $50M. Our experience spans Ethereum, Arbitrum, Polygon, and BNB Chain. If you're planning your own DEX launch, you'll need more than code—you need market-making and security expertise. Here we share practical solutions.

Why the Constant Product Formula is Still Relevant

AMM (Automated Market Maker) replaces the traditional order book with a mathematical formula. Uniswap V2 popularized x * y = k—the product of reserves remains constant. The price of token X in units of Y is price = y / x. During a swap, the trader contributes Δx and receives Δy, accounting for a 0.3% fee. Price impact—the price shift—is directly proportional to the trade size relative to the pool. This is fundamental: large orders get poor pricing in small pools.

The formula with fee: Δy = y * Δx * (1 - fee) / (x + Δx * (1 - fee)). Despite its simplicity, it's inefficient for assets with the same price (stablecoins). That's where Curve's hybrid formula comes in.

How Concentrated Liquidity Changes Capital Efficiency

Uniswap V3 introduced concentrated liquidity: LPs specify a price range [Pa, Pb]. Outside that range, liquidity is inactive. Formulas: x = L * (1/√P - 1/√Pb), y = L * (√P - √Pa). Capital efficiency increases 100-4000x for stablecoin pairs, but LPs face a more complex impermanent loss.

AMM DEX Smart Contract Architecture

A typical architecture consists of Factory, Pair (Pool), and Router contracts. The Factory creates pools via CREATE2:

contract AmmFactory {
    mapping(address => mapping(address => address)) public getPair;
    function createPair(address tokenA, address tokenB) external returns (address pair) {
        require(tokenA != tokenB, "IDENTICAL_ADDRESSES");
        (address token0, address token1) = tokenA < tokenB ? (tokenA, tokenB) : (tokenB, tokenA);
        require(token0 != address(0), "ZERO_ADDRESS");
        require(getPair[token0][token1] == address(0), "PAIR_EXISTS");
        bytes memory bytecode = type(AmmPair).creationCode;
        bytes32 salt = keccak256(abi.encodePacked(token0, token1));
        assembly { pair := create2(0, add(bytecode, 32), mload(bytecode), salt) }
        IAmmPair(pair).initialize(token0, token1);
        getPair[token0][token1] = pair;
        getPair[token1][token0] = pair;
    }
}

The Pair contract is the core: it stores reserves, issues LP tokens, executes swaps with optimistic transfer and invariant check. The flash loan pattern is embedded via callback:

function swap(uint amount0Out, uint amount1Out, address to, bytes calldata data) external lock {
    (uint112 _reserve0, uint112 _reserve1,) = getReserves();
    if (amount0Out > 0) _safeTransfer(_token0, to, amount0Out);
    if (amount1Out > 0) _safeTransfer(_token1, to, amount1Out);
    if (data.length > 0) IUniswapV2Callee(to).uniswapV2Call(msg.sender, amount0Out, amount1Out, data);
    uint balance0 = IERC20(_token0).balanceOf(address(this));
    uint balance1 = IERC20(_token1).balanceOf(address(this));
    uint amount0In = balance0 > _reserve0 - amount0Out ? balance0 - (_reserve0 - amount0Out) : 0;
    uint amount1In = balance1 > _reserve1 - amount1Out ? balance1 - (_reserve1 - amount1Out) : 0;
    require(amount0In > 0 || amount1In > 0, "INSUFFICIENT_INPUT_AMOUNT");
    uint balance0Adjusted = balance0 * 1000 - amount0In * 3;
    uint balance1Adjusted = balance1 * 1000 - amount1In * 3;
    require(balance0Adjusted * balance1Adjusted >= uint(_reserve0) * _reserve1 * 1000**2, "K");
    _update(balance0, balance1, _reserve0, _reserve1);
}

The Router contract provides multi-hop routes, slippage protection, and deadline.

MEV and Reentrancy Protection

A classic sandwich attack: an MEV bot inserts a buy before the victim's swap and a sell after. Protection: Slippage tolerance—the user sets a maximum price impact; private mempool (Flashbots); commit-reveal schemes; batch auctions (CoW Protocol)—all orders executed at a single price.

Reentrancy protection: the mutex lock uses a single storage slot, saving ~2300 gas compared to OpenZeppelin's ReentrancyGuard.

uint private unlocked = 1;
modifier lock() {
    require(unlocked == 1, "LOCKED");
    unlocked = 0;
    _;
    unlocked = 1;
}

Tokenomics and Governance

We recommend a two-tier fee structure: LP fee (0.3%) + protocol fee (0.05%), even if the protocol fee is initially turned off. Governance tokens are distributed via liquidity mining using the MasterChef pattern (SushiSwap). Simplified formula: pendingReward = userLPBalance * (accRewardPerShare - userRewardDebt) / 1e12.

Frontend and UX

Critical components: swap interface with real-time price impact, liquidity management with range visualization (for V3), charts via The Graph, wallet integration (wagmi + viem, WalletConnect v2), transaction simulation through Tenderly.

How to Deploy an AMM DEX in 5 Steps

1. Develop smart contracts (Factory, Pair, Router) with Foundry tests.
2. Security audit (Slither, Mythril, Echidna) and formal verification.
3. Deploy to testnet, integrate with frontend.
4. Test liquidity pools with real tokens.
5. Deploy to mainnet, set up monitoring (Tenderly, Etherscan API).

What's Included in AMM DEX Development

Why Order Development from Us?

We guarantee code quality and audit readiness. Our track record—over 10 successful DEX projects, including Layer 2 integrations (Arbitrum, Optimism). We use proven patterns and libraries. Uniswap V2 Whitepaper is the foundation we adapt to your needs. Automated Market Maker is the key mechanism at the core. Contact us for a free consultation and project evaluation. Order turnkey AMM DEX development—from idea to deployment and support.

Why exchange development requires deep domain expertise

We develop exchanges — not 'chart sites,' but matching engines that process thousands of orders per second without delay, route liquidity between pools, and guarantee that no user gains access to others' funds. Teams that start with the UI and postpone the engine 'for later' end up rewriting everything in six months in 90% of cases.

Order Book vs AMM: where most projects break

Centralized exchanges (CEX) are built around an order book + matching engine. Decentralized exchanges (DEX) either also use an order book (dYdX on StarkEx, Serum/OpenBook on Solana) or an AMM with concentrated liquidity (Uniswap v3/v4, Curve, Balancer). A classic mistake when developing a CEX is implementing the matching engine on top of a relational database with transactions for each match. PostgreSQL handles ~500 RPS without special effort, but at peak loads of 5,000–10,000 orders per second, it turns into a deadlock nightmare. The correct architecture: in-memory order book (Redis Sorted Sets or custom C++/Rust structure), asynchronous writing of matches to PostgreSQL via a queue (Kafka/RabbitMQ), and a separate settlement service that finally updates balances.

For DEX, the most painful problem is sandwich attacks and MEV. A pool with a plain xy=k AMM without slippage protection becomes a target for MEV bots within hours of launch. Uniswap v2 lost hundreds of millions of dollars in user liquidity. Solutions: integration with Flashbots Protect, a commit-reveal scheme for orders, or switching to TWAMM (Time-Weighted AMM) for large trades.

Concentrated liquidity and impermanent loss

Uniswap v3 introduced concentrated liquidity – LPs choose a price range in which to provide liquidity. Capital efficiency increased 4,000x compared to v2 for stable pairs. But implementing this mechanism correctly is non-trivial. The Uniswap v3 liquidity contract uses tick-based accounting: the price space is divided into discrete ticks (tick = log₁.0001(price)), each tick stores accumulated fee growth and liquidity delta. When creating a position, the lower and upper ticks are computed, and the contract recalculates all active positions at each swap. Storage layout is critical here – incorrect variable packing in slots easily adds 40–60% to swap gas cost.

We implemented a Uniswap v3 fork for a client on Polygon with a custom fee tier system. The initial version consumed 180k gas for a swap across 2 ticks. After slot packing of variables in Tick.Info and inlining several internal calls, it dropped to 112k gas. This reduced gas costs by 38% and saved the client substantial costs on fees monthly. The techniques applied are described in the Uniswap v3 Whitepaper and confirmed by our audit experience.

How a matching engine delivers performance

A production-ready matching engine is built according to the following scheme:

• Order ingestion layer – WebSocket gateway (Go or Rust), accepts orders, validates signature, checks balance via Redis, queues them. Latency at this level must be <1ms.
• Matching core – single-threaded event loop (eliminates race conditions without mutexes). In memory, we hold two Sorted Sets for each trading instrument: bids and asks. FIFO matching for limit orders, immediate-or-cancel for market orders. Throughput with a proper Rust implementation – 500k–1M matches per second on a single core.
• Settlement service – reads matches from Kafka, atomically updates balances in PostgreSQL (UPDATE accounts SET balance = balance - $1 WHERE id = $2 AND balance >= $1). Optimistic locking via row versioning.
• Withdrawal pipeline – separate service with cold/hot wallet architecture. The hot wallet holds 5–10% of total deposits, the rest is cold storage with multi-sig (Gnosis Safe or custom HSM). Automatic withdrawals only from hot wallet, large amounts require manual authorization.

How our exchange development process ensures reliability

Smart contracts and gas optimization

For EVM-based DEX (Ethereum, Arbitrum, Optimism, Polygon), the entire critical path lives in Solidity. Main contracts: Pool, Factory, Router, PositionManager (for v3-like), and Quoter for off-chain calculations. Typical mistakes we see in audits:

Reentrancy via callback. Uniswap v3 uses flash swap with a callback (uniswapV3SwapCallback). If your router lacks a nonReentrant guard and you don't check msg.sender == pool, the contract gets drained via a nested call. This is not hypothetical – several v3 forks lost funds this way.

Oracle manipulation in AMM. If your contract uses the spot price from the pool for collateral calculation, it is front-runnable. Correct: TWAP over 30+ minutes (Uniswap v3 OracleLib) or an external oracle (Chainlink).

Unbounded loops in liquidity range. If a swap crosses many ticks in a row (price impact 80%+), gas may exceed the block limit. Need MAX_TICKS_CROSSED with partial fill and returning the remainder.

For Solana DEX (Anchor framework, Rust), the architecture is fundamentally different: account-based model, Program Derived Addresses (PDA) instead of storage, Cross-Program Invocations instead of internal calls. Solana's throughput (~3,000–4,000 TPS vs 15–30 on Ethereum mainnet) allows building on-chain order books – exactly what Phoenix DEX does.

Liquidity bootstrapping and aggregator integration

Launching a pool is not enough – you need to ensure liquidity at launch. Practical mechanisms:

• Liquidity Bootstrapping Pool (LBP) – initial price is high, asset weights dynamically shift, creating selling pressure and even token distribution. Implemented in Balancer v2.
• Initial Liquidity Offering via Uniswap v3 – adding liquidity in a narrow range around the initial price, then gradually expanding as volume grows. Requires active liquidity management or integration with Arrakis/Gamma.
• Integration with 1inch, Paraswap, Li.Fi – aggregators bring traffic but require standard compliance: the pool must have correct getAmountsOut, support ERC-20 approval/permit, and not have custom transfer hooks that break the aggregator's routing.

Development process and deliverables

Analytics and design begin with choosing the architectural model: CEX with custodial storage, non-custodial DEX, or hybrid (off-chain order book + on-chain settlement, like dYdX v3). This decision determines everything – regulatory load, tech stack, team.

Development proceeds in layers: first smart contracts with full Foundry coverage (fuzzing, invariant testing), then backend services, then integration layer, and finally frontend. Testing includes fork testing on mainnet via Foundry – we reproduce real liquidity conditions, not synthetic ones.

Audit is mandatory before mainnet deployment. For DEX contracts, minimally one firm with manual review (Trail of Bits, Spearbit, Code4rena contest). For CEX custody, audit of key storage processes. We guarantee all contracts undergo formal verification and fuzzing testing (Echidna, Foundry invariant).

Estimated timelines

Cost is calculated individually after a technical briefing: chain selection, throughput requirements, custodial model. Our certified engineers with 10+ years of experience will help you choose the optimal architecture and avoid common pitfalls. Contact our team for a detailed proposal.

Pitfalls to avoid at launch

• Forgetting the price oracle in AMM. Spot price can be manipulated with a flash loan in one transaction. If your lending protocol uses the spot price from its own pool, that's a bug.
• Hot wallet without limits. A CEX without daily limits on automatic withdrawals is an invitation for attackers. Compromising one key should lose at most 10% of total funds.
• Absence of circuit breaker. A 40% price drop in 5 minutes should halt automatic liquidations or withdrawals until manual review. Without this, a cascading liquidation spiral destroys all TVL.
• Incorrect decimal handling. USDC uses 6 decimals, WBTC – 8, most tokens – 18. Mixing without normalization leads to either precision loss or overflow. Solidity has no float; we work with fixed-point using FullMath (mulDiv with overflow protection).

Want to avoid these problems? Get a consultation — we will select the architecture for your project and provide exact timelines. Order exchange development with quality guarantee and ongoing support.