Why two aggregators may return the same route

Two aggregators can return the same route because they access the same public liquidity and solve a similar optimization problem. Matching pool names are not evidence, by themselves, that one copied the other or that the services are identical.

One market can serve many interfaces

Public pool contracts can be accessed through multiple applications. If one hypothetical A/B pool has the strongest executable terms for a given amount, several independent routers may choose it.

An application can also embed an external quote provider. 0x describes this application-and-provider relationship. Shared underlying services are therefore another possible explanation, but the route alone does not prove that relationship.

The same pools do not guarantee the same trade

Compare allocation, trade size, mode, quote state and surrounding charges. Two plans can name the same venues while assigning different portions or applying different user constraints.

A route summary may also omit operational differences such as how the transaction is submitted or which settlement wrapper is used. Conversely, different-looking diagrams can summarize equivalent execution in different formats.

What matching routes establish

At most, they establish that the displayed plans overlap in their identified sources. To determine common infrastructure, use provider disclosures or integration documentation. To determine equivalent execution terms, compare the complete quote fields.

Uniswap's public router code illustrates that route search can itself be open and reusable. A shared algorithm or codebase is another distinct fact from using the same pool.

For evaluation, preserve these distinctions: common venue, common quote provider, common software and common settlement contract. They can coincide, but none logically proves all the others. This prevents unsupported claims about ownership while keeping the comparison focused on what the actual offer shows.