Arc Liquidity Pool Creator

Setting the opening price deliberately

A pool has no price to negotiate with. Its price is the ratio of the two reserves, so the two numbers in the form above are the price, and everything trades from there until volume or arbitrage moves it. Two levers decide it: how much USDC you deposit and how many tokens you deposit. Both are public afterwards, so change them one at a time and read the preview each time.

The fully diluted valuation is the same arithmetic run over the entire supply: FDV = pool USDC ÷ share of supply placed in the pool. A token with a 1,000,000,000 supply, seeded with 500,000,000 tokens and 8,000 USDC, opens at 0.000016 USDC per token and an FDV of 16,000 USDC. The same 500,000,000 tokens against 40,000 USDC opens at 0.00008 and an FDV of 80,000 — depth and valuation are the same decision made twice.

Depth decides how violently ordinary trades move that price. On a constant-product pool a buy of size B against a USDC reserve of R moves the price by roughly B ÷ (R + B) before fees: a 1,000 USDC buy moves a 10,000 USDC pool about 9.1% and a 50,000 USDC pool about 2%. A shallow pool is not a cheap pool — it is a pool that prints alarming candles on trivial volume. For a small-cap launch, 5,000 to 10,000 USDC of depth is the practical floor.

Where the LP tokens go, and why it matters

Whoever holds the LP tokens can remove the liquidity. Until the market knows who that is, a launch is discounted by default, because draining the pool is the most common way a token holder gets hurt. There are three answers, and this tool supports all three:

• Keep them. Maximum flexibility, minimum credibility. Entirely reasonable for an established project, and the default assumption buyers make is that an unlocked pool can be pulled at any moment.
• Lock them. The LP tokens sit in the Arctools Liquidity Locker until an unlock timestamp anyone can read from the contract. There is no owner override and no early exit, and fees keep accruing to the position while it is locked.
• Burn them. The strongest commitment, and permanent: the liquidity can never be withdrawn by anyone, including you. Burning also gives up the ability to migrate the pool or recover the capital, so make that decision once, deliberately.

Locking and burning both happen after the pool exists, because the LP tokens do not exist until the pair is seeded. That is why they are follow-up transactions rather than checkboxes inside this one: the tool leaves the LP in your wallet and hands you to the locker with the pool pre-filled.

How Arc's two USDC interfaces are handled here

USDC on Arc is one balance with two views of it. The native view has 18 decimals and is what pays gas and travels as msg.value. The ERC-20 view at 0x3600000000000000000000000000000000000000 has 6 decimals and is what a Uniswap pair, an allowance and a transferFrom understand.

Pool math is done in ERC-20 units — 6 decimals — because that is the unit the pair's reserves are denominated in. The capital travels as native value, so this page converts once at the boundary: the USDC leg is sent as amount6 × 10¹², the same quantity of money in the 18-decimal form. The manager divides it back down and reverts rather than truncating if a value cannot be converted exactly, which is also why the form insists on whole USDC: it keeps every figure on the page exact.

Two consequences worth internalising. First, USDC is never paired against USDC — that would be an asset trading against itself, and the manager rejects its own USDC address as an invalid token. Second, there is no wrapped USDC on Arc and no addLiquidityETH path: the router is always called with two ERC-20 addresses, one of which is USDC.