Camelot DEX
Camelot DEX Supports Token Swaps and Full-Range or Concentrated Liquidity
Camelot DEX is a decentralized exchange where users swap tokens or supply assets to full-range and concentrated liquidity pools. Its foundation is Arbitrum One, with deployments across parts of the Arbitrum Orbit ecosystem. Swaps exchange one asset for another; liquidity deposits create positions whose token composition changes as trading occurs. V2 provides full-range liquidity, while V3 and V4 support selected price ranges. Manual positions give users control over those ranges, and available automated strategies manage them. The useful choice depends on token compatibility, available liquidity, and whether the aim is immediate conversion or continued exposure to a pool.
The short version: A concentrated liquidity position earns trading fees within its selected price range, so range selection changes both token exposure and management needs.
Token Conversion or an Ongoing Liquidity Position
A swap fits an immediate conversion, while liquidity provision commits assets to a pool that other users trade against. These actions produce different holdings. A completed swap delivers the output token; a liquidity deposit creates an interest in pooled assets, with potential trading fees and changing token balances. Camelot’s exchange uses an automated market maker, or AMM, to price trades through pools.
Network compatibility comes first. Tokens on another chain aren’t available to a local pool simply because their tickers match. Camelot’s presence on multiple networks also doesn’t mean every deployment offers identical pairs, liquidity, or strategies. The relevant choice starts with the network and token contracts the intended pool supports.
What Determines the Amount a Swap Returns?
A swap’s output depends on the input amount, available liquidity, pool pricing, applicable fees, and market movement before execution. Price impact describes how the trade itself changes the pool price. Slippage tolerance sets the acceptable execution difference; raising it doesn’t improve liquidity or the quoted exchange rate.
Camelot supports pool-specific swap modes and aggregation. A mode restricted to one AMM version searches a narrower set of liquidity than aggregation. Compare the quoted output and minimum received for the same input, including the network transaction cost. For tokens with transfer taxes, avoid aggregator mode because its route can trigger multiple taxed transfers. Use a compatible pool-specific mode with liquidity for that token.
Swap fees aren’t one universal percentage. V2 pairs can apply different fees by direction, and V3 supports fees that respond to volatility. A reverse trade therefore needn’t have the same fee as the original direction.
Full-Range Pools and Their Pricing Curves
Camelot V2 offers volatile and stable pool types, with pricing curves suited to different relationships between the paired assets. Full-range provision avoids selecting upper and lower price boundaries, although trading still changes the underlying asset balances.
Volatile Pairs
Camelot V2 volatile pools use a constant-product pricing curve. The relationship is commonly written as x × y = k, with x and y representing reserves in the idealized model before fee effects. Larger trades relative to those reserves move the marginal price further.
Stable Pairs
Camelot’s stable curve targets correlated assets and seeks to keep exchange ratios near parity. That pricing design doesn’t guarantee either token’s value or preserve a peg. Choosing this pool type requires an economic relationship between the assets; a familiar ticker alone doesn’t establish one.
How Does a Concentrated Position Earn Fees?
A concentrated position earns trading fees when swaps use its liquidity within the selected price range. Focusing capital around fewer prices increases liquidity density, but actual earnings still depend on trading activity and competing active liquidity.
A manual V3 position stops earning trading fees while the pool price remains outside its selected range. Beyond a boundary, its principal consists of one asset. Crossing that boundary doesn’t itself liquidate the position, and the liquidity becomes active again if the price returns inside.
V3 uses tick-based concentrated liquidity built on Algebra. Ticks define the permitted price boundaries, so the accepted range can differ slightly from typed prices. A narrower interval increases concentration, but it also leaves less room for market movement before the position becomes inactive.
V4 uses Algebra Integral’s modular architecture. It also supports concentrated liquidity, while plugins can change peripheral pool behavior, including fees. Custom pools for the same token pair may use different configurations. Their shared tokens don’t establish identical operating conditions.
Manual Ranges and Automated Strategies
Liquidity management determines who chooses and adjusts a concentrated position’s range. Camelot provides manual provision and an automated route where a compatible strategy is available.
Direct Range Control
Manual provision suits a requirement for specific price boundaries. The deposit ratio follows the selected range and its relationship to the pool price, rather than an arbitrary equal split. Managing the position also involves deciding whether its existing exposure remains acceptable as prices move. To exit a manual V3 position, withdraw its liquidity through the position controls; the returned token amounts reflect its current composition.
Delegated Range Management
Auto mode requires a strategy provider and a strategy, as well as supported tokens and deposit amounts. Automation reduces direct range management, while adding the selected strategy’s contracts and operating rules. It doesn’t remove the assets’ price exposure. Available strategies, their charges, and their withdrawal conditions belong in the comparison with a manual position.
Trading Fees and Campaign Rewards
Trading fees come from swaps, while incentive campaigns distribute additional rewards under their own eligibility rules. A pool can support trading without offering a reward campaign. An advertised annualized rate also doesn’t fix future earnings, because activity, active liquidity, and reward funding can change.
Camelot’s incentive system distinguishes V2 liquidity ownership from V3 fee generation when allocating rewards. Campaigns can impose address restrictions, and V3 campaigns can also apply token weightings, so equal deposit values don’t necessarily earn equal rewards. Reward calculations and claims also have their own update process; a recent deposit doesn’t imply an immediately visible claim.
Pool version matters. The existence of V4 liquidity doesn’t establish eligibility for a campaign targeting V2 or V3. Evaluate the actual campaign’s pool, eligible positions, reward token, and distribution conditions before treating incentives as part of a position’s expected proceeds.
GRAIL Conversion and xGRAIL Allocation
GRAIL and xGRAIL add token conversion and allocation functions alongside trading and liquidity provision. xGRAIL is an escrowed governance token with transfers restricted to interactions involving whitelisted addresses. Holders can allocate it to plugins for the benefits each plugin specifies. Allocated xGRAIL is unavailable for other uses until deallocated, and deallocation can incur a fee. Those token-allocation plugins serve a different purpose from V4 plugins that customize pool behavior.
Conversion has different conditions in each direction. Converting GRAIL into xGRAIL uses a one-to-one ratio, while redeeming xGRAIL into GRAIL requires vesting. Longer vesting increases the GRAIL received, up to a one-to-one ratio at the maximum duration; completing a shorter redemption burns the remaining GRAIL. Cancelling an unfinished redemption returns xGRAIL and voids that redemption; it doesn’t provide a partial GRAIL payout.
Why Does Changing a Range Alter the Required Tokens?
A manual concentrated deposit requires token amounts determined by its range relative to the pool price. Consider a deposit prepared with only one token: a range entirely above or below the current pool price requires one particular asset of the pair, while a range spanning that price generally requires both. Changing that input changes the required composition.
- Confirm that the wallet network and token contracts match the selected pool before considering a deposit.
- If the proposed active range requires a token the wallet lacks, stop before approval or submission.
- Adjust the unsubmitted range only if the resulting exposure fits the intended position; an outside range won’t earn fees immediately.
- If the revised amounts match the available balances and intended exposure, review the spending approval before authorizing the deposit.
- After submission, compare the confirmed transaction and recorded position with the intended pool, deposited amounts, and accepted boundaries.
A preview change is reversible and moves no tokens. If the available balance can’t support the intended exposure, leaving the deposit unsubmitted avoids creating an unwanted position.
Pool Exposure Compared With Holding Tokens
Holding tokens outside a pool avoids the changes in token composition caused by pool trading. Impermanent loss describes the value difference between a liquidity position and retaining the deposited tokens outside the pool. Trading fees can offset that difference, but they needn’t cover it.
A swap fits a desired asset conversion. Full-range liquidity avoids managing price boundaries; concentrated liquidity offers more control over where capital participates. An automated strategy delegates that management under additional operating rules. If retaining the original token quantities is the priority, holding them outside a pool is the more direct alternative.
Questions people ask about Camelot DEX
Do I Need GRAIL to Make an Ordinary Token Swap?
GRAIL ownership isn’t a general prerequisite for an ordinary swap. The required assets are the selected input token and the network’s transaction-fee asset. GRAIL conversion and xGRAIL allocation are separate functions, rather than an access requirement for every trading pair.
Why Does the Wallet Request Approval Before a Swap?
A token approval authorizes a contract to spend the token within the approved allowance. It doesn’t complete the swap itself. A subsequent transaction performs the exchange, so an approval confirmation alone doesn’t establish that the output token has arrived.
Does an estimated-amount Error Prove a Token Has a Transfer Tax?
An estimated-amount error doesn’t prove that a token charges a transfer tax. Market volatility can also produce that error. Taxed tokens need a compatible pool-specific route; avoid aggregator mode because it can trigger multiple taxed transfers. Raising slippage without identifying the cause can permit a worse execution without resolving incompatibility.
Are Manual V3 Trading Fees Automatically Compounded?
Manual V3 fees are available to harvest rather than automatically increasing the position’s principal. In auto mode, trading fees compound into the liquidity position. Incentive rewards are a separate category, so a compounding strategy doesn’t imply that every reward token automatically becomes additional liquidity.
Can a New Token Pair Have a V3 Pool?
A new token combination can have a V3 pool when no V3 pool already exists for that pair. Creation requires the relevant tokens, an initial pool price, a selected range, and the necessary deposit amounts. The first liquidity provider sets that starting price, so check the token order and exchange rate before approving and depositing. Creating a pool doesn’t supply outside trading demand or guarantee that other providers will add liquidity.
Is an Emergency Pause Possible in a V4 Pool?
Camelot’s documented V4 security plugin supports emergency pool halts. That capability doesn’t establish that a particular pool is paused or that every custom pool uses identical controls. Pool operation depends on its actual configuration, including the plugins attached to it.