# Identifying a DEX pool: token pair, network, fee and contract A useful pool identifier includes the network, protocol version, token contract addresses and the version-specific pool parameters. In Uniswap v3, a factory creates distinct pools for a token pair and fee. Two screens showing the same token symbols can therefore describe different liquidity and execution. Evidence: [Uniswap v3 protocol architecture](https://docs.uniswap.org/contracts/v3/reference/core/UniswapV3Factory); [Fees](https://docs.uniswap.org/concepts/protocol/fees) Canonical: https://degreesofsatoshi.com/encyclopedia/identifying-dex-pools/ Published: 2026-10-02 Substantively modified: 2026-10-02 Independently verified by an automated reviewer: 2026-10-02T19:18:00.092Z Data current through: 2026-10-02 AI-assisted research and drafting with a separate automated source-verification pass; no external expert or named human review is implied. ## Key facts - **v3 identity:** A pool is defined by two token contracts and a fee within its factory. ([Uniswap v3 protocol architecture](https://docs.uniswap.org/contracts/v3/reference/core/UniswapV3Factory)) - **Multiple pools:** The same asset pair can have different fee-tier pools. ([Uniswap v3 protocol architecture](https://docs.uniswap.org/contracts/v3/reference/core/UniswapV3Factory)) - **Version matters:** v4 fee and hook arrangements differ from v3. ([Fees](https://docs.uniswap.org/concepts/protocol/fees)) ## Record identifiers before comparing statistics A pair name such as A/B is a display label. For a reproducible comparison, retain chain, factory or deployment, pool address, both asset addresses and fee parameters. The pool address identifies the specific contract state being measured. This also prevents a bridge representation or unrelated token with the same symbol from silently entering the comparison. Evidence: [Uniswap v3 protocol architecture](https://docs.uniswap.org/contracts/v3/reference/core/UniswapV3Factory) ## Two pools can offer different outcomes Imagine two v3 pools for the same contracts: one charges a lower trading fee but has little active liquidity; the other charges more but has deeper inventory near the current price. For a particular trade, lower fees do not necessarily produce more output. Compare an executable quote for the same input at the same time. Total historical volume or total value across every pool is not a substitute for the route’s current execution. Evidence: [Uniswap v3 protocol architecture](https://docs.uniswap.org/contracts/v3/reference/core/UniswapV3Factory); [Fees](https://docs.uniswap.org/concepts/protocol/fees); [Concentrated Liquidity](https://docs.uniswap.org/concepts/protocol/concentrated-liquidity) ## Separate pool statistics from routed trades A router can use several pools for a trade. A final transaction’s route should be compared with the pools actually touched, rather than whichever pool page was open beforehand. Pool identity is the starting point for reading fees, reserves and oracle data; it does not certify the pool’s safety. Evidence: [Uniswap v3 protocol architecture](https://docs.uniswap.org/contracts/v3/reference/core/UniswapV3Factory); [Single Swaps](https://docs.uniswap.org/contracts/v3/guides/swaps/single-swaps) ## Questions ### Does the biggest pool always give the best quote? No. Active liquidity, pool fees, the requested size and route execution costs matter. Compare final outputs under equivalent assumptions. Evidence: [Concentrated Liquidity](https://docs.uniswap.org/concepts/protocol/concentrated-liquidity); [Fees](https://docs.uniswap.org/concepts/protocol/fees); [Single Swaps](https://docs.uniswap.org/contracts/v3/guides/swaps/single-swaps) ## Claims and scope ### identifying-dex-pools-quick-answer A useful pool identifier includes the network, protocol version, token contract addresses and the version-specific pool parameters. In Uniswap v3, a factory creates distinct pools for a token pair and fee. Two screens showing the same token symbols can therefore describe different liquidity and execution. Scope: {"collection":"defi","dataAsOf":"2026-10-02","blockHeight":null} ### identifying-dex-pools-fact-v3-identity v3 identity: A pool is defined by two token contracts and a fee within its factory. Scope: {"collection":"defi","dataAsOf":"2026-10-02","blockHeight":null} ### identifying-dex-pools-fact-multiple-pools Multiple pools: The same asset pair can have different fee-tier pools. Scope: {"collection":"defi","dataAsOf":"2026-10-02","blockHeight":null} ### identifying-dex-pools-fact-version-matters Version matters: v4 fee and hook arrangements differ from v3. Scope: {"collection":"defi","dataAsOf":"2026-10-02","blockHeight":null} ## Sources - [Uniswap v3 protocol architecture](https://docs.uniswap.org/contracts/v3/reference/core/UniswapV3Factory) — Uniswap. Factory deploys pools for a token pair and fee; network identification remains necessary. Locator: uniswap-v3-core / Factory paragraph in the redirected v3 contracts overview. Retrieved: 2026-10-02T18:53:20.189Z. - [Fees](https://docs.uniswap.org/concepts/protocol/fees) — Uniswap. Separates liquidity-provider and protocol accounting; no universal live fee schedule asserted. Locator: Swap fees; Pool fees tiers; Protocol fees. Retrieved: 2026-10-02T18:53:19.509Z. - [Concentrated Liquidity](https://docs.uniswap.org/concepts/protocol/concentrated-liquidity) — Uniswap. Active range, inventory changes and fee earning. Locator: Active liquidity; ticks. Retrieved: 2026-10-02T18:53:19.537Z. - [Single Swaps](https://docs.uniswap.org/contracts/v3/guides/swaps/single-swaps) — Uniswap. Version-specific router constraints and worked integration examples. Locator: exactInputSingle; exactOutputSingle; deadline; amountOutMinimum; amountInMaximum. Retrieved: 2026-10-02T18:53:19.662Z. ## Revision history - 2026-10-02: First publication after primary-source research and separate automated verification. ## Cite this entry Degrees of Satoshi editorial project. “Identifying a DEX pool: token pair, network, fee and contract.” Published 2026-10-02; updated 2026-10-02. https://degreesofsatoshi.com/encyclopedia/identifying-dex-pools/