Frequently asked questions

TangoSwap is a production-ready Uniswap V3 fork: a marketing site, a swap + liquidity DEX UI, and a self-hosted indexer/API. It is built to deploy on any EVM-compatible chain.

No. It forks Uniswap V3 (core + periphery as upstream submodules), adds WETH9 and deploy tooling, and ships the frontend/backend kit. Do not market it as a novel AMM beyond V3.

1) Traders using a deployed instance. 2) Chain/ops teams who need a turnkey DEX + site. 3) Teams combining a DEX with a meme + launchpad kit for new-chain launches.

WalletConnect Project ID, deployer private key (with gas), target RPC URL, production domain, and socials/email in site config. See the operator checklist on the landing page.

The kit is redeploy-ready for EVM chains such as Ethereum, Polygon, Arbitrum, Optimism, Base, and new EVMs you configure. That is a capability, not proof that a public TangoSwap brand is already live with TVL on each. Wire each chain via deploy JSON + chains.ts + env. A Sepolia deployment artifact exists in the kit.

Set PRIVATE_KEY and RPC_URL, run the Foundry Deploy.s.sol script with broadcast, then register addresses from deployments/{chainId}.json in frontend and backend config.

Optional for basic UI; recommended for quotes/prices/positions UX. Run the Hono + Viem backend and set NEXT_PUBLIC_API_URL.

Yes. You connect a wallet and sign. The interface does not hold your keys or custody balances.

Uniswap V3 concentrated liquidity: fee tiers, price ranges, position NFTs via the periphery Position Manager — same mental model as Uniswap V3.

Approved phrasing: Built on audited Uniswap V3 contracts when using unmodified upstream v3-core / v3-periphery. Upstream Uniswap V3 has published audit materials; that is not the same as a separate, TangoSwap-commissioned product audit or score. Do not say “TangoSwap audited” or invent a score.

Upstream: V3 core and periphery submodules. Kit-custom called out in product docs: WETH9 plus deploy scripts, frontend, and indexer. Review before mainnet.

Only from real deployment analytics the operator owns. Invented metrics are forbidden.

Use the Contact page channels configured by the operator. Placeholder socials in templates are not verified official accounts until replaced. Email is preferred until socials are set.