Liquidity providers supply the assets held in XSwap's pools. Routing connects an exchange between selected tokens to that liquidity. A token's appearance in the project directory identifies the asset; it doesn't establish the liquidity available for a particular trade.

XSwap's DEX volume measures spot token swaps over the reporting period. Pool liquidity concerns the assets available for exchange. A protocol-wide volume total can't establish the liquidity supporting one requested route.

XDC mainnet uses chain ID 50; Apothem testnet uses chain ID 51. XSwap lists separate contract deployments for these environments. An address needs its network context to identify the intended token or router deployment.

Open full-size image

The V3 mainnet contract list also names SwapRouter02 and V3SwapRouter . V2 mainnet and Apothem testnet routers have separate entries.

XSwap's ecosystem directory groups trading, analytics, and farming under V3 and marks the V2 ecosystem deprecated. The directory also specifies automatic launchpad liquidity addition only into V2 pairs. That integration doesn't establish that the same liquidity has been supplied to V3.

XSwap's Responsible Risk Disclosure Policy says displayed prices are indicative and may differ from executable or executed rates. Network latency can delay quotations or make trading unavailable.

Open full-size image

• For a mainnet trade, confirm XDC chain ID 50. Apothem chain ID 51 is testnet.
• For the selected assets, match token contracts and inspect the liquidity relevant to the pair.
• For a saved router or an older guide, identify its network and whether it concerns V3 or deprecated V2.
• Before confirming a swap, review the quoted rate and applicable interface fees, keeping the indicative-price limitation in mind.

Open full-size image