Help us improve Dexfy

Optional cookies help us understand how Dexfy is used and improve the product. Learn more

All updates
Product5 min readPublished

Dexfy expands DEX route coverage and version transparency

Flap join Dexfy’s generated DEX matrix, with the current protocol versions and configured chain mappings published from shared metadata.

Release summary

Dexfy’s current shared registry now exposes 9 DEX integrations and 19 DEX/version adapters in one generated matrix. The August release adds Flap coverage and makes the complete current adapter/version inventory visible. A listed adapter means implemented route metadata exists for its configured chain; it does not guarantee liquidity, a quote, continuous protocol availability, or support for every token pair.

Release questions answered

  • Which DEX routes did Dexfy add?
  • Why do adapter versions matter?
  • Does listed DEX support guarantee a live route?

What changed

Dexfy now generates the public DEX table from the same shared registry consumed by the product and execution code. Flap Portal coverage is configured on BNB Smart Chain.

The current version inventory is: PancakeSwap V2/V3/Infinity; SushiSwap V3; Uniswap V2/V3/V4; Raydium CPMM/CLMM/LaunchLab; Orca Whirlpools; Meteora DLMM/DAMM v2/DBC; Pump.fun Bonding Curve/PumpSwap; Flap Portal; Four.meme TokenManager V1/TokenManager V2.

Why version-level coverage matters

A DEX brand can expose multiple router, factory, pool, or program generations. Quotes, pool discovery, approvals, risk probes, and transaction construction depend on the exact configured version and chain—not only the protocol name.

Publishing the version matrix makes the boundary inspectable and reduces the risk of treating one supported version as universal support for every route under the same DEX brand.

What the matrix does not promise

The registry does not measure liquidity, token behavior, uptime, quote quality, price, or execution success. A route can be implemented and still be unavailable for a particular token pair, pool, protection requirement, provider condition, or moment in time.

  • Check the exact DEX version in the live product.
  • Verify the token pair, pool, quote, liquidity, fees, and enabled protections.
  • Treat a missing or unavailable required route as a stop condition.

Related guides and evidence

Use the evergreen guides and current integration evidence before enabling the released capability.

Supported chains, routes, fees, and limitationsUnderstand what a listed integration means and why live availability can still differ.Execution coverage researchSee the reproducible chain-by-chain route snapshot and its explicit limitations.

Sources and release evidence

Configure only after checking the live route

The dashboard is the final source for current pair, route, liquidity, quote, and protection availability.

Launch Dexfy