Curveswap is a Pool Selection, LP Deposit And Position Exit Workflow

Wrong Pool Selection Creates The Wrong Position

The wrong pool selection creates exposure to assets or wrappers that the depositor did not intend to hold. Curveswap selection starts with the exact pool contract, not a familiar-looking symbol.

A pool page names its top-level coins, yet a metapool can place a base-pool LP token among those entries. The 3CRV token, for example, represents the 3pool containing DAI, USDC and USDT. A metapool that holds 3CRV therefore carries underlying exposure beyond its short top-level pair. The same distinction applies to native ETH, WETH and liquid-staking assets such as stETH: each contract has different transfer and accounting behavior. Match every deposit field to the intended asset contract before entering an amount, then read the withdrawal choices for that exact pool.

Pool construction also sets the expected relationship among assets. StableSwap pools serve correlated values, while CryptoSwap pools serve assets whose prices move independently. Choosing between them determines the position that the LP token represents.

Network And Wallet Prerequisites Set The Transaction Path

The selected network decides which pool, token contracts and wallet balances Curveswap can use for a deposit. A wallet connected elsewhere sees a different contract state.

Ethereum uses chain ID 1, Optimism uses 10, Base uses 8453 and Arbitrum uses 42161. These fixed identifiers let MetaMask or Rabby confirm the signing network before an approval. The wallet needs the pool assets on that same chain and enough of the chain's native currency for each state-changing action. An Ethereum position remains on Ethereum, while an Arbitrum position remains on Arbitrum. Returning to the original chain restores the matching pool, token and balance view.

StableSwap, Twocrypto And Tricrypto Define The Deposit Shape

The pool implementation determines how many deposit fields appear and how Curve interprets their balances. Pool type therefore comes before amount entry.

StableSwap-NG For Correlated Assets

StableSwap-NG plain pools contain at least 2 coins and at most 8 coins. Its asset-type codes cover 4 cases: 0 for standard ERC-20, 1 for an oracle-rated token, 2 for a rebasing token and 3 for an ERC-4626 vault token. Supported token precision reaches 18 decimals, while rate-oracle precision uses 10 ¹⁸ .

Twocrypto-NG For Two Volatile Assets

Twocrypto-NG fixes the pool at 2 coins and integrates the ERC-20 LP token into the pool contract. A CRV/WETH market therefore presents two deposit amounts whose relative values follow the CryptoSwap invariant.

Tricrypto-NG For Three Volatile Assets

Tricrypto-NG fixes the pool at 3 coins and supports the familiar volatile-asset basket shape, such as a USD asset with WETH and WBTC. Depositing one constituent still mints a claim on the full three-asset pool. The deposit screen therefore contains 3 amount fields, even when only one carries a nonzero amount.

How Do You Deposit Into A Curveswap Pool?

An ERC-20 allowance decides whether a single-asset Curveswap deposit needs one wallet signature or two. The deposit itself calls the pool's liquidity function and mints LP units.

Approval Before Deposit

An input token without sufficient allowance needs 1 approval transaction before the deposit transaction. Each token maintains its own allowance for a particular spender on a particular chain. If the allowance already covers the entered amount, the interface moves directly to deposit confirmation. Changing the deposit asset changes the allowance check.

Deposit And Stake As One Action

The Curve interface exposes Deposit and Deposit & Stake as separate modes. Deposit leaves minted LP tokens under the wallet address. Deposit & Stake combines the pool deposit and gauge placement into 1 transaction after required approvals. The second mode changes where the resulting position appears, so record the selected mode before signing.

The Mint Preview Sets The Acceptance Floor

The minimum-mint field determines whether the pool accepts the final LP-token output. Curveswap should show that floor before the wallet submits the deposit.

The pool calculates expected LP units from the entered amounts, current pool balances, token rates, invariant and total LP supply. Its add_liquidity call receives the amounts and a min_mint_amount. Execution continues only when the calculated mint meets or exceeds that minimum; otherwise, the transaction reverts without creating the position. A minimum of 0 supplies no output floor. StableSwap-NG expresses the LP result with 18-decimal precision, so the interface converts the contract integer into readable units before presenting the confirmation. The encoded floor applies to that one submitted transaction and nothing later.

Read the expected LP amount again after changing any deposit field. A one-asset contribution and a proportional multi-asset contribution produce different mint previews because each one changes pool balances differently.

LP Token Receipt Confirms Pool Ownership

The LP token receipt confirms ownership only when its pool address and holding location match the submitted deposit. A success banner alone lacks those details.

StableSwap-NG pool LP tokens use 18 decimal places and expose an ERC-20 balanceOf value. The same contract also exposes totalSupply, which supplies the denominator for ownership calculations. A successful deposit emits 2 relevant event types, Transfer and AddLiquidity. On EVM chains, a contract address contains 20 bytes and displays 40 hexadecimal characters after 0x; a transaction hash contains 32 bytes and displays 64 hexadecimal characters. MetaRegistry maps a Curve LP token back to its pool, while Etherscan shows the receipt and event log on Ethereum. On other EVM chains, use that chain's explorer for the same receipt fields.

A Worked Share Calculation Turns LP Units Into Ownership

The LP ownership fraction equals wallet LP balance divided by total LP supply, then multiplied by 100. Token decimals cancel when both values use the same scale.

In this worked example, every changing input is hypothetical: a wallet holds 125 LP tokens, total supply equals 25,000 LP tokens and the two-coin pool holds 2,000,000 units of asset A plus 1,000,000 units of asset B. The calculation is 125 divided by 25,000, or 0.005; multiplying by 100 gives a 0.5% pool share. A proportional exit at that state corresponds to 10,000 units of asset A and 5,000 units of asset B.

The percentage describes ownership of the pool's live balances, not a fixed quantity of either asset. Swaps and later liquidity changes alter those balances while the LP fraction follows the holder's units relative to total supply.

Direct Holdings And Gauge Stakes Change Where The Position Appears

The custody location of LP tokens determines where Curveswap displays the position and which action comes before withdrawal. Direct tokens and gauge deposits use separate balances.

A plain deposit credits the wallet's LP-token balanceOf. Deposit & Stake sends the resulting LP units into the pool's Curve gauge, which records the depositor's gauge balance instead. MetaMask or Rabby might omit an unfamiliar LP token from the default asset list, yet the contract balance remains readable. The pool's Your Details view should identify the deposit and whether it is staked. CRV rewards, when a gauge offers them, sit beside this record; they do not replace the LP units that measure the withdrawal claim. The correct balance location follows the mode selected at deposit.

Balanced, One-Coin And Custom Exit Modes Burn Different Amounts

The withdrawal mode decides whether burned LP tokens return the current pool mix, one selected asset or requested custom amounts. Start from the desired final assets.

Balanced Withdrawal Preserves The Pool Ratio

The Curve interface presents 3 withdrawal shapes: balanced, one coin and custom. Balanced withdrawal burns the chosen LP amount and returns every constituent in the pool's current ratio. For directly held LP tokens, that exit settles in 1 withdrawal transaction.

One-Coin Withdrawal Selects One Output

One-coin withdrawal burns LP tokens and returns 1 selected pool asset. The contract identifies coins with zero-based indices beginning at 0, although the interface shows symbols. Its quote incorporates the internal conversion required to concentrate the claim into that asset. Select the output contract first, then compare the quoted quantity with the wallet's expected receiving asset.

Custom Withdrawal Targets Specific Amounts

Custom withdrawal requests chosen quantities and enforces a maximum LP-token burn. The contract uses the requested asset amounts to calculate the actual burn, then rejects execution above that maximum. This mode fits an exit whose final asset ratio differs from the pool ratio. It provides granular output control, while the maximum-burn value serves as the transaction's acceptance boundary.

Final-State Checks Close The Position Cleanly

Final-state checks compare wallet balances, gauge balances and receipt events before Curveswap treats the position as closed. A full exit clears both LP locations.

A staked position requires 2 separate state changes in the standard interface: unstake first and withdraw second. After a full withdrawal, the relevant wallet LP balance should read 0, the gauge deposit should read 0 and the selected underlying balances should reflect the confirmed output. The withdrawal receipt records the LP burn and outgoing asset transfers. Keep the transaction hash with the pool address because a wallet activity label does not identify every contract involved.

A partial exit follows the same checks, except the remaining direct or staked LP balance stays above 0. That nonzero balance continues to represent the wallet's residual share under the selected pool contract.