Uni swap is a First LP Position Workflow From Pool Choice to Manual Exit

v4 Makes Pool Configuration Part of the First Decision

v4 pool configuration is a visible first-position decision: the same token pair supports multiple pools with different fee settings, tick spacing, and optional hooks, while each position defines its own range. A position belongs to one exact pool, not merely a pair. v3 offers four established tiers, while v4 also permits other fee settings and hook-enabled pools. A hook changes pool behavior and becomes part of the market identity. For a first position, an existing pool without a hook keeps later verification focused on the pair, range, and deposit.

Wallet and Network Preparation Before Pool Creation

Wallet preparation for a first LP position requires the deposit tokens, the network's gas token, a connected web-app wallet, and enough balance for approval and creation transactions.

Network identity matters because equal tickers on separate chains represent separate balances and separate pools. Ethereum uses chain ID 1, Base uses 8453, Arbitrum One uses 42161, Optimism uses 10, and Unichain uses 130. Keep those identifiers ungrouped because each number names a network. ETH pays network costs on all five of those deployments. The deposit itself uses assets already present on the selected chain; a balance on Ethereum does not fund a Base position. The mobile wallet app connects to the web app, but position creation and the full LP view live in the web interface.

Token Pair and Pool Selection as One Market Choice

Token-pair selection identifies the assets, while pool selection fixes the exact contract state the new position will join and determines how its range is interpreted.

In v3, pool identity starts with two ordered token addresses and one fee tier. v3 exposes four standard fee tiers for each token pair: 0.01%, 0.05%, 0.3%, and 1%. Each tier points to a separate pool for the same pair, so WETH/USDC at 0.05% is distinct from WETH/USDC at 0.3%. v4 expands the PoolKey to five fields: currency0, currency1, fee, tick spacing, and hook address. Select the existing pool whose token contract addresses match the intended assets, then note its version and settings before continuing. The Explore view helps distinguish established activity, while the contract addresses establish asset identity.

Pool creation is a different action from joining an existing pool. A first LP workflow stays easier to verify when the chosen pool already has an initialized price.

Price Range Entry and Tick Rounding

Price-range entry sets two boundaries for concentrated liquidity, and the interface converts those displayed prices into usable ticks before the wallet receives a creation request.

Custom Range Mechanics

A custom range places liquidity between a lower tick and an upper tick. Every tick advances the token1-to-token0 price ratio by a factor of 1.0001, equivalent to about 0.01% for one step. v3 supports tick indexes from −887272 through 887272, while each pool's tick spacing limits which indexes initialize. The interface therefore rounds a typed boundary to the nearest permitted price. Review the rounded values, because those onchain boundaries govern the position.

Lower Bound

The lower bound marks where the position reaches one edge of active liquidity. Record the rounded price shown in the review.

Upper Bound

The upper bound marks the opposite edge. A current price between both bounds makes the deposit in range and requires both pool tokens.

Full Range Mechanics

Full range sets the conceptual price span from 0 to infinity. It removes the need to choose finite endpoints, yet the position still belongs to one pool and retains that pool's tick spacing. The interface maps the selection to the widest usable ticks. A custom range concentrates the same capital over fewer price intervals, so range choice remains the main maintenance commitment.

Deposit Sizing and Token Composition

Deposit sizing follows the selected range and current pool price, so the preview calculates the two token quantities required for the requested amount of liquidity.

An in-range WETH/USDC position draws from both assets. An out-of-range v3 or v4 position is single-sided and accepts only the token on the applicable side of the range. Token precision still matters: native USDC uses 6 decimal places, while WETH uses 18. Those decimal settings affect smallest representable units, not the economic ratio. Enter one amount, inspect the paired amount the interface computes, and keep enough ETH outside the deposit to pay network costs.

The Max control targets the available token balance. For a first position, a smaller deliberate amount leaves room to verify the NFT, observe composition, and perform a later manual exit.

How Do You Confirm a New LP Position?

A new LP position is confirmed by reviewing the pool details, authorizing token movement when required, signing the requested message, and approving the creation transaction in the wallet.

For a fresh v4 ERC-20 path with no existing allowance, the wallet flow contains three distinct actions: one onchain token approval, one Permit2 signature, and one onchain creation transaction. The Permit2 signature has zero network cost because it is not itself a transaction. The two onchain actions consume gas. If a sufficient allowance already exists, the approval step is omitted. v3 creation likewise separates token authorization from the position mint when authorization is needed.

Before signing, compare the wallet's network, token addresses, selected version, fee tier, and rounded range with the review screen. The creation transaction should name the same account holding the deposit assets. After submission, wait for confirmed status instead of treating the wallet's sent state as final settlement.

Reading the Position After Confirmation

The position details screen verifies a successful LP creation by showing the deposited token amounts, ownership record, selected range, current pool price, and position status. Its 11 numbered values are grouped into three blocks: four liquidity values, four uncollected fee values, and three price values. v3 and v4 also mint an ERC-721 NFT to the connected address, providing the ownership record for adding or removing liquidity. Confirm the wallet address, network, token pair, lower price, upper price, and NFT before considering the setup complete.

Range Maintenance Requires Removal and Re-Creation

Range maintenance for v3 and v4 positions uses two separate operations because existing lower and upper ticks cannot be edited after the NFT is minted.

When the pool price crosses either boundary, the position becomes out of range and single-sided. It holds one token and stops participating in swaps until the price returns. Leaving it untouched preserves the original boundaries. Moving the range requires removing liquidity from the old position, choosing new rounded endpoints, and creating a replacement position. That sequence introduces new wallet confirmations and network costs, so maintenance should follow a written trigger rather than an accidental interface visit.

Record the current token composition before removing anything. The exit returns those current tokens, not the original deposit ratio, because swaps inside the range changed the position while it was active. The next decision is whether to wait, withdraw partially, or rebuild the range.

Partial Withdrawal as a Controlled Test Exit

Partial withdrawal removes a chosen percentage of active liquidity, returns the corresponding current token amounts, and leaves the remaining share attached to the same position.

Open Pool, select the NFT-backed position, choose Remove Liquidity, enter a percentage below 100%, and review both outputs. The removal transaction requires the wallet owner to confirm an onchain action. After settlement, compare the remaining liquidity and token balances with the displayed transaction record.

In this worked example, every changing input is hypothetical: the position currently holds 0.30 WETH and 750 USDC, has zero uncollected fees, executes at an unchanged pool price, and removes 60% of its liquidity. Ignoring token-unit rounding, the withdrawal returns 0.18 WETH and 450 USDC. The remaining 40% retains 0.12 WETH and 300 USDC at that execution snapshot in the same range. This calculation scales each current token amount by 0.60; it does not reconstruct the original deposit. This case leaves a position with 40% active liquidity remaining.

The remaining 40% now becomes the next maintenance decision: keep it, re-range it, or remove it fully.

Full Removal and a Clean Manual Exit

Full removal closes the LP position by selecting 100%, confirming the withdrawal, and verifying the returned tokens and closed status after the transaction settles.

For v3 or v4, open the position, choose Remove Liquidity, enter 100%, review the token outputs, and confirm the onchain removal. If ETH is part of the pool, the interface offers Collect as WETH; this keeps the returned asset in ERC-20 form. Once settled, the wallet receives the current token balances plus collected amounts, and the position holds zero active liquidity.

After a standard manual removal, the NFT remains in the wallet as the position record. Its presence does not mean liquidity is still deployed; the detail view should show the position as closed. Save the transaction hash, confirm both token balances, and decide separately whether any token allowance should remain. Uni swap is fully exited only when the position shows no liquidity and the intended assets are back under the wallet address.