A pool can exist onchain without being available through a particular aggregator. Permissionless deployment concerns who can create or interact with protocol objects; aggregator support concerns which objects the service can discover, model and execute through.
Several steps separate existence from a quote
- The pool must exist on the relevant network.
- The service must discover or index it.
- The router must understand its pricing and token behavior.
- The execution system must support its settlement interface.
- The pool must be eligible and useful for the requested trade.
Failure at one of these stages can remove the pool from the result without implying that the onchain pool disappeared.
Uniswap's routing repository documents provider and pool-selection components. Its configuration shows that candidate selection is an explicit part of route construction.
Supported does not mean selected
A service can fully integrate a pool and still choose another route because the first pool offers weaker terms for the amount. Conversely, a pool visible in a block explorer can be absent because the required adapter or indexing coverage is missing.
These are different explanations. The absence of a venue from one route does not establish an integration gap; the absence of every quote using it may still need more evidence.
A token list is another separate layer
A front end can list a token for selection without guaranteeing liquidity for every trade direction or size. A router can also technically understand a token while the interface chooses not to expose it in a default list.
When a token or pool seems missing, formulate the question precisely: missing from the selector, missing from supported sources, missing from indexing, or simply not selected for this request?
That vocabulary helps distinguish interface discovery from execution capability. It also avoids treating permissionless infrastructure as a promise that every third-party service supports every object deployed on it.
Sources & verification (3)
Source-check date is recorded in the article details. URLs are provided for manual verification. Use Copy to keep this page open.
- Uniswap Smart Order Router
Routing searches consider split paths and gas costs.
https://github.com/Uniswap/smart-order-router - Uniswap smart-order-router: alpha-router.ts
Candidate-pool selection and configurable hop and split limits.
https://github.com/Uniswap/smart-order-router/blob/main/src/routers/alpha-router/alpha-router.ts - What is 0x?
Aggregation includes onchain and offchain liquidity, and interfaces can embed an aggregation service.
https://docs.0x.org/docs/core-concepts/introduction-to-0x