Curve: token swaps, pool fees, LP withdrawals, lending and governance

Curve is a collection of smart-contract services with a shared interface and governance ecosystem. Its exchange activity is organised around liquidity pools rather than a central limit-order book. StableSwap targets assets expected to trade near one another, while CryptoSwap handles less closely correlated prices. A pool share is a claim on changing pool assets; it is not a deposit balance with a fixed redemption currency.[1]

For an ordinary swap, select the network, input and output tokens, amount and route. The preview’s minimum received is more useful than assuming that the displayed dollar price is executable for any size. An allowance may need a separate wallet approval before the swap transaction can be signed. That approval is spending authority for the specified contract; it is not the trade itself. Review the contract and amount shown in the wallet, particularly when an unfamiliar token is involved.[7]

The current lending architecture allows markets with different borrowed and collateral assets. Its configurable oracle, rate policy, caps and liquidation parameters make the individual market the relevant unit of analysis. A newly deployed market is not automatically an unrestricted borrowing facility; administrative configuration and an enabled cap can matter. The old v1 user guide explicitly describes itself as a version being phased out, so its examples should not be copied unqualified into a new v2 loan.[24][6]

The 15 October update reports a live v2 market using a reUSD/sfrxUSD LP token as collateral, with a 3 million crvUSD cap after the relevant vote executed. That is a particular deployed market, not a cap applying to every pool or borrower. The same update separates a different proposal still in voting; proposed markets and limits are not treated as available products in this profile.[29]

StableSwap configurations can increase charges as balances move away from their intended relationship. CryptoSwap uses parameters governing fees near and away from the target balance. A published base fee therefore does not necessarily describe the whole executed route. Parameters can also be changed through the applicable governance process. Comparing two routes requires their final output for the same input and network, rather than selecting the lowest isolated fee number.[10]

For a simple fee-only illustration, 10,000 units traded at an assumed 0.02% pool rate incur 2 units of fee. This is a calculation using one possible rate, not a universal Curve tariff. It excludes price impact, gas, transfer-tax tokens and any additional pools in a route. A quote showing 1,000 output units with a 0.5% tolerance instead imposes a 995-unit minimum; that bound applies after the quoted pool costs, so deducting the fee from it again would double count.[7]

The router can combine several operations into one transaction, but an executable quote is not a guaranteed standing order. Pool balances can move before confirmation. A tighter bound can cause failure instead of an unfavourable fill; a wider bound accepts more execution variation. An approval transaction and a swap can also be separate gas-paying actions. The exact wallet preview, not a generic advertised percentage, determines what is being authorised.[2]

Lending costs need a separate calculation. Interest increases outstanding debt over time, while swaps used to leverage, repay or liquidate can add pool costs and price impact. The legacy borrowing guide describes no separate loan-opening or closing fee, but that statement should not override the current v2 market’s actual configuration and route preview. A low displayed interest rate is not an estimate of total cost if collateral moves through LLAMMA during the loan.[19]

Curve does not consolidate all networks into one exchange cash balance. The chain-support guide distinguishes where the exchange, lending and governance products operate; Ethereum remains the primary governance network. The availability of a token on one supported network does not establish that every Curve product is available there. Token contracts, gas assets and transaction histories need to be matched to the selected network.[13]

Bridging is a separate movement between chains, using the documented native or third-party route. The bridge guide includes LayerZero routes for CRV, crvUSD and scrvUSD. A matching token ticker is insufficient: verify the recognised contract address on the destination chain and allow for the route’s fees and completion process. Bridge failure, message delays and a missing destination gas balance can prevent an apparently simple onward swap or redemption.[14]

A lending vault’s visible share balance may exceed what can immediately be redeemed. Funds already borrowed are not idle cash; borrower repayments or other liquidity changes may be needed. Post-deployment controls include caps and other market settings. A supplier should distinguish the accounting value of shares from the maximum withdrawal available at that moment, and a borrower should distinguish collateral value from the amount releasable after satisfying debt and health constraints.[25]

FXSwap refuel deposits deserve particular care. They do not mint a normal, transferable claim that can later be redeemed by the contributor. The refuel mechanism supplies finite operating capital that is consumed as the pool recentres; it should be treated as a committed operating contribution, not ordinary LP principal. Exhausting that buffer does not necessarily stop all swaps, because other mechanisms can remain available. The existence of a refuel transaction in wallet history is not evidence of a withdrawable LP balance.[27]

CRV locks have their own calendar. The documented lock can run from one week to four years, with voting weight declining as expiry approaches. A user can add to or extend an active lock but cannot simply shorten it to withdraw early. veCRV is non-transferable, and the original CRV becomes reclaimable at expiry. A disconnected wallet, changed device or desire to switch pools does not remove that lock.[18]

An LP share exposes its holder to the assets and contracts beneath it. If a supposedly stable asset loses its peg, arbitrage can leave a pool increasingly concentrated in the weaker asset. A metapool or interest-bearing receipt can add underlying issuer, lending and redemption risks. Permissionless deployment also means that a visible pool is not proof that its tokens have been independently vetted or that the apparent dollar value is recoverable.[12]

LLAMMA gradually converts collateral across price bands, but the words liquidation protection do not mean losses are prevented. Conversions can reduce the value of the collateral position, and a price recovery does not necessarily restore the original amount. A loan can still reach hard liquidation when its health falls to the relevant threshold. The bottom of a configured conversion range is therefore not a guaranteed single liquidation price or a stop-loss instruction.[20]

Bad debt is a further risk for a lending supplier. If a market cannot recover enough from borrowers and collateral, the shortfall can affect lenders and restrict withdrawals. Market isolation can limit the spread of a problem, but it does not compensate the participants in the affected market. A displayed deposit value should not be read as a promise of full and immediate repayment; any recovery process depends on the actual deficit and available assets.[21]

The audit index covers distinct components and dates, including StableSwap NG, Tricrypto NG, cross-chain infrastructure and scrvUSD. That supports a more precise claim than saying the whole current ecosystem is audited. A report for a particular implementation does not establish that every new pool, oracle configuration, bridge, frontend change or collateral asset shares its coverage. This review inspected the index and documentation, without independently reproducing the audits or verifying all deployed bytecode.[5]

A protocol can be technically callable while an interface imposes separate terms. The current legal entry point was reached, but its operative clauses were not returned as readable text. Consequently this profile does not publish a country whitelist, a claim that identification is never required, or an assumed customer compensation scheme. The prospective user needs the current terms applicable to the exact interface and any bridge or wallet service used with it.[32]

Availability also varies by product and deployment. A supported chain can have DEX pools without the same lending markets, CRV locking functions or assets as Ethereum. A pool page, borrow cap and executable route provide more specific evidence than a general network logo. This matters especially when returning from another chain: the desired withdrawal asset and the bridge route out should be checked before the deposit is committed.[13]

The official links page leads to the application, documentation, governance forum and community channels. These are useful for identifying the correct project and discussing problems, but they are not evidence of a contractual customer-service response time. No verified broker-style telephone dealing facility or complaint-resolution clock was established. Keep the public transaction hash, chain, pool or market address, wallet address and the intended operation when asking for help.[23]

Frontend issues can be reported through the official repository and its linked developer community. A website error should be separated from a failed wallet signature, a reverted on-chain transaction, a pending bridge message or a successful transaction displayed incorrectly. The repository documents the interface’s dependency on protocol libraries and APIs; an interface outage does not, by itself, prove that a pool contract has stopped operating. Nor does that distinction guarantee that an alternative interface will provide a safe or available exit.[31]

The vulnerability programme provides a private reporting process with eligibility conditions and a stated maximum reward of US$250,000. That ceiling concerns qualifying security reports, not insurance per liquidity provider. Its scope distinguishes contract vulnerabilities from other issues. Report a suspected exploitable flaw using the official bounty instructions rather than publishing exploit details in a general support thread.[17]

Curve describes its core pool contracts as immutable, while governance and other contracts retain specific parameter-setting powers. Code immutability therefore does not mean that every operating condition is permanently fixed. Oracles, fees, collateral policies and connected contracts can still matter. Conversely, an emergency power over a related component should not be described as an unrestricted ability to withdraw LP assets. Authority has to be read contract by contract.[16]

The emergency documentation distinguishes the Peg Stability Reserve from the swap pools: pausing that component is not a blanket statement that every Curve pool can be paused. It also describes bounded changes to debt ceilings, deposit limits and certain lending parameters. These controls can affect access or capacity even when they cannot transfer a user’s assets to the signers. Their existence is a technical risk-management arrangement, not an insurance promise.[15]

Swiss Stake AG’s development report describes work on the Curve ecosystem, including LlamaLend v2 and a new Router V2 deployed on Ethereum, Base, Gnosis, Arbitrum and Optimism. It reports split routing and balanced LP withdrawal support. Those developments mean an older Router NG hop limit should not be asserted as the current universal interface limit. The report identifies a developer’s contribution; it does not by itself establish one contracting exchange operator for every Curve service.[30]

The current interface contract could not be established from readable operative terms. The documented DAO and development organisations cannot therefore be assumed to be the customer’s contracting exchange. Users of a specific interface, collateral market or third-party wrapper need the terms and authority applying to that particular relationship.[32]

The report excludes YieldBasis and omits unindexed or unpriced activity. It is therefore an historical, defined sample rather than live all-chain volume on 20 October. Swaps are transaction activity, not registered customers or unique active traders. The latest weekly report did not supply a comparable DEX volume table, so no apparent October growth rate or current global ranking is inferred from the September figures.[28]

Operator

Curve DAO-governed contracts; Swiss Stake AG is a documented development contributor

Exchange model

Decentralised

Service scope

Token swaps, LP positions, gauge rewards, CRV locks and separate LlamaLend borrowing and supply markets.

Client types

Retail clients

Pricing publication

Public pricing

Funding scope

On-chain tokens on supported networks; bridges add separate transfer dependencies.

Custody and asset handling

Wallet-authorised contracts hold pool or vault assets; LP shares and governance locks have different exit rights.

Client eligibility

Protocol connectivity does not establish interface eligibility. Current legal clauses and a complete jurisdiction matrix were not retrievable.

Support

Documentation, linked community channels and repository issues; no verified complaint-resolution clock.

Authorisation and registration scope

DAO governance and technical access do not establish a regulated exchange permission; no such permission is assigned here.

Exchange metadata checked 20 Oct 2026Source 1Source 2Source 4Source 14Source 16Source 18Source 23Source 24Source 30Source 32

Pool earnings and incentives follow different accounting paths. Base returns can increase LP share value, while CRV and other incentive tokens may require gauge staking and a separate claim. The displayed base yield is backward-looking; a boost or incentive can depend on a user’s position and governance holdings. Third-party points are not established cash receivables. Unclaimed rewards, LP principal and a time-locked CRV balance should therefore be recorded separately.[11]

scrvUSD is a vault receipt for deposited crvUSD, with returns linked to protocol borrowing revenue under its design. It is not a fixed-rate bank deposit. The receipt-to-underlying conversion can change as returns accrue, so comparing token counts alone can misstate the position’s value. A displayed rate is a current or historical observation, not a contractual assurance of future earnings or the stability of crvUSD.[22]

The positions interface is network-specific and shows LP positions and claimable amounts. Record every relevant chain and wallet, including gauge stakes, borrowed balances and bridge movements. A single screen is not evidence of a consolidated tax statement, and a comprehensive jurisdiction-ready export was not established in the reviewed material. Preserve transaction records and acquisition information independently of a particular dashboard layout.[3]

The October interface update describes mobile form changes, including drawer-based lending controls. That supports mobile browser usability, not a claim that every web function has an identical native app or that settings synchronise across devices. The reviewed frontend materials also did not establish a native copy-trading contract or AI agent with spending authority. A separate wrapper or automation provider introduces its own permissions; closing the Curve page does not unwind its contracts.[29][31]

An idle wallet remains capable of holding a live pool or vault position. There is no established general account-inactivity tariff in the reviewed positions documentation, but that finding says nothing about whether a loan continues accruing interest, an incentive ends or a governance lock has expired. Those conditions follow their individual contracts rather than the last time the user opened the interface.[3]