Most decentralised exchange volume does not arrive at the exchange. It arrives at an aggregator, which splits the trade across whichever pools produce the best result and sends it on. For anyone providing liquidity, this means the aggregator decides whether the pool earns anything.
What an aggregator is actually solving
Given a token in and a token out, the aggregator searches for the path that leaves the trader with the most. That path is frequently not one pool. It may be a split across several venues, or a multi-hop route through an intermediate asset, or both at once.
This is why a pool can hold real depth and still receive nothing. If a competing route is a fraction cheaper, it takes the whole trade. Routing is winner-take-most, not proportional.
The four things that decide the route
- Price impact at the requested size. The dominant factor, and the reason depth matters more than fee tier on large trades.
- Pool fee. Decisive between pools of similar depth, irrelevant between pools of very different depth.
- Gas cost of the path. A route across four pools may quote better and net worse once execution is paid for, which is why aggregators favour shorter paths on expensive chains.
- Whether the pool is indexed at all. Not a factor so much as a precondition. An unindexed pool is not considered.
Why the best quote is not always the best fill
A quote is a calculation against the pool state at quote time. Between then and inclusion, other trades land, and on a thin pool the difference between quoted and received can be substantial.
Routes that split across many pools are more exposed to this, because every leg can move independently. A slightly worse quote through a single deep pool often fills better than an optimal-looking split, which is the practical case for depth over cleverness.
How a pool gets included
Indexing is usually automatic once a pool clears a liquidity threshold and shows trade history, but two things are not automatic and both are commonly missed.
The first is token metadata. Name, symbol, decimals and logo come from token lists that aggregators read, and a token absent from them displays as a bare address in the routing interface. The second is the exchange itself: on a newer venue, the aggregator may not have integrated the exchange’s contracts at all, and no amount of pool depth changes that. Check whether other pools from the same exchange already appear before funding one.
What this means for a token launch
Concentrate liquidity rather than spreading it. Two shallow pools on two exchanges lose to one adequate pool on either, because the aggregator routes to the better one and the other earns nothing while still holding capital.
Pair against an asset that routes cleanly. A pair against a major stablecoin or the chain’s native asset is one hop from almost anything. An exotic pairing forces the aggregator into multi-hop paths, which raises cost on every trade and pushes flow toward whoever did the simpler thing.
The full sequence for getting listed, indexed and found is in our guide to listing a token on a DEX, and the pool sizing question is covered in low-slippage stablecoin pools.
What to check as a trader
Expand the route before confirming. A quote that beats every competitor usually does so by routing through something the others exclude, and that something is frequently a bridge or an unaudited venue.
Compare the amount received rather than the headline rate, since gas and bridge fees sit outside the quote. On a small trade a shorter, slightly worse route often nets more than an optimal one. The wider set of checks is in how to choose a reliable DEX.
What aggregators do not do
- Vet tokens. Inclusion in a route is not an endorsement and implies no review of the contract.
- Guarantee the quote. It is an estimate against pool state that changes before inclusion.
- Protect against front-running. Some offer private submission, most do not by default.
- Create liquidity. They find the best available route and cannot improve on what exists.
For projects, the practical consequence is that liquidity work and distribution work are the same project. Depth nobody can route to earns nothing, and a well-routed pool with no demand behind it earns very little either. How we run launch distribution across explorers and crypto media is on our crypto traffic acquisition page.