The DEX

Fully permissionless, for any token pair — whether or not either side ever passed through the launchpad. Nothing here depends on the launchpad, and nothing in the launchpad restricts what this allows.

Two pool types

V2 is a standard constant-product pool (the classic x*y=k model) — one fixed 0.30% fee, no configuration. Anyone can create a pool for any two tokens; the router creates it automatically on your first deposit if it doesn't already exist.

V3 is real, forked Uniswap v3 — concentrated liquidity, three fee tiers (0.05% / 0.30% / 1.00%), and a chosen price range instead of full-range-only. Full range earns fees at any price, like a V2 pool; a custom range concentrates capital for higher efficiency but earns nothing while price sits outside it.

Why both exist

V2 is simpler for a straightforward swap or a first liquidity position. V3 exists for anyone who wants concentrated capital efficiency, and it's also what every launch's own locked position uses internally (see How Launches Work) — a single-sided full-range position is just a V3 position with one side's deposit at zero.

Routing on /swap

• Checks both factories directly for a real on-chain pool, symmetrically — no assumptions based on whether a token happens to be a launch token.
• Prefers V2 if a pool exists there, since it needs no range management to swap against.
• Falls back to probing V3's three standard fee tiers otherwise, using the first one with a real pool.
• No multi-hop routing — only direct pairs. If no direct pool exists for your exact pair, the swap won't find a route.

This DEX is self-deployed, not a fork-of-a-fork pointed at someone else's pools

On every chain Openlaunch supports, the V3 infrastructure (factory, position manager, swap router, quoter) is genuinely deployed by this protocol — real, unmodified Uniswap v3 source, not a re-implementation. Pools here are not shared with, or dependent on, any other DEX deployment that might exist on the same chain.