Skip to article
Degrees of SatoshiFollow the connections.
SearchTrace an address
Degrees of Satoshi/ Encyclopedia

Encyclopedia DeFi · Entry 320

Identifying a DEX pool: token pair, network, fee and contract

AI-assisted research · separate automated verificationCorrections

Theme
DeFi
Sources
4 cited records
Reading time
About 3 minutes
Automated verification
Substantive update
In this article

At a glance

Key facts

Key facts for Identifying a DEX pool: token pair, network, fee and contract
FactDetailSource
v3 identityA pool is defined by two token contracts and a fee within its factory.[1]
Multiple poolsThe same asset pair can have different fee-tier pools.[1]
Version mattersv4 fee and hook arrangements differ from v3.[2]
01

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.

02

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.

03

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.

Direct answers

Questions people ask

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.

Inspect the evidence

The answer and key facts have stable claim links. These records retain the scope and qualification when reused.

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: DeFi · data through 2026-10-02. Verification: verified · 2026-10-02T19:18:00.092Z.

Link to this claim
v3 identity: A pool is defined by two token contracts and a fee within its factory.

Scope: DeFi · data through 2026-10-02. Verification: verified · 2026-10-02T19:18:00.092Z.

Link to this claim
Multiple pools: The same asset pair can have different fee-tier pools.

Scope: DeFi · data through 2026-10-02. Verification: verified · 2026-10-02T19:18:00.092Z.

Link to this claim
Version matters: v4 fee and hook arrangements differ from v3.

Scope: DeFi · data through 2026-10-02. Verification: verified · 2026-10-02T19:18:00.092Z.

Link to this claim
Revision history
  1. — First publication after primary-source research and separate automated verification.

Source register

Sources and references

Retrieval dates and locators are recorded individually.
  1. Uniswap v3 protocol architectureUniswap

    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 · Version / scope: Documentation retrieved for the 2026-10-02 editorial scope; content hash recorded · Retrieved: 2026-10-02T18:53:20.189ZOpen source
  2. FeesUniswap

    Separates liquidity-provider and protocol accounting; no universal live fee schedule asserted.

    Locator: Swap fees; Pool fees tiers; Protocol fees · Version / scope: Documentation retrieved for the 2026-10-02 editorial scope; content hash recorded · Retrieved: 2026-10-02T18:53:19.509ZOpen source
  3. Concentrated LiquidityUniswap

    Active range, inventory changes and fee earning.

    Locator: Active liquidity; ticks · Version / scope: Documentation retrieved for the 2026-10-02 editorial scope; content hash recorded · Retrieved: 2026-10-02T18:53:19.537ZOpen source
  4. Single SwapsUniswap

    Version-specific router constraints and worked integration examples.

    Locator: exactInputSingle; exactOutputSingle; deadline; amountOutMinimum; amountInMaximum · Version / scope: Documentation retrieved for the 2026-10-02 editorial scope; content hash recorded · Retrieved: 2026-10-02T18:53:19.662ZOpen source
How this article was made

Research and drafting use AI assistance. A separate automated review checks claims against primary sources; no external expert or named human review is implied. Publication, substantive editing, source retrieval and verification are recorded separately. This version was independently checked by an automated reviewer on 2 October 2026.

Editorial method and corrections

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/