Add Liquidity to an Existing Pool on Arbitrum
Deposit into a Uniswap pool that is already trading on Arbitrum One, on v2, v3 or v4. Already own a position there? The money lands in that one instead of buying you another NFT to look after. Put in one figure and the pool works out the rest. 0.002 ETH.
0.002 ETH service fee plus network gas
How to Add Liquidity on Arbitrum
Point it at the pool
A token address brings back the Uniswap markets trading that token on Arbitrum, listed by version and tier. A pool address goes straight there. Positions your wallet already holds are shown at the same time.
Choose the position, not just the pool
Selecting a position you own deposits into that one and leaves its bounds alone. Choosing the pool by itself mints a separate position, which is what you want only if you have changed your mind about the range.
Fill in one side
Enter either token and its counterpart is derived from the current price, plus, on a concentrated position, from how far that price sits from each of your bounds. Nothing beyond what the ratio calls for is taken.
Approve with a signature where you can
A token implementing permit makes its allowance free to grant, and Permit2 reaches a good share of those that do not implement it. Paid approvals are reserved for tokens supporting neither, and the form flags that before you get there.
Read the dry run and confirm
Your exact deposit runs against Arbitrum as it currently stands, so the figures on screen are the figures that move. Blocks land roughly every quarter second here, which leaves the ratio little room to drift between quote and confirmation.
No Code Required
Create and launch tokens without writing any code. Visual configuration for all features.
Fully Transparent
All token data is publicly visible and verifiable on block explorers.
Multi-Chain
Available on Solana, Ethereum, Base, Arbitrum, Polygon, and BNB Chain.
Full Ownership
You have full control. We never hold your keys, tokens, or authority.
Frequently Asked Questions
One Deposit in Three Goes Into a Position That Already Exists
Almost every guide to providing liquidity teaches the first deposit, because that is the interesting one to write about. The behaviour on Arbitrum tells a different story. Counting real Uniswap liquidity additions on the chain, roughly a third of them go into positions that already exist rather than opening new ones, and on v4 the share is higher still. That is a very large group of liquidity providers to have essentially no third-party tooling for, and every one of them is watching trading fees accrue against a position they cannot easily feed.
The reason it matters is that the two operations are not interchangeable. Rival services issue a brand-new position NFT for every single deposit, the range you asked for being irrelevant to that, and not one of them discloses it. Three deposits therefore leave you holding three positions in place of one, each carrying its own fee balance to sweep, its own closing transaction and its own gas bill on the way out. The measured cost points the same direction: about 235,000 gas to increase something that exists, against roughly 449,000 to write a position and its ticks from nothing.
So the useful question on returning to a pool is not how much to put in but what to put it into. Where those bounds still match your reading of the market, deposit into the thing you already own. Where they no longer do, no amount of topping up will say so, and minting something separate is the honest answer.
The Block Number Your Token Sees Is Not Arbitrum's
This one is genuinely peculiar to Arbitrum and it produces failures that look like the tool is broken. A contract running on Arbitrum that asks for the current block number does not get Arbitrum's. It gets Ethereum's, which sits around half a billion blocks behind, and it advances at Ethereum's pace of roughly twelve seconds rather than Arbitrum's quarter of a second.
That is harmless until a token uses block counts for launch protection, which is extremely common. A contract that pauses transfers or caps wallet sizes for the first few blocks after deployment is, on Arbitrum, counting Ethereum blocks. A restriction the deployer expected to lift in well under a minute is still enforcing itself hours later, and every attempt to deposit into the pool reverts against it. Nothing is wrong with the pool, the deposit or the wallet.
Uniswap's own contracts sidestep this because they gate on timestamps rather than block heights, so the protocol is unaffected. The token is what turns you away. If a brand-new token refuses your deposit for no visible reason, this is the first thing worth checking, and the answer is usually to wait rather than to change anything.
On v4 the Fee Is Whatever the Pool Decided
Uniswap v3 on Arbitrum offers four fee tiers and only four: 0.01%, 0.05%, 0.30% and 1.00%. The set has not changed since the 0.01% tier was added by governance in early 2023, and it matches Ethereum mainnet exactly. Where new pools land has shifted sharply though. Across a recent week of new v3 pools on Arbitrum, the overwhelming majority opened on the 1.00% tier, which is the tier tokens with real volatility use, rather than spreading across the four the way early Arbitrum did.
Uniswap v4 abandoned the fixed list altogether. A v4 pool carries whatever fee its creator chose when opening it, and in a recent week of Arbitrum v4 pools that meant dozens of distinct values scattered anywhere from nothing at all to almost the entire trade. A meaningful share of them use a fee that changes as the pool runs rather than a fixed one, and a quarter hold native ETH directly with no wrapping involved. So on v4 there is no correct tier to pick, only the one the pool already has, which the tool reads for you rather than asking.