KyberSwap liquidity-source controls: when to change them

KyberSwap source controls let you narrow the venues considered for routing. They are useful when you have a specific reason to avoid or isolate a source, but a narrower search can reduce available liquidity or remove the only eligible route.

The network and exchange documentation says traders can customize considered DEXs in the interface. The API specification also exposes source filters and restrictions such as direct-pool or single-path selection.

Change one condition at a time

Start with a quote for the exact assets and amount, note the settings, then change the intended source restriction. Compare the new route and outcome. Changing the amount, slippage and source set together makes it difficult to know which choice caused the difference.

There are legitimate reasons to filter: investigating an unexpected route, applying a documented institutional allowlist or avoiding a source affected by an incident. “Fewer logos looks safer” is not a meaningful analysis of the contracts involved.

A route restriction is not a guarantee

Excluding one exchange does not remove token risk, wallet authorization risk or every other contract dependency. Likewise, requesting a direct route does not ensure a lower total cost. The price and depth of the available pool still matter.

If no route remains, inspect the active restrictions before concluding that the token is impossible to trade. A route can disappear because the application has deliberately disallowed the intermediate assets or sources it would require.

Record the policy with the quote

For a comparison, save both the requested filters and the returned route. Two screenshots with different hidden source settings are not a controlled test of provider quality. For repeated use, revisit an old exclusion when its original reason changes; a forgotten setting can silently constrain later trades.