Arc x Uniswap🦄 Swap and liquidity infrastructure for Arc
# AMM
# DEX
# liquidity
# swaps
# developer tools
Uniswap is coming to Arc, bringing builders a leading DeFi layer for swaps, liquidity, token discovery, and composable market infrastructure.
Tim Baker
Uniswap is coming to Arc Mainnet.
Why this matters
Most financial applications do not exist in isolation.
A wallet needs a clean path for users to move between assets. A payments app may need conversion before checkout or settlement. A treasury product may need to rebalance between stablecoins or other tokenized assets. A lending or trading protocol may need swap execution inside the product flow. A new asset issuer needs a place where users can discover and trade the asset.
Uniswap is a leading DeFi primitive for those paths with $4.4T in all-time volume.
What builders can do with this
For app teams, the first use case is straightforward: add swaps where the product already needs asset conversion.
That could mean:
Wallets routing users between Arc assets
Payment apps converting into the asset needed for settlement
Treasury tools rebalancing stablecoin or tokenized asset positions
DeFi protocols executing swaps inside vault, lending, or collateral flows
Trading tools indexing pools, quotes, routes, liquidity, and LP positions
Asset issuers giving users a clearer path to trade new Arc assets
For market makers and liquidity providers, Uniswap provides an established venue to evaluate Arc pairs, provide liquidity, and build tooling around pool behavior.
For protocol developers, the value is composability. Instead of treating swap execution as a separate destination, teams can build it directly into the product path.
Integration paths
Uniswap’s public developer docs outline a few different integration models, depending on how much control the application needs.
The lighter path is to send users into a pre-filled swap flow. That works when the app does not need to own quoting, routing, or transaction construction.
A more integrated path uses Uniswap API or SDK flows, where the app can request quotes, construct transactions, or compute routing locally depending on the implementation.
For protocol-level work, teams can integrate directly with router or pool contracts. That is the path for apps that need swaps inside smart contract logic, vault strategies, arbitrage systems, or other DeFi flows where the full lifecycle needs to happen onchain.
Uniswap v4 also introduces hooks, which let developers add custom logic around pool lifecycle events. That opens up more advanced design space for teams building market structure, dynamic fees, access-controlled pools, custom settlement behavior, or app-specific liquidity logic.
A good first build
A good first build is not a generic “Uniswap integration.” It is an Arc app where asset conversion is already part of the product.
Examples:
A payments app that lets a user pay from one supported asset and settle in another
A treasury dashboard that routes rebalances through Arc liquidity
A wallet flow that makes swaps feel native instead of sending users somewhere else
A stablecoin or FX app that uses pool liquidity as part of the transaction path
A tokenized asset product that wants secondary trading without building its own exchange surface
Start here
Uniswap coming to Arc Mainnet gives builders a practical DeFi layer to plan around: swaps, liquidity, routing, LP workflows, and composable market infrastructure.
