XDEX has turned on swap aggregation. The core DEX of the X1 blockchain can now build a route across several liquidity pools at once and execute the whole thing as a single swap — a change that, on a chain where almost no two tokens share a pool, does more for tradability than any amount of new listings.

Jason, founder of XDEX and the Degen launchpad and part of the X1 Labs core dev team, announced it on Telegram today:

“XDEX can now route swaps across multiple liquidity sources on X1.

The new routing engine supports multi-hop and cross-DEX routing, automatically finding efficient paths between tokens.

A swap doesn’t have to happen through a single pool or even a single DEX.

XDEX can build the route and execute the steps as a single swap experience, finding the best available result across connected liquidity.”

The feature lives behind a new Multi tab on the XDEX swap interface, alongside the existing Swap, Limit and TWAP modes. Below is what we found when we read the chain rather than the announcement.

A new program, four days old

Routing is not a front-end trick. It is a separate on-chain program, muLikYso43cx27nE6izKLULNtkHPBNfyLuwNjEWhtXQ, deployed to X1 mainnet at slot 77,477,230 on 8 September at 17:06 UTC. The first routed swap landed 41 minutes later, at 17:47 UTC.

As of this morning the program has been touched 21 times — one deployment and 20 routed swaps, every one of them successful, with no failed transactions on record. That is a soft launch by any measure, and consistent with a team testing its own engine before pointing users at it.

The program exposes a single instruction, MultiHopSwap, and it holds its own upgrade authority (DwhWUT38Dwth5e1NYAJ2SSacYSaLEvct3kMndM7VSbcS) — a different key from the one that controls the XDEX AMM itself. Router and AMM are separately upgradeable.

Anatomy of the six-hop swap

An example transaction circulating in the community, 3we3DBy1…F7UMCT, is a good specimen. We pulled it from rpc.mainnet.x1.xyz and reconstructed it from the vault balance deltas. It is six hops:

MR. EGGPLANT → ANL → WXNT → UNO → TRUMP → X1FINITY → USDC.X

309 MR. EGGPLANT went in. 0.240126 USDC.X came out of the last pool, of which 0.238926 reached the trader. Six distinct XDEX pools were touched, each with its own SwapBaseInput call, and the intermediate tokens never sat in the wallet for longer than the transaction — every hop’s output became the next hop’s input inside the same instruction.

The whole route is a single instruction referencing 86 accounts, and it works across both of X1's token standards without the trader noticing either fact. What does have a practical limit is compute: the six-hop swap consumed 298,072 compute units, against roughly 82,000 for a single-hop routed swap. Each extra hop costs another 35–40k, so the six-hop ceiling is a real budget, not an arbitrary number.

Five associated token accounts had to be created for the intermediate mints before the swap could run. Net of the reclaimed rent and the priority fee, the trader was down about 0.0203 XNT on the transaction itself.

The routing engine is a public API

The quote logic runs off-chain. The swap page calls api.xdex.xyz/api/xdex/swap/multi-hop/quote with token_in, token_out, token_in_amount, venue, max_hops and network, then posts to a matching /prepare endpoint to get the transaction built. The endpoint is unauthenticated and answers anyone who asks.

Defaults are venue=all and max_hops=6. A quote comes back with the full path, per-hop pool addresses, per-hop reserves before and after, the pool fee rate on each leg, and both a gross and a net output figure. When no path exists the error names the engine’s pool snapshot: “No swap path found for this pair in the Metis snapshot.”

What it costs

Routed swaps carry a 0.5% router fee, taken from the output token and paid to a fee wallet, on top of each pool’s own trade fee. The quote API states it plainly as fee_bps: 50, and the on-chain transactions match: across the routed swaps we sampled, the fee wallet received exactly 0.500% of gross output every time.

This fee is specific to routing. We checked eight recent direct swaps against the XDEX AMM and none of them touched that wallet — the Swap tab is unaffected.

The pool fees stack on top. The pools in that six-hop route each charge 0.28%, which compounds to about 1.67% over six legs; add the router’s 0.5% and a maximum-length route costs roughly 2.2% before price impact. Long routes are a way to reach a token that was previously unreachable, not a way to trade it cheaply.

Why this matters more on X1 than it would elsewhere

We indexed the XDEX AMM to see how bad the fragmentation actually is. There are 1,252 pools spanning 725 distinct tokens — but only 1,189 unique token pairs. That is 0.45% of the 262,450 pairs those 725 tokens could theoretically form.

The distribution explains why. Wrapped XNT is the hub: 658 of the 725 tokens have a WXNT pool, and 450 tokens have exactly one pool, full stop. The median token on XDEX is connected to precisely one other token.

Allow three hops and that inverts. Sampling across the pool graph, the average token can reach 717 of the other 724 within three hops. Routing does not add liquidity — it makes the liquidity that already exists reachable, and on X1 that is the difference between 0.45% pair coverage and roughly 99%.

The engine’s own quotes show the size of the effect. Asking for 1 USDC.X of MR. EGGPLANT, the direct pool returns about 2,002 tokens; the three-hop route through WXNT and ANL returns 26,490 — thirteen times more. At 50 USDC.X the direct pool is simply exhausted and returns 2,159 tokens for fifty dollars, while the route returns 1.28 million. The direct pool exists; it just has nothing in it.

“Cross-DEX” — what is wired, and what is not yet

The cross-DEX half of the claim is real in the code but not yet visible in the transactions. The quote API accepts a venue parameter, and the swap UI badges every hop with the venue it uses, drawing either the XDEX mark or the Degen mark and labelling it “XDEX pool” or “Degen pool”. So the second venue currently wired in is the Degen launchpad — also Jason’s.

Every route we saw, both in the 20 on-chain swaps and in our own quote probes, resolved entirely to XDEX pools. That is not surprising four days in, and it says nothing about whether other venues follow. It does mean that today, “cross-DEX” describes the architecture rather than the traffic.

XDEX is not the first aggregator on X1 — RipperSwap shipped multi-hop aggregation in July. The difference is where it sits. Routing built into the chain’s core DEX becomes the default path for every trader who never leaves the main swap page, and it is the venue that other front ends will quote against.

How to use it

Open app.xdex.xyz/swap and connect a wallet on X1 Mainnet. On desktop, use the X1 Wallet browser extension; on mobile, Backpack is the practical choice. Then select the Multi tab next to Swap, Limit and TWAP. Pick the input and output tokens and the interface will fetch a route, show each hop with its venue badge, and submit the whole path as one transaction.

Two things to keep in mind. Long routes create associated token accounts for each intermediate mint, so keep a little XNT spare for rent. And the 0.5% router fee applies to Multi swaps only — if a direct pool has enough depth for your size, the plain Swap tab is still cheaper.

Traded through the Multi tab? Tell everyone whether it held up — you can rate or spank XDEX on our reviews page.

All on-chain figures in this article were read directly from X1 mainnet via rpc.mainnet.x1.xyz and from XDEX’s public quote API on 10 September 2026. Pool graph statistics come from X1 Report’s own index of the XDEX AMM program.