Automated Market Maker (AMM)

Overview

An AMM holds reserves of two or more assets and calculates trade prices from a formula. Constant-product pools are a common design, but stable-swap, weighted, concentrated-liquidity, and dynamic models use different curves and capital-allocation rules.

A trade changes the pool’s reserves, causing the quoted price to move. Larger trades relative to pool liquidity create more price impact. Arbitrageurs trade between the AMM and external markets, helping align pool prices with broader market prices.

Liquidity providers earn a share of trading fees and may receive token incentives. Their return must be compared with simply holding the assets. When relative prices change, the pool automatically rebalances, creating impermanent loss. Concentrated liquidity can improve fee efficiency but can leave a position inactive or heavily exposed to one asset outside its selected range.

AMMs can be manipulated when other protocols use their spot price as an oracle. Time-weighted prices, liquidity thresholds, and independent oracle systems reduce this risk. Tokens with transfer taxes, rebasing, blacklisting, or callback behavior can also break assumptions.

Integrations should verify router, pool, token contracts, decimals, minimum output, deadline, and allowance target. A displayed annual yield can be dominated by temporary emissions.

Automated Market Maker (AMM) can appear in the same workflow as liquidity and transaction ordering, but the records should remain separately identifiable. A relationship between them does not prove that pricing, execution, settlement, custody, or accounting has completed.

A reliable review of Automated Market Maker (AMM) starts with the specific distinction in the definition: Traders swap against pooled assets, while liquidity providers supply the pool and can receive fees or incentives. This prevents a related quote, balance, order status, or provider response from being treated as proof of the final economic outcome.

Control evidence for Automated Market Maker (AMM) should cover asset, venue, executable size, depth, spread, access limits, withdrawal state, and settlement route. The definition also indicates that amms improve open market access but expose users to slippage, impermanent loss, smart-contract risk, oracle manipulation, toxic flow, and low-quality tokens. Keeping these details together makes later reconciliation and performance comparison possible without rewriting the original record.