Camelot: AMM versions, liquidity strategies, costs and xGRAIL exits

Camelot is an Arbitrum-focused decentralised trading and liquidity platform with several generations of automated market maker. Its website combines token swaps with pool participation and related GRAIL/xGRAIL mechanics. A spot swap, a managed liquidity strategy and a token redemption are different transactions with different exit conditions.[1]

The DefiLlama Camelot dataset observed on 20 October 2026 showed approximately $124.52 million of 30-day DEX volume and $2.17 million over 24 hours. These are dated protocol trading measures, not a count of registered users, audited revenue or GRAIL-token exchange volume. The dataset aggregates tracked Camelot components; its methodology should remain attached to comparisons with other venues.[2]

The V4 documentation describes adaptive and direction-sensitive fee mechanisms, custom pools and a security plugin able to stop one or multiple pools. Its references to limit-order and perpetual-leverage plugins include development or future features. They do not establish a generally available Camelot derivatives account, a live universal limit-order book or a published leverage schedule.[6]

The swap guide asks the user to inspect the expected rate, price impact and minimum received. A successful wallet approval is only permission for a contract to use tokens; the swap still needs its own confirmation. Before signing, the amount and selected output asset should be reconciled with the actual transaction prompt.[13]

Camelot’s token-tax guide warns that an aggregated route can apply transfer taxes multiple times. Increasing slippage tolerance does not reduce that tax; it permits a wider execution outcome. Taxed-token support can also differ between pool versions. The complete token and route behaviour matters more than a low displayed pool percentage.[8]

For an illustration, an estimated output of 1,000 token units with a hypothetical 0.5% tolerance corresponds to a 995-unit floor before any separate mechanism that the quote does not include. This calculation explains tolerance; it is not a promise that a taxed token will arrive at that amount or that execution will occur. The actual confirmation must show the route’s minimum received.[3]

These percentages divide the protocol’s fee revenue; they are not fees charged as those percentages of a customer’s trade. Each column totals 100%. They also do not establish an individual LP’s yield: pool activity, the position’s active range and its share of eligible liquidity affect the eventual amount.[9]

Camelot uses a supported blockchain wallet. The Arbitrum guide describes obtaining assets through a bridge or a centralised exchange withdrawal and keeping ETH for Arbitrum One gas. A centralised venue’s withdrawal minimum or a bridge’s waiting period belongs to that separate service; neither is a universal Camelot deposit rule.[11]

A wallet-to-wallet transfer has no ordinary Camelot withdrawal queue because no conventional customer account balance is being debited. A pool or vault exit is different: it calls the relevant contract, depends on available chain execution and can be affected by pool controls or strategy terms. A visible wallet balance should not be confused with capital still committed to a position.[14][20]

xGRAIL is non-transferable except through allowed contracts and cannot be used in another plugin while allocated. The usage guide gives a default 0.5% deallocation fee. For an illustrative 200 xGRAIL deallocation at that rate, the charge is 1 xGRAIL and 199 return before any separate redemption choice. Deallocation and GRAIL redemption are different steps with different consequences.[18]

The wallet guide places recovery-phrase and private-key responsibility with the wallet owner. Camelot does not thereby become a password-recovery service for that wallet. Once assets enter a pool or strategy, their return depends on that contract and its permissions as well as the user’s ability to sign an exit.[19]

Liquidity risk is separate from key security. As relative asset prices move, a pool position can underperform simply holding the deposited assets. Concentrated liquidity adds a chosen range: outside that range, the position can become entirely one asset and stop earning in-range trading fees until price returns or the position is adjusted.[27][15]

Access requires a compatible wallet and assets on the selected deployment. The public wallet guide describes both desktop-browser and mobile wallet options. It does not establish a centralised individual KYC account, institutional onboarding standard or a right to use every product in every jurisdiction.[19]

The application returned a loading shell. Its complete operative terms, contracting entity and country restrictions could not be recovered. This documentation gap does not establish unrestricted legal access.[28]

For a failed or delayed action, the relevant evidence is the chain, transaction hash, router or position identifier and exact operation attempted. V4 security controls can pause pools, so repeatedly approving a transaction is not proof that a blocked pool will execute. No public promise of a human override for a halted contract was established.[6]

No independently verified exchange authorisation, custody permission or compensation scope was established. Incomplete legal retrieval prevents a reliable licensed-entity mapping; wallet access does not supply that evidence.[28]

Camelot’s launch documentation dates its public sale to 29 November–5 December 2022, with initial liquidity planned after the sale. Its separate Genesis emissions ended on 23 May 2023. Those historical incentives should not appear as current account-opening rewards or guaranteed benefits for a new liquidity position.[26]

The Orbital Liquidity Network documentation describes expansion within the Arbitrum ecosystem. Some cross-chain swapping, gauge and accelerator features are labelled upcoming. A network strategy is different from a confirmed live deployment: chain support, routers and assets should be established from the relevant contract reference and current application.[25]

The published materials identify a protocol team and administrative multisignatures, but the inspected sources did not establish a specific contractual company, registered office or shareholder structure. The profile keeps those fields unresolved rather than assigning the protocol’s name to an invented corporation.[1][28]

Operator

Protocol team and contract administrators; a specific contractual legal entity was not established from the inspected public material.

Exchange model

Decentralised

Service scope

Arbitrum-based spot routing, multiple AMM generations, liquidity strategies and xGRAIL participation.

Client types

Not established

Pricing publication

Public and quoted pricing

Pricing scope

Pool-, direction- and route-dependent fees; network charges and third-party costs are additional.

Funding scope

On-chain assets on the selected deployment; independent bridges and centralised withdrawal routes are separate services.

Custody and asset handling

Wallet-authorised interaction with pools and strategy contracts; multisignature administration affects specified contracts.

Client eligibility

Wallet and supported network required; a complete current legal-country matrix was not recovered.

Support

Official support documentation links community channels; no universal response clock established.

Authorisation and registration scope

No independently verified exchange authorisation or statutory customer compensation scope established.

Exchange metadata checked 20 Oct 2026Source 1Source 7Source 12Source 18Source 20Source 23Source 28

The incentive guide contains a legacy spNFT transition notice with a January 1 deadline that does not display a year in the inspected text. It also marks some integrations and V4 support as future work. Existing position owners need the current claim and migration instructions for their own contract; the undated notice cannot establish a new universal future deadline.[10]

The manual-position guide says rewards may take more than four hours to appear. Its harvest control can collect pending position rewards. A screen showing no current claim should be checked against the calculation epoch and the position’s eligibility rather than treated immediately as evidence of a missing deposit.[15]

No current official autonomous AI execution service or copy-trading mandate was established in the inspected plugin documentation. Disconnecting a wallet from the website changes the session; it should not be assumed to remove an existing contract allocation or dispose of a liquidity position. Those actions require the relevant plugin or position controls.[30]

No numeric inactivity fee, conventional account deactivation or wallet-recovery cooldown was established in the inspected material. Product allocations and timed redemptions have their own conditions.[19]