Curve DEX

Orange · 69/100

Executive summary

Curve DEX is a multi-chain automated market maker optimized for stablecoin and pegged-asset swaps, scoring 44/100 (orange band) with high data confidence (85/100) and a -10 penalty for unresolved incident remediation.

  • Security: Extensive audit coverage by ChainSecurity, MixBytes, Trail of Bits, and Quantstamp across DAO, DEX pools, crvUSD, and LlamaLend; all critical/high findings in reviewed audits were reportedly fixed, but bytecode match to current multi-chain deployments is not verifiable as of September 2026.
  • Incidents: July 2023 Vyper reentrancy exploit ($61.7M loss, reimbursed); two DNS hijacks (2022: $575k recovered; May 2025: ~$450k, partial recovery, reimbursement incomplete); June 2024 crvUSD depeg/liquidation cascade ($31k loss, compensation rejected); January 2026 DUSD/USDC oracle manipulation ($6.16M loss, $3.65M recovered, $2.15M unrecovered); March 2026 sDOLA/crvUSD oracle attack ($822k borrower loss, no reimbursement executed); October 2025 CRV-long market bad debt (~$700k lender shortfall, unresolved).
  • Governance & custody: Non-custodial protocol governed by veCRV holders via Ethereum-based DAO with 168-hour execution delay; Emergency DAO (5-of-9 multisig) can freeze pools and deploy up to 400k crvUSD without standard delay; voting power concentrated in large lockers; signer identities and independence not verifiable.
  • Top risks: Smart-contract/compiler vulnerabilities (Vyper incident demonstrates correlated failure); oracle manipulation and liquidation cascades in illiquid LlamaLend markets; permissionless pool integration exposes LPs to depeg, bridge, and issuer insolvency of any listed asset; founder Michael Egorov's historically large CRV-collateralized borrowing created systemic liquidation risk (debts now reduced but concentration remains); cross-chain messaging via LayerZero FastBridge with temporary unbacked minting and DVN censorship risk.
  • Strengths: Very low slippage and fees for stablecoin swaps via StableSwap invariant; deep multi-chain liquidity ($1.4B TVL); passive LP model; mature documentation and open API; no fraud/rug-pull history; active bug bounty (up to $250k).
  • Unverified: Current on-chain TVL, exposure, and concentration by chain (Dune unavailable); exact bytecode match of audited code to live deployments on Arbitrum, Avalanche, Base, Fantom, Fraxtal, Gnosis, Kava, Monad, OP, Plasma, Polygon, Sonic; Emergency DAO signer identities; DAO treasury composition and withdrawal status; stress-test losses under BTC <$10k or collateral depeg scenarios.
  • Recommended exposure: Conservative allocation (≤5% of DeFi portfolio) given unresolved incidents and oracle/liquidation risks; favor Ethereum mainnet pools with deep liquidity and established assets; avoid illiquid LlamaLend markets and newer chains without verified audits; monitor Emergency DAO actions and founder CRV positions; require independent on-chain verification of pool health and admin controls before deployment.
  • Open questions: Verify current bytecode of deployed contracts matches audited versions on each target chain; confirm Emergency DAO signer identities, independence, and recent actions; quantify chain-by-chain TVL, collateral composition, and liquidation thresholds; assess DAO treasury adequacy for future incident reimbursement; validate oracle robustness and manipulation cost for target pools; review founder CRV collateral positions and liquidation risk; confirm LayerZero FastBridge DVN configuration and daily limits.

Score

Component Weight Raw Points Reason
Security 20% 100 20.0 17 audit(s); continuous security program bonus; active bug bounty bonus
Audits 20% 50 10.0 last full audit 2025-02-21 is older than a year
Incidents 20% 100 20.0 5 open incident(s), $4,513,475 at risk = 0.4% of TVL (threshold 10%)
Governance 20% 90 18.0 DAO governance; no single party can withdraw funds
TVL 20% 7 1.4 TVL $1,281,058,757 = 7% of reference ($17,538,184,136)
Data confidence 85 7/7 critical categories; 17/63 verified facts; 63/63 fresh (180d)

Identification

protocol identification

two sources

Curve is a decentralized exchange (DEX) and automated market maker (AMM) optimized for swaps between stablecoins and similarly priced assets using the StableSwap invariant. ### Protocol identification

  • Name: Curve Finance / Curve DEX
  • Category: DeFi DEX / AMM for stable and pegged assets (stablecoins, wrapped BTC/ETH, LSTs).
  • Launch date: Protocol launched on Ethereum in January 2020 (mainnet launch around 3 January 2020).
  • Website: Public sources identify curve.fi as the primary front-end and hub for the protocol (not directly cited here per constraints; treat as standard industry knowledge).
  • Docs: The Curve Knowledge Hub / Technical Docs are hosted under the protocol’s documentation domain, describing user, developer, and factory documentation.
  • Native token: CRV – governance and incentive token of the Curve DAO; launched August 2020 on Ethereum, max supply ~3.03B.
  • Chains: Documentation and analytics sources confirm deployments on Ethereum mainnet and multiple EVM L2/sidechains, including Arbitrum, Avalanche, Fantom, Optimism (OP Mainnet), Polygon, Gnosis/xDai and others.
  • Presence on some newer chains in your list (Base, Fraxtal, Kava, Monad, Plasma, Sonic) is mentioned in factory/deployment docs for “EVM-compatible sidechains/L2s” and specific implementations (e.g., Sonic admin blueprint), but per-contract, chain-specific deployment details are Not verifiable as of 2026-09-04 from the retrieved data. ### Main contracts (high level)
  • Curve uses pool implementation contracts and factory contracts (ERC‑5202 blueprints) from which pools, gauges and LP tokens are deployed.
  • Pools are categorized as plain pools, lending pools, and metapools implementing the StableSwap invariant.
  • Exact “main” contract addresses and explorer verification status per chain are Not verifiable as of 2026-09-04 from the available data (would normally require direct explorer/on-chain checks). ### Fork lineage and design
  • Curve is not described as a fork of another DEX; it is generally treated as an original protocol introducing the StableSwap algorithm, later forked by others.
  • The StableSwap AMM is presented as its own invariant, distinct from Uniswap’s constant product, concentrating liquidity near the peg.
  • The documentation highlights additional innovations such as crvUSD and Curve Lending with LLAMMA liquidation mechanisms, which are native developments of Curve.
  • Audits: Public sources and industry practice indicate Curve has undergone multiple formal audits, but specific reports, auditors, and coverage of incremental changes are Not verifiable as of 2026-09-04 from the retrieved snippets.
  • Malicious-modification history in similar forks: Many later DEXes and stable-swap AMMs adopted or forked Curve’s design, and some forks have had incidents; however, no concrete, source-backed catalog of malicious modifications in Curve-style forks is available in the retrieved data, so this item is Not verifiable as of 2026-09-04.
Evidence (15)

maturity

two sources

Curve DEX appears to be a real, functional product rather than a pure landing page: the documentation site includes user guides for depositing, staking, unstaking, and withdrawing, and the docs explicitly describe live UI actions for those flows. The documentation portal also contains developer material and an API reference, which is a strong sign of product maturity and integration readiness. The best-supported open-API signal is the published Curve API documentation and OpenAPI spec referenced in the project’s public GitHub repository, plus the docs site’s dedicated curve-api section.

That indicates an open, documented API exists. What is not verifiable from the gathered web evidence is the live operational state of the app today across the listed chains, including whether deposits/withdrawals are currently working on each network, and whether any broken links, fake metrics, or template-style placeholders exist. Not verifiable as of 2026-09-04.

Overall assessment: high maturity on documentation and developer tooling; likely a real portal with functional user flows; open API present; live-chain execution status and any UI defects remain unverified as of 2026-09-04.

Evidence (5)

Security

bug bounty

unverified

Curve appears to have an active bug bounty/security reporting program. The program is documented in Curve’s security page and in Curve DAO contracts/GitHub as an active bounty for issues that can cause substantial loss of money, broken liveness, or irreversible loss of funds. It is not verifiable as of 2026-09-04 whether this is run through a formal third-party platform or managed directly by Curve; the public documentation reviewed does not show a named platform.

The documented payout matrix on Curve’s security page shows rewards from $250 to $250,000 depending on likelihood/severity, with the top tier at $250,000. The security page itself is dated 2020-07-10, which is the earliest public evidence found for this program. No independently verifiable results table or total paid-out amount was found in the reviewed sources, so the program’s realized results are Not verifiable as of 2026-09-04.

Active
Yes
Max payout
$250K
Since
2020-07-10
Evidence (2)

counterparty risks

unverified

As of September 6, 2026 — Curve DEX dependency and counterparty risk Assessment: HIGH and multi-layered. Curve has no inherent centralized custodian or mandatory CEX/MM dependency; however, pool users inherit the solvency, oracle, bridge, and governance risks of every listed asset and integration.

  • Bridges/cross-chain: Curve uses canonical L2 bridges for some crvUSD routes and a LayerZero-based FastBridge for Arbitrum, OP Mainnet, and Fraxtal. FastBridge can release temporarily “unbacked” crvUSD before canonical settlement; compromised DVNs or messenger contracts could censor transfers or mint excess destination tokens. Curve paused LayerZero infrastructure in April 2026 after an external rsETH exploit, then resumed selected CRV bridges with conservative 10,000-CRV chain limits and reduced daily limits.
  • Oracle/manipulation: crvUSD/LlamaLend markets depend on Curve-derived and external pricing. ChainSecurity identified oracle-update sandwich risk and liquidation feedback loops in illiquid pools. A 2026 LlamaLend sDOLA incident reportedly caused approximately 822,475 crvUSD of borrower-equity losses through rate manipulation, distorted oracle pricing, and liquidations.
  • Stablecoin, LST/LRT, RWA and issuer exposure: Curve pools can contain USDC/USDT-like stablecoins, ETH derivatives/LSTs, protocol-issued stablecoins, and newer RWA-linked assets such as FIDD. A depeg, issuer freeze, redemption failure, rehypothecation loss, or bridge failure can create LP losses and liquidation cascades. Exact asset-by-asset exposure by chain is Not verifiable as of September 6, 2026 because Dune MCP is unavailable.
  • crvUSD/scrvUSD dependency: crvUSD is exposed to collateral liquidity, LLAMMA liquidation mechanics, PegKeeper/governance parameters, and cross-chain liquidity fragmentation; scrvUSD adds vault/accounting and redemption-liquidity dependence. The protocol reported crvUSD remained near peg through the 2026 market decline, but this is protocol-sourced and not an independent on-chain verification. > Contradiction / update: Prior notes cited Superbridge for some crvUSD routes. Current evidence confirms LayerZero FastBridge for Arbitrum, OP Mainnet, and Fraxtal; a current Superbridge dependency is Not verifiable as of September 6, 2026. CEX/MM, custodian, issuer concentration, chain-level TVL shares, and maximum counterparty exposure are Not verifiable as of September 6, 2026 without raw on-chain analysis. No Dune query ID or execution ID is available. Failure scenarios: bridge minting or censorship; stablecoin/LST/RWA depeg; oracle manipulation; thin-pool liquidation spiral; crvUSD bank-run/redemption stress; issuer insolvency or sanctions freeze; governance/admin-key compromise. Structured fields: dependency_failure_active: null; max_exposure_pct: null
Evidence (5)

crypto custody

unverified

Curve DEX is organized as a non-custodial protocol: users interact with smart contracts/pools directly, and Curve does not take possession of user private keys or hold user assets in the way a centralized custodian would. Governance is organized through Curve DAO, with CRV holders able to lock tokens as veCRV to vote on protocol parameters, gauges, fees, and related changes. For chain-native and ERC-20 assets managed by the DAO across non-Ethereum chains, Curve documentation describes a DAO-controlled Vault contract, but that is protocol treasury/governance custody rather than user custody.

Withdrawal status is not verifiable as of 2026-09-06.

Evidence (3)

incident

one source

Curve DEX: Frontend & Infrastructure via DNS Hijack on Ethereum; loss $575,000, returned $575,000 (DeFiLlama hacks registry). Remediation status: resolved (retained evidence).

Date
2022-08-09
Cause
Frontend / infrastructure hack
Loss
$575K
Status
resolved
Recovered
$575K
Classification
Frontend & Infrastructure
Technique
DNS Hijack
Evidence (1)

incident

one source

Curve DEX: Reentrancy via Vyper Compiler Bug on Ethereum; loss $61,700,000 (DeFiLlama hacks registry). Remediation status: resolved (retained evidence).

Date
2023-07-30
Cause
Smart-contract exploit
Loss
$61.7M
Status
resolved
Reimbursed
Yes
Classification
Reentrancy
Technique
Vyper Compiler Bug
Evidence (2)

incident

unverified

2024-06-12 — crvUSD upward depeg and sUSDe LlamaLend liquidation cascade (Ethereum): PegKeeper V2’s deviation check failed to stabilize crvUSD during liquidation demand, causing improper liquidation of sUSDe borrowers. Reported user loss was approximately $31,000. Curve proposed 112,637 CRV compensation, but governance commentary records that the compensation vote was rejected and payment was not executed.

PegKeeper and market-design mitigations were pursued. Status: remediation_in_progress; reimbursement unresolved.

Date
2024-06-12
Cause
Depeg / collateral
Loss
$31K
Status
remediation in progress
Recovered
$0
Reimbursed
No
Evidence (2)

incident

unverified

2025-05-12 — Curve.fi frontend/domain hijack: registrar/DNS compromise redirected users to a malicious imitation site that solicited wallet signatures. Curve contracts and infrastructure were not compromised. Media reported approximately $450,000 stolen and substantial recovery, while a later governance proposal documented materially different claimant totals and said any DAO reimbursement was discretionary and not guaranteed.

Therefore final recovered amount and reimbursement completion are Not verifiable as of September 6, 2026. The domain was taken offline and Curve moved users to curve.finance. Status: remediation_in_progress.

Date
2025-05-12
Cause
Frontend / infrastructure hack
Loss
$450K
Status
remediation in progress
Evidence (2)

incident

one source

August 2025 DNS/domain compromise affecting Curve front-end access: reporting says Curve shifted to a new domain after a DNS attack. Reported impact was about $450,000 stolen, with more than 83% reportedly recovered and reimbursed to impacted users. Because only media coverage was available in this run and no on-chain verification was possible, this should be treated as an incident report rather than a fully verified chain-level accounting.

Current status: resolved.

Date
2025-05-14
Cause
Frontend / infrastructure hack
Loss
$450K
Status
resolved
Recovered
$450K
Reimbursed
Yes
Evidence (1)

incident

unverified

2025-10-10 — CRV-long LlamaLend market (Ethereum): liquidation-mechanism failure and accumulated bad debt, with no identified external attacker. Lenders became unable to withdraw fully; vault assets were reported around 70% backed, implying approximately $700,000 of lender loss/underbacking. Curve deprecated the market and proposed a permissionless recovery pool using impaired vault tokens, but this is not a guaranteed repayment.

No reimbursement was verified. Status: unresolved.

Date
2025-10-10
Cause
Liquidity issue
Loss
$700K
Status
unresolved
Reimbursed
No
Evidence (1)

incident

one source

2026-01-20 — DUSD/USDC Curve pool (Ethereum): flash-loan manipulation of Makina’s MIM/3CRV accounting instruction inflated DUSD’s external Curve oracle and drained USDC. Affected users were LPs, not funds inside Makina machines. Gross user loss was approximately $6.16m: $4.2m direct exploit loss, $884k execution costs, and $1.076m post-exploit toxic flow.

Attacker/MEV proceeds were approximately 1,299 ETH (~$4.2m). Recovery mode, withdrawals and redemptions were paused; accounting was hardened, permissioned keepers enabled, and operations restored on January 26. Approximately $3.65m was recovered or committed for distribution, but about $2.15m remained unrecovered in the latest disclosed accounting.

Users received partial restitution; full reimbursement is not verified. Status: remediation_in_progress.

Date
2026-01-20
Cause
Oracle manipulation
Loss
$6.2M
Attacker proceeds
$4.2M
Status
remediation in progress
Recovered
$3.6M
Reimbursed
No
Evidence (2)

incident

unverified

2026-03-02 — sDOLA/crvUSD LlamaLend (Ethereum): flash-loan/oracle manipulation inflated the sDOLA rate and triggered hard liquidation of 27 borrowers. Borrower equity loss was approximately 822,475 crvUSD; lenders and Curve incurred no bad debt. Attacker proceeds were estimated at $240,000–$245,000.

The market was deprecated and removed from the UI; higher borrow rates and oracle redesigns were pursued. Compensation proposals remained pending, with the funding-source proposal explicitly stating that final repayment terms were not agreed. Status: remediation_in_progress; reimbursement not executed.

Date
2026-03-02
Cause
Oracle manipulation
Loss
$822K
Attacker proceeds
$245K
Status
remediation in progress
Recovered
$0
Reimbursed
No
Evidence (2)

key management

two sources

Curve DEX does not appear to organize key management around a protocol-controlled custody or wallet layer. The core architecture is a set of smart contracts for swaps, liquidity, gauges, fee distribution, and governance, while user control is centered on CRV/veCRV governance rather than any protocol-managed private-key system. For users, key management is therefore self-custodial by default: interacting with Curve means using an external wallet that the user controls, and Curve itself does not disclose a proprietary MPC, multisig wallet product, or embedded key-rotation system in the materials provided.

The governance model instead relies on locking CRV into veCRV, which gives voting power over gauge weights and protocol decisions; that is governance access, not custody of private keys. What is verifiable from the available sources is that Curve’s operational control is organized through on-chain contracts and DAO governance, not through a centralized key-management service. Not verifiable as of 2026-09-04: whether any specific admin, upgrade, or emergency controls use multisig, timelocks, or other off-chain key-management arrangements, because the provided sources do not confirm those details.

Evidence (7)

smart-contract

one source

Assessment — as of 2026-09-06. Dune was unavailable; therefore no raw on-chain state, decoded proxy-admin events, current role reads, timelock measurement, or Dune query/execution IDs are available. Architecture / addresses ``text veCRV holders → Curve DAO governance → Agent / cross-chain relayer → Ownership / Parameter / Emergency Admins → factories, gauges, pools, fee vaults Users → Router/Registry → pool contracts → LP tokens / gauges ` The documented legacy control path is DAO → Aragon Agent → Ownership Proxy → Contracts; PoolProxy controlled pool administration and GaugeProxy controlled gauges. Governance had separate ownership, parameter, and emergency authorities. A canonical Address Provider is 0x0000000022d53366457f9d5e68ec105046fc4383` on Ethereum and sidechains in the legacy registry documentation/source.

The current Curve Core registry defines slots for Ownership Admin, Parameter Admin, Emergency Admin, governance agent/relayer, and fee vault, but the registry itself is not proof of live state. An Ethereum explorer labels 0x40907540d8a6C65c637785e8f8B742ae6b0b9968 as “Curve: Ownership Agent”; this is an explorer attribution, not a verified cross-chain admin map. Admin powers / exit risk

  • Pool admin code includes fee withdrawal, pool kill/unkill, parameter changes, ownership/admin rotation, burner controls, and selected oracle/parameter configuration.
  • Emergency authority can kill pools/gauges; parameter authority can change pool parameters. Governance execution historically required voting delays/quorum, but the live timelock delay is Not verifiable as of 2026-09-06.
  • Ordinary LPs generally retain direct pool withdrawal paths; however, ability to exit every listed deployment, and whether any vault/strategy can block or redirect withdrawals, is Not verifiable as of 2026-09-06.
  • Key compromise worst case: malicious parameter/fee changes, pool/gauge shutdown, admin-fee extraction, replacement of admin authorities, or—where an upgradeable/vault component exists—malicious implementation or asset-routing changes. Arbitrary draining of all user funds by the core pool admin is Not verifiable as of 2026-09-06. Contradiction / limitation: Curve publishes audited components, but audit coverage does not prove every listed chain deployment matches audited bytecode. Deployment-to-audit matching and unresolved finding counts are Not verifiable as of 2026-09-06.
Evidence (5)

audit

one source

ETH/sETH pool implementation (Curve v1 style stableswap‑like pool on Ethereum).

Auditor
ChainSecurity
Report date
2021-09-27
Scope
ETH/sETH liquidity pool smart contracts on Ethereum mainnet DEX; not chain‑specific beyond mainnet.[1][3][12]
Findings
ChainSecurity report (referenced in catalog) discusses pool invariants, pricing, and withdrawal flows; Curve summary does not list explicit critical/high issues, implying none or all fixed.[1][3][12]
Fix status
Catalog presents this pool as audited with no outstanding critical/high findings; treated as marketing claim in absence of independent classification.[1][3]
Evidence (2)

audit

one source

ChainSecurity — Curve Tricrypto

Auditor
ChainSecurity
Report date
2021-09-29
Scope
CurveCryptoMath3, CurveCryptoSwap and CurveCryptoViews3; Vyper 0.2.11–0.2.15; three-asset Tricrypto system.
Findings
0 critical, 0 high, 1 medium, 9 low. Medium issue corrected; 6 low findings corrected and 3 acknowledged.
Fix status
Medium corrected; low-severity status split between corrected and acknowledged.
Evidence (1)

audit

one source

Curve Stablecoin Smart Contracts (crvUSD AMM)

Auditor
ChainSecurity
Report date
2023-06-01
Scope
crvUSD AMM and related stablecoin smart contracts (Ethereum; extension to other chains Not verifiable as of 2026-09-03).
Findings
Issues including incorrect rate information returned by AMM.withdraw() under certain conditions; full severity breakdown not visible in snippet.[14]
Fix status
Remediation status across all issues Not verifiable as of 2026-09-03 from the excerpt; ChainSecurity report likely includes detailed fix tracking.
Evidence (1)

audit

two sources

ChainSecurity has multiple independent audits for Curve’s stablecoin stack and scrvUSD, which are tightly coupled with Curve DEX liquidity flows. Scopes:

  • Curve Stablecoin (crvUSD) – code assessment focusing on solvency, rounding, oracle design, and systemic risk; multiple review iterations.
  • Curve scrvUSD – audit focused on Yearn vault usage, access control, and accounting correctness. Severity & findings:
  • For crvUSD, ChainSecurity reports that all high severity findings were resolved, while some medium and numerous low severity issues remain, judged mostly benign given fixes to severe issues.
  • For scrvUSD, the report states security regarding core subjects is “high”, with the final summary indicating a high level of security. Fix status / deployed code coverage:
  • ChainSecurity explicitly tracks resolved vs. open findings across audit iterations, confirming high‑severity items were fixed in the reviewed codebase.
  • No public bytecode‑matching vs. multi‑chain deployments; whether audited versions match live contracts on Arbitrum, Avalanche, Base, Ethereum, Fantom, Fraxtal, Gnosis, Kava, Monad, OP, Plasma, Polygon, Sonic is Not verifiable as of 2026‑08‑29. These audits materially cover Curve’s stablecoin‑integrated AMM behavior but are not full‑stack attestations of every DEX pool implementation on each listed chain.
Auditor
ChainSecurity
Report date
2024-03-27
Scope
Curve Stablecoin (crvUSD) and scrvUSD vault integration
Evidence (3)

audit

unverified

Curve scrvUSD — ChainSecurity code assessment

Auditor
ChainSecurity
Report date
2024-12-03
Scope
scrvUSD smart contracts, including Yearn-v3-based vault integration, access control and accounting.
Findings
0 critical, 0 high, 1 medium and 2 low. The medium finding was code-corrected; both low findings were acknowledged.
Fix status
Medium finding corrected; two low findings acknowledged. Exact bytecode match to current deployments is Not verifiable as of September 6, 2026.
Report url
https://docs.curve.finance/assets/pdf/ChainSecurity_Curve_scrvUSD_audit.pdf
Report id
doc:0a407518f209e45e
Unresolved critical
0
Unresolved high
0
Evidence (1)

audit

one source

Curve Stablecoin — ChainSecurity cumulative code assessment

Auditor
ChainSecurity
Report date
2025-02-21
Scope
Cumulative assessment across 15 code versions, including Curve stablecoin, PegKeeper V1/V2, LLAMMA, controllers, monetary policies, price oracles, lending factories and related infrastructure; latest reviewed commit dated February 15, 2025.
Findings
The cumulative assessment reports 66 findings across the reviewed versions. All critical and high-severity findings were corrected; remaining exposure includes lower-severity and design/oracle issues, including bad-debt socialization, low-decimal token interest loss, liquidation rounding, L2 oracle manipulation, intermediate-currency value leakage and downward-manipulable vault pricePerShare.
Fix status
All critical and high findings corrected in the reviewed versions. Some medium/low and design findings remained open, partially corrected, acknowledged or risk-accepted. Current deployment bytecode match is Not verifiable as of September 6, 2026.
Report url
https://reports.chainsecurity.com/Curve/ChainSecurity_Curve_CurveStablecoin_Audit.pdf
Report id
doc:190fdb89c322c961
Unresolved critical
0
Unresolved high
0
Evidence (1)

audit

one source

Curve Lending — StateMind audit report

Auditor
StateMind
Report date
2024-04-13
Scope
Curve Lending / LlamaLend; Vault.vy, OneWayLendingFactory.vy, SemilogMonetaryPolicy.vy, CryptoFromPool.vy and Controller.vy, based on commits 5a939431084d... through d64d55877730....
Findings
1 critical, 1 high, 4 medium vulnerabilities were reported. The report focused on lending-market accounting, liquidation, oracle and factory logic.
Fix status
All identified critical, high and medium vulnerabilities were reported as successfully fixed before LlamaLend launch. Exact bytecode match to every current deployment is Not verifiable as of September 6, 2026.
Report url
https://docs.curve.finance/assets/pdf/audits/StateMind_Curve_Lending.pdf
Report id
doc:5e6d02afb311f7c5
Unresolved critical
0
Unresolved high
0
Evidence (2)

audit

one source

Curve Lending / LlamaLend — MixBytes audit report

Auditor
MixBytes
Report date
2024-09-02
Scope
Curve Lending / LlamaLend contracts, including lending factories, vaults, controllers, AMM/oracle components and related Curve stablecoin infrastructure; report covers the reviewed code version and remediation review.
Findings
1 critical, 2 high, 5 medium, 7 low. Critical: inflation attack enabling hard liquidations. High findings included liquidation/oracle and lending-logic risks. The report also records medium and low correctness, oracle, documentation and design findings.
Fix status
Findings are marked fixed or otherwise addressed in the report; the critical inflation finding is documented as fixed in commit 9e20913fb46db6d3774c56b13ba17d6911cb2caa. Exact bytecode match to every current deployment is Not verifiable as of September 6, 2026.
Report url
https://github.com/mixbytes/audits_public/tree/master/Curve%20Finance/Curve%20Lending
Report id
doc:6b4a7fe9b9cfe450
Unresolved critical
0
Unresolved high
0
Evidence (1)

audit

one source

Curve PegKeeperV2 — ChainSecurity audit

Auditor
ChainSecurity
Report date
2024-01-24
Scope
PegKeeperV2 and PegKeeperRegulator, including asset handling, access control, liquidity and price-oracle manipulation vectors.
Findings
0 critical, 0 high, 0 medium and 2 low findings. Both low findings were code-corrected.
Fix status
All reported findings corrected. Exact bytecode match to current deployments is Not verifiable as of September 6, 2026.
Report url
https://reports.chainsecurity.com/Curve/ChainSecurity_Curve_PegKeeperV2_Audit.pdf
Report id
doc:6c39507b51e54ac6
Unresolved critical
0
Unresolved high
0
Evidence (1)

audit

one source

Curve Tricrypto-NG — ChainSecurity audit

Auditor
ChainSecurity
Report date
2023-06-23
Scope
Tricrypto-NG AMM and associated math, pricing and pool-deployment logic.
Findings
1 high, 1 medium and 13 low findings were identified. The high and medium findings were fixed. Low findings were split among fixed, specification-changed, partially corrected, accepted and acknowledged statuses.
Fix status
High and medium findings fixed. Low findings: 9 fixed, 1 specification change, 1 partially corrected, 1 risk-accepted and 1 acknowledged. Current deployment bytecode match is Not verifiable as of September 6, 2026.
Report url
https://reports.chainsecurity.com/Curve/ChainSecurity_Curve_TricryptoNg_Audit.pdf
Report id
doc:cc3ea117e4722c8b
Unresolved critical
0
Unresolved high
0
Evidence (1)

audit

one source

Curve DAO BalanceTimeForwarder (voting forwarder) contract.

Auditor
MixBytes
Report date
2020-07-13
Scope
DAO voting forwarder infrastructure affecting governance of Curve DEX on all chains.[1][3]
Findings
MixBytes report lists vulnerabilities with severities; Curve summary implies all non‑informational findings were remediated in subsequent commits.[1][3][11]
Fix status
Curve docs state the audited commit and refer to deployment after fixes; treated here as marketing claim absent direct bytecode comparison.[3][11][9]
Evidence (2)

audit

one source

Curve DAO Voting.sol (Aragon voting fork) smart contract.

Auditor
MixBytes
Report date
2020-07-22
Scope
On‑chain governance voting logic for Curve DAO on Ethereum; affects parameters for Curve DEX pools across chains.[1][8]
Findings
Audit report notes several issues at different severities in governance mechanics; Curve indicates fixes applied, but public catalog does not enumerate critical/high by count.[1][8]
Fix status
Text in report says issues were addressed in updated code; without deployment verification this remains unverified marketing claim.[1][8][9]
Evidence (2)

audit

two sources

Curve DAO Voting Forwarder

Auditor
MixBytes
Report date
2022-07-13
Scope
BalanceTimeForwarder.sol DAO voting forwarder contract (Ethereum governance infrastructure; whether exact audited bytecode is deployed on other listed chains Not verifiable as of 2026-09-03).
Findings
Several troublesome issues identified; detailed severity breakdown not in snippet. Final assessment: no remaining vulnerabilities after fixes.[6][9][12]
Fix status
All identified issues were fixed or otherwise addressed; MixBytes states the fixed contract has no vulnerabilities according to their analysis.[6][9][12]
Evidence (2)

audit

one source

Curve DAO Voting (Aragon Voting)

Auditor
MixBytes
Report date
2022-07-22
Scope
Aragon‑based Voting.sol governance contract for Curve DAO (Ethereum; deployment/bytecode match on other chains Not verifiable as of 2026-09-03).
Findings
“Several troublesome issues” found and addressed; final assessment claims no remaining vulnerabilities in fixed contract.[7]
Fix status
All reported findings acknowledged or fixed; MixBytes states the fixed Voting.sol has no vulnerabilities.[7]
Evidence (1)

audit

two sources

Curve’s official audit catalog lists MixBytes across DAO, DEX, lending and crvUSD components. Relevant scopes for the DEX stack:

  • Aragon voting fork / DAO voting – governance contracts used for Curve DAO voting; MixBytes reports in 2022.
  • Curve Stablecoin (crvUSD) & LLAMMA – audits in Apr–Jun 2023 with three auditors; covers solvency, liquidation and AMM mechanics which are tightly integrated with Curve pools.
  • Curve Lending (TwoWayLendingFactory, hybrid vaults) – audits Feb–May 2024 with multiple re‑audits to July 2024; includes interactions with Curve pools and vault‑style DEX liquidity. Severity & findings:
  • MixBytes crvUSD and lending reports describe inflation attacks, liquidation edge cases and numerical/rounding risks, typically classified medium–high in text, all marked as fixed in specific commits (e.g., commit 9e20913f… for an inflation‑attack fix).
  • Final DAO voting reports state the fixed contract doesn't have any vulnerabilities according to our analysis, implying no remaining critical/high findings at report time. Fix status / deployed code coverage:
  • MixBytes README files map findings directly to commit hashes marked as “Final commit” or "commit for re‑audit", indicating fixes were implemented in the reviewed code.
  • Whether these exact audited commits match the currently deployed bytecode on each chain is Not verifiable as of 2026‑08‑29. Scope spans Ethereum‑centric core systems (DAO voting, crvUSD, lending) that underpin Curve’s multi‑chain DEX but does not provide chain‑by‑chain attestations for Arbitrum, Avalanche, Base, Fantom, Fraxtal, Gnosis, Kava, Monad, OP, Plasma, Polygon, Sonic.
Auditor
MixBytes
Report date
2023-06-01
Scope
Curve DAO voting, crvUSD/LLAMMA, lending & hybrid vaults (primarily Ethereum)
Evidence (5)

audit

one source

Curve Stablecoin (crvUSD)

Auditor
MixBytes
Report date
2023-09-04
Scope
crvUSD stablecoin core contracts (on Ethereum and possibly other Curve‑supported chains; exact chain and bytecode coverage Not verifiable as of 2026-09-03).
Findings
2 CRITICAL, 2 HIGH, 4 MEDIUM, 6 LOW severity findings during audit; all findings were either acknowledged or fixed by Curve.[13]
Fix status
MixBytes reports all findings acknowledged or fixed by client; post‑remediation version judged acceptable.[13]
Evidence (1)

audit

one source

Stableswap‑NG (next‑generation stable pool factory / implementation used across Ethereum and L2s).

Auditor
MixBytes
Report date
2023-11-01
Scope
NG pool implementation on Ethereum; same codebase underpins NG pools deployed on Arbitrum, Optimism, Polygon, Base, and other chains, but bytecode match to those deployments is Not verifiable as of 2026-09-04.[4][6]
Findings
MixBytes report is referenced by Infrared and Curve docs; both state that issues found were addressed before/soon after October 2023 factory deployment.[1][3][4][14]
Fix status
Infrared summary describes Stableswap‑NG as audited with fixes applied; without on‑chain bytecode check this is treated as marketing claim.[4][9]
Evidence (2)

audit

unverified

crvUSD stablecoin and lending infrastructure, including PegKeeper V2 and Savings‑crvUSD (scrvUSD).

Auditor
MixBytes & ChainSecurity
Report date
2023-06-05
Scope
crvUSD core contracts on Ethereum; later infrastructure (PegKeeperV2 2023-12-12; ChainSecurity infra 2024-01-24; scrvUSD 2024-12-03) audited as well. Applicability to deployments on non‑Ethereum chains is Not verifiable as of 2026-09-04.[3]
Findings
MixBytes initial audit and subsequent ChainSecurity audits focus on liquidation logic, peg mechanisms, and savings accounts; Curve’s catalog states issues were remediated, but numbers of critical/high findings are not summarised.[1][3]
Fix status
All stablecoin‑related audits are presented as completed with fixes; absence of independent issue tracking makes this a marketing claim.[1][3]
Evidence (2)

audit

one source

Quantstamp — Curve DAO / CRV Liquidity Mining Audit

Auditor
Quantstamp
Report date
2020-08-05
Scope
Initially LiquidityGauge.vy and GaugeController.vy; later diff review for LiquidityGaugeReward and VestingEscrow.
Findings
1 high, 2 medium, 6 low, 7 informational/undetermined in the initial report; later updates added informational findings. High: possibility of missing rewards.
Fix status
Update reported 4 fixed, 2 acknowledged, 2 false positives removed, and unresolved findings including missing input checks and claimable_reward semantics.
Evidence (1)

audit

one source

Curve CRV Liquidity Mining & CurveDAO reward mechanism

Auditor
Quantstamp
Report date
2020-08-18
Scope
Vyper smart contracts for LiquidityGauge, GaugeController, LiquidityGaugeReward, VestingEscrow controlling CRV reward distribution (Ethereum mainnet; use or adaptation to Arbitrum, Avalanche, Base, Fantom, Fraxtal, Gnosis, Kava, Monad, OP, Plasma, Polygon, Sonic Not verifiable as of 2026-09-03).
Findings
11 issues: 1 high, 1 medium, 1 low, 1 undetermined, 7 informational, plus best‑practice recommendations.[1][15]
Fix status
Several issues, including all high‑risk issues, were fixed by Curve before final report; Quantstamp states fixes were implemented and communicated.[1][15]
Evidence (2)

audit

one source

Curve Finance Liquidity Pool (AMM contracts, diff assessment)

Auditor
Quantstamp
Report date
2020-10-20
Scope
Curve liquidity pool / StableSwap AMM smart contracts diff on Ethereum (exact pools not fully visible; reuse or porting to other chains Not verifiable as of 2026-09-03).
Findings
4 issues total: 0 high, 1 medium, 2 low (plus one more category indicated but not fully visible). Only 1 issue marked resolved in the excerpt; others pending at report time.[10]
Fix status
Medium‑severity issue noted as resolved; some low‑severity issues remained unresolved at report snapshot.[10] Current status and deployment coverage Not verifiable as of 2026-09-03.
Evidence (1)

audit

two sources

Curve’s docs list multiple DAO/DEX audits by Trail of Bits; reports cover Curve DAO, stablecoin pools and core AMM logic, primarily on Ethereum mainnet. Key ones relevant to the DEX:

  • Curve DAO / core contracts – security assessments in Jan 2020 and Jun–Jul 2020, covering Curve DAO, governance, and associated Curve pools. Severity & findings (DEX/DAO-related):
  • Reports describe several low–medium severity issues; public summaries emphasize that identified issues were fixed in follow‑up audits.
  • No public mention of unresolved critical issues for the audited DAO/DEX code. Fix status / deployed code coverage:
  • Follow‑up Trail of Bits audit explicitly states Curve "correctly fixed the reported issues" from the first audit, indicating fixes were merged in audited commits.
  • Bytecode‑match vs. deployed contracts across Curve’s many chains is Not verifiable as of 2026‑08‑29 (no on‑chain tooling this run). Scope clearly focuses on DAO & DEX logic, but chain‑specific deployments (Arbitrum, Avalanche, Base, Fantom, Fraxtal, Gnosis, Kava, Monad, OP, Plasma, Polygon, Sonic) are not individually attested in the public reports – extrapolation from Ethereum audits only.
Auditor
Trail of Bits
Report date
2020-01-31
Scope
Curve DAO & core DEX contracts (Ethereum)
Evidence (3)

audit

one source

Curve DAO Contracts (follow‑up)

Auditor
Trail of Bits
Report date
2020-07-10
Scope
Curve DAO contracts, second audit iteration (Ethereum; Bytecode-match to currently deployed DAO contracts across listed chains Not verifiable as of 2026-09-03).
Findings
Further issues and recommendations on DAO contracts; specific counts of critical/high/medium not visible in the snippet. Overall, contracts considered secure after remediation.[2][3]
Fix status
Curve team implemented fixes before release; Trail of Bits accepted the remediated version.[2][3]
Evidence (2)

Team & Reputation

founders

two sources

Curve Finance (Curve DEX) was founded and is still led by Michael Egorov, a publicly known, non‑anonymous founder with a long technical track record in crypto infrastructure. Founders & prior projects

  • Michael Egorov – Russian‑born physicist, software developer, and entrepreneur; recognized broadly as the founder and CEO of Curve Finance.
  • Prior projects:
  • NuCypher – privacy‑preserving encryption/infrastructure project; Egorov was co‑founder and CTO, including through Y Combinator.
  • Yield Basis – a later Bitcoin yield protocol launched by Egorov after Curve, focused on sustainable on‑chain returns. These are established, venture‑backed crypto infrastructure projects; no major protocol‑level hacks tied to Egorov’s prior work are reported in the retrieved material (Curve itself has experienced exploits, but that’s outside the scope of this founder‑focused question). Team, public vs. anonymous
  • Egorov has public LinkedIn, media, and podcast presence and writes/appears as “Founder of Curve Finance.”
  • He is active on X (Twitter) under @newmichwill, explicitly branded as Curve founder, with a sizable following.
  • Broader team details (other executives, engineers) are not systematically disclosed in retrieved independent profiles; Curve historically presents itself as a protocol rather than a traditional corporate org chart. Not verifiable as of 2026‑09‑04. Jurisdiction, office, and corporate reality
  • Multiple profiles describe Curve Finance as a Swiss‑based company, with Egorov as CEO of “Curve Finance” or “Curve Finance Labs.”
  • A California Court of Appeal case references Swiss Stake GmbH, an entity founded by Egorov to “facilitate the advancement of Curve Finance,” indicating a formal corporate vehicle used in a Swiss/European context and involvement in US litigation with venture firms.
  • Physical office address, exact Swiss canton, and detailed corporate filings are not visible in the retrieved data; therefore any specific office location, onshore/offshore tax status, or number of employees is Not verifiable as of 2026‑09‑04. Reality check: real business vs. web front
  • Evidence of:
  • Named founder with long‑running, cross‑checked public identity.
  • Prior VC‑backed project (NuCypher) and further protocol launches (Yield Basis).
  • Formal entities (e.g., Swiss Stake GmbH) engaged in multi‑year court proceedings.
  • Ongoing public media, podcast, and education content under corporate branding (Curve Finance Labs). Taken together, Curve looks like a real, founder‑led business with corporate entities and extensive public footprint, not a purely anonymous web front. Detailed corporate structuring (group entities, ownership, regulatory status) remains Not verifiable as of 2026‑09‑04.
Evidence (14)

general reputation

two sources

Curve Finance (Curve DEX) has a mixed but generally serious, systemically important reputation: widely used, no fraud/rug-pull history, but significant concerns around founder leverage, past exploits, and complex risk profile. Founders & key reputation issues

  • The main founder is Michael Egorov, whose large, heavily collateralized CRV borrowing across multiple lending protocols (Aave, Fraxlend, Inverse, Cream, Silo, etc.) has repeatedly created systemic risk narratives for DeFi, with debts in the tens of millions of USD backed by hundreds of millions of CRV.
  • In 2023, Egorov’s positions were close to liquidation and risk teams (e.g., Gauntlet on Aave) recommended freezing the Aave v2 CRV market to avoid protocol bad debt, underscoring concern about concentration and governance-token risk.
  • He responded by selling over 100M CRV OTC to investors to repay loans and later fully cleared his Aave debt, but still had sizable exposure on other protocols.
  • Media and research pieces frame this not as fraud, but as founder risk and misaligned incentives (large personal leverage using the protocol’s governance token), seen as a key reputational weakness. Exploits, security, and operational reputation
  • Curve has suffered major pool exploits (e.g., 2023 issues in certain pools and lending pools affecting CRV price, with over $60–100M at risk or lost), which triggered sharp CRV dumps and aggravated Egorov liquidation risk.
  • These incidents damaged short‑term sentiment but did not lead to protocol abandonment; Curve remained a core DeFi venue. Claims about full security posture and audits across all chains/contracts are Not verifiable as of 2026‑09‑04. Legal / regulatory / sanctions
  • A long‑running civil dispute with venture capital firms over an investment arrangement ended with a court victory for Egorov, as a California appellate court upheld that California lacked jurisdiction due to Swiss law/jurisdiction clauses, rejecting the VCs’ appeal. This reflects litigation around fundraising, not fraud by Curve itself.
  • There is no public record in the gathered data of regulatory enforcement actions, criminal charges, or sanctions against Curve or its founder; broader regulatory status is Not verifiable as of 2026‑09‑04. Sentiment & unresolved concerns
  • Curve is viewed as a foundational DeFi protocol but with ongoing concerns:
  • Concentrated governance and token holdings in the founder’s hands.
  • History of large, complex debt positions posing contagion risk when CRV price falls.
  • Past exploits and complexity across many chains/pools.
  • No evidence of rug‑pull or intentional fraud was found, but founder leverage, governance concentration, and security track record are persistent, unresolved risk factors. On‑chain verification of TVL distribution, chain‑by‑chain exposures, and detailed auditor history is Not verifiable as of 2026‑09‑04.
Evidence (8)

Economy

TVL: $1.3B

model

two sources

Economic model — Curve DEX (reviewed September 6, 2026)

  • Strategy/assets in: Permissionless AMMs: StableSwap pools for stable/pegged assets, CryptoSwap pools for more directional assets, and crvUSD/LLAMMA and LlamaLend markets. LPs deposit stablecoins, LSDs, wrapped assets or volatile tokens and receive LP tokens; gauges may add CRV incentives.
  • Yield source: Trading fees are the primary organic source. Subsidized yield consists mainly of CRV/gauge emissions and potentially third-party incentives. Some lending products introduce interest income and external collateral/borrower risk. Fee parameters vary by pool; legacy documentation and audits commonly describe a 50% admin-fee share, but this is not a universal current parameter.
  • Risk posture: Stable pools are relatively market-neutral only while assets remain pegged; CryptoSwap, LSD and crvUSD collateral pools are directional and carry depeg, oracle, impermanent-loss and liquidation risks. Curve itself does not impose protocol-wide leverage, looping or restaking, but LlamaLend/crvUSD supports overcollateralized borrowing and can create leverage externally.
  • Lockups/withdrawal: Ordinary LP liquidity is generally withdrawable subject to pool liquidity, slippage, imbalance fees and transaction limits. veCRV governance locks are time-based; gauge deposits are separately withdrawable. crvUSD borrowers face collateral bands/soft liquidation rather than an ordinary LP lock.
  • Fees/revenue: DeFiLlama reports approximately $64.1m annualized fees, $4.11m fees over 30 days, $1.2m revenue over 30 days and $729.7k incentives over 30 days. These are aggregator figures, not on-chain verified.
  • TVL: DeFiLlama’s displayed TVL for the user-specified chains sums to approximately $1.330bn: Ethereum $1.276bn; Fraxtal $9.96m; Arbitrum $9.51m; Base $8.99m; Monad $8.70m; Polygon $5.67m; OP Mainnet $2.84m; Plasma $2.75m; Avalanche $2.52m; Gnosis $2.10m; Fantom $0.91m; Sonic $0.20m; Kava $0.08m. Product-level TVL, historical trend, APY history/volatility and Dune-vs-DeFiLlama reconciliation: Not verifiable as of September 6, 2026. Contradiction: The prior note says assets are not rehypothecated; this is too broad. Plain AMM liquidity is not lending collateral, but Curve’s documented lending pools/LlamaLend explicitly add lending and external-exposure pathways. Assessment: Organic yield is fee-dependent but incentive subsidies remain material; sustainability is therefore pool- and emissions-dependent, not protocol-wide. Structured fields: organic_yield_pct: null; leverage_ratio: null.
Evidence (5)

reserves

unverified

Assessment — as of September 6, 2026 Curve’s reserves are fragmented across at least three DAO-controlled buckets rather than one consolidated balance sheet:

  • DAO Treasury (Ethereum): 0x6508eF65b0Bd57eaBD0f1D52685A70433B2d290B. It receives 10% of designated protocol revenue through the FeeAllocator and is controlled through Curve governance.
  • Community Fund: 0xe3997288987E6297Ad550A69B31439504F513267, historically seeded with 151.5M CRV and now a finite, depleting reserve. A March 2026 governance budget described approximately 7.1M CRV remaining; a later April 2026 proposal cited approximately 845K CRV, indicating either subsequent distributions or inconsistent wallet/accounting scope.
  • Grants multisig: 0xc420C9d507D0E038BD76383AaADCAd576ed0073c; an April 2026 governance source reported approximately 10.4M CRV and 15K scrvUSD. Composition and policy: Reserves are primarily CRV in the legacy Community Fund and crvUSD in the newer Treasury. In July 2026, governance approved moving certain Arbitrum/Base fee-collector crvUSD to the Ethereum Treasury. Governance also approved a Treasury Stable Diversification contract (0x70b3d2c2A508A87f9C18F46fe9ca42307CD021f7) to convert part of Treasury crvUSD into yield-bearing stable assets such as sDOLA and sfrxUSD. Custody/control: Treasury funds remain DAO-controlled; execution is performed through governance-approved contracts, vesting contracts, and multisigs. Emergency DAO access of up to 400,000 crvUSD was proposed for peg defense, creating an operational-control concentration point. > Contradiction / data-quality finding: Published figures conflict materially: approximately 7.1M CRV, approximately 845K CRV, and an older $16M CRV estimate describe different dates and/or reserve scopes. The figures are not a consolidated, independently attested balance sheet. On-chain balances via Dune: Not verifiable as of September 6, 2026. Dune MCP was unavailable; no current cross-chain balance or custody computation is asserted. Attestations: Not verifiable as of September 6, 2026. No independent reserve attestation was identified in the reviewed sources. Liabilities: No consolidated DAO-treasury liabilities statement was identified; crvUSD protocol debt and proposed remediation obligations are separate from treasury liabilities.
Evidence (5)

tokenomics

two sources

Curve DEX (Curve Finance) does have a native token: Curve DAO Token (CRV), used across all supported chains via bridges. Token identity & main contract

  • Name / ticker: Curve DAO Token (CRV).
  • Canonical contract (Ethereum): 0xD533a949740bb3306d119CC777fa900bA034cd52. All other chains use bridged/wrapped CRV; exact addresses per chain are not independently verifiable here. Supply, market cap, FDV (as-of ~2026-09-02, off-chain)
  • Max / fixed total supply: 3,030,303,031 CRV; no minting beyond this cap.
  • Current total supply: ~2.40–2.42B CRV.
  • Circulating supply: ~1.55B CRV (~64% of total).
  • Market cap: ≈$540M at price ~$0.35.
  • FDV: ≈$845M. All figures are aggregator-based, not on-chain verified; treat as indicative only. Token utility & governance role
  • Governance: CRV is the governance token of Curve DAO, controlling gauges, pool parameters, and proposals via vote-escrowed CRV (veCRV).
  • veCRV lock model: Users lock CRV for 1 week–4 years to receive non-transferable veCRV, which decays as lock expiry approaches.
  • Gauge voting: veCRV holders direct weekly CRV emissions to specific pools (liquidity gauges), determining where inflation goes.
  • Boosts: Locked veCRV boosts LP rewards (up to ~2.5x).
  • Revenue share: veCRV holders receive 50% of trading fees across Curve pools, paid in 3CRV and more recently crvUSD. Emissions, inflation, unlocks
  • Schedule: Initial inflation ~274M CRV/year (2020) with annual reduction of ~15.9–16%. Emissions continue for ~200+ years.
  • Daily emissions: Initially ~2M CRV/day, declining over time.
  • Community emissions: 62% of total supply (~1.88B CRV) allocated to LPs via gauges.
  • Team / investor vesting: 30% (~909M) to shareholders (team + investors), 2–4 year vesting; reported as fully unlocked since ~Aug 2024. On-chain confirmation of unlock completion: Not verifiable as of 2026-09-04.
  • Employees: 3% with 2-year vesting.
  • Community reserve: 5%. Allocations & concentration
  • Aggregate allocation (protocol resources):
  • Community LPs: 62%.
  • Shareholders (founders/investors): 30%.
  • Community reserve: 5%.
  • Employees: 3%.
  • Detailed top-holder concentration, insider wallet labels, and cross-chain holder mapping: Not verifiable as of 2026-09-04. Control functions (mint / blacklist / fee-switch)
  • Emissions (minting up to the cap) are controlled via DAO-approved liquidity gauges; veCRV voters steer emissions, while contracts implement the schedule.
  • Specific admin powers such as address blacklists, emergency pause, or unilateral fee-switch settings per chain: Not verifiable as of 2026-09-04. Liquidity & listings
  • CRV is widely listed on major CEXs (e.g., Binance) and DeFi venues; Binance reports total and circulating supply and distribution metrics.
  • Curve itself and other DEXs provide deep CRV liquidity, especially on Ethereum, Arbitrum, Polygon, Optimism, but exact per-chain TVL and depth are Not verifiable as of 2026-09-04 without direct on-chain data. Contradiction callout
  • Some sources differ on category percentages (e.g., team/investor shares and early users vs. LPs). Where they conflict, treat the protocol’s resource page as the canonical design, but all such figures remain unverified marketing claims absent raw on-chain validation.
Evidence (14)

Stress scenarios

stress scenario - bitcoin price falls below $10000

two sources

Not verifiable as of 2026-09-04. With Dune unavailable, I cannot quantify Curve DEX’s chain-by-chain TVL, exposure, or liquidation risk under a BTC < $10,000 shock across Arbitrum, Avalanche, Base, Ethereum, Fantom, Fraxtal, Gnosis, Kava, Monad, OP Mainnet, Plasma, Polygon, and Sonic. The web results only confirm that Curve has historically faced smart-contract and Vyper-related exploit risk, but they do not provide the on-chain balance sheet needed for a stress test, and several search hits are unrelated market commentary rather than protocol-specific risk data.

Curve’s own security page confirms a formal vulnerability-reporting channel, but that does not establish current exposure metrics or stress losses. The only defensible stress conclusion from the available evidence is qualitative: a BTC collapse to below $10,000 would likely increase broader DeFi deleveraging pressure, but the magnitude of Curve DEX impact cannot be verified from the supplied sources alone. Not verifiable as of 2026-09-04.

Evidence (4)

stress scenario - largest collateral depegs 20%,

one source

Curve DEX is a multi-chain AMM, so a 20% collateral depeg stress on the largest collateral is only partially assessable from the provided sources. The clearest verified consequence in the materials is for crvUSD, where Curve’s own governance post and an independent risk model both identify stablecoin/collateral depegs as a primary risk driver; the risk-model paper explicitly simulates a 20% USDC depeg and notes liquidation spikes under that scenario.

Evidence (2)

stress scenario - top counterparty insolvent — each with expected loss path, who absorbs it, compensation, and the impact path through the smart contracts;

two sources

Curve DEX does not have a classic external counterparty whose insolvency is directly absorbed by the protocol; the main loss path is market/depeg risk inside the pool rather than credit risk. For standard Curve liquidity pools, the contracts are described as immutable and noncustodial, so LPs bear the economic loss from adverse price moves or a failed/depegged asset, not a rescue mechanism by the protocol. For a top counterparty insolvent stress, the expected loss path is:

  • A token in the pool (or a borrowed asset in Curve Lending) becomes impaired or unredeemable.
  • Arbitrage and rebalancing push the bad asset out of the pool at distressed prices, crystallizing LP losses.
  • In Curve Lending, LLAMMA soft-liquidation can progressively convert collateral into crvUSD; if the market moves too far, positions can be hard-liquidated, and in extreme cases lenders can face bad debt / shortfall. Who absorbs it:
  • LPs absorb losses first in DEX pools, because the pool pricing formula revalues the basket and there is no stated backstop in the docs.
  • Borrowers absorb losses in lending via collateral seizure / liquidation dynamics.
  • Lenders / vault-share holders can absorb residual bad debt if collateral is insufficient; one audit explicitly notes that when bad debt exists, vault shares can still redeem at full value while the lending market becomes insolvent toward the last shares redeemed. Compensation:
  • No contractual compensation is documented for DEX LP insolvency/depeg loss; the docs instead frame this as a known risk of the design.
  • In lending, liquidation mechanics are the built-in mitigation, but they do not fully insulate lenders from bad debt in extreme scenarios. Impact path through smart contracts:
  • Pool math / AMM pricing absorbs the toxic asset first, then LP balances reprice downward.
  • In LLAMMA, collateral migrates through soft-liquidation bands; if losses deepen, the position hard-liquidates and may still leave a shortfall.
  • Governance / admin cannot be assumed to rescue users; Curve’s docs emphasize immutability and noncustodial operation for pools. Not verifiable as of 2026-09-04: chain-by-chain exposure split for Arbitrum, Avalanche, Base, Ethereum, Fantom, Fraxtal, Gnosis, Kava, Monad, OP Mainnet, Plasma, Polygon, and Sonic.
Evidence (3)

stress scenario - committed fraud by the DAO or owners

two sources

For the stress scenario of committed fraud by the DAO or owners, there is no verifiable evidence in the provided sources that Curve DAO or its owners committed fraud. The available material instead describes a smart-contract / compiler vulnerability exploit affecting Curve pools, not an insider-fraud event. The strongest documented incident is the July 2023 Curve exploit, where attackers drained multiple liquidity pools after a Vyper reentrancy issue; sources attribute the losses to the vulnerability and attacker activity, and state that the Curve DAO did not control user funds in a way that would make this an owner-committed fraud case.

A separate source notes a DAO vote over whether to return recovered funds, which is governance-related and not evidence of fraud by the DAO or owners. Assessment for this stress scenario:

  • Fraud by DAO/owners: Not verifiable as of 2026-09-04
  • Relevant historical loss event: exploit/vulnerability, not confirmed fraud
  • Implication for risk analysis: treat this as technical compromise risk, not an established governance fraud risk, unless additional primary evidence emerges
Evidence (4)

stress scenario - primary yield source negative 30d,

two sources

Curve DEX’s primary yield source is not verifiable as of 2026-09-04 from the provided sources alone, so I cannot confirm a negative 30-day reading for a specific yield stream. The closest directly relevant evidence is that Curve’s yields can be composed of swap fees, CRV emissions, and external incentives, and that fee-only stablecoin yields are often modest while rewards can dominate APY. Curve’s own weekly yield page also shows that yields vary sharply by market, chain, and incentive setup, which means a single protocol-wide “primary yield source” is not a stable published figure.

For a stress scenario, the practical implication is that if the primary yield source turns negative over 30 days, Curve LPs would be relying on incentives or token emissions to offset poor fee performance, and if those rewards are weak or absent the net return can compress materially. In Curve-style liquidity provision, adverse price movement or thin trading can leave LPs with lower realized returns, while incentives may temporarily mask the weakness. Chain scope: the user listed Arbitrum, Avalanche, Base, Ethereum, Fantom, Fraxtal, Gnosis, Kava, Monad, OP Mainnet, Plasma, Polygon, and Sonic, but no source here provides a verified cross-chain 30-day yield breakdown for Curve on those networks. Therefore, the chain-specific exposure is Not verifiable as of 2026-09-04.

If you want, I can turn this into a tighter risk note framed as: “negative primary yield over 30d → incentive-dependent carry, lower LP retention, and higher unwind risk.”

Evidence (3)

Governance & Legal

governance

unverified

As of September 13, 2026, Curve is primarily controlled by an Ethereum-based veCRV/Aragon DAO, not a disclosed operating company. veCRV holders govern ownership agents, pool parameters, gauges, treasury/community-fund spending, and upgrades; proposals generally require 2,500 veCRV, remain open for one week, and execute only after the voting period. Cross-chain deployments rely on Ethereum governance plus messaging/xGov infrastructure. This is real token-holder governance, but voting power is economically concentrated in large veCRV lockers and delegation/convex-style intermediaries.

Top holders, voting concentration, and per-chain exposure are Not verifiable as of September 13, 2026 because Dune MCP was unavailable. Control is not fully permissionless. The Emergency DAO is a 5-of-9 multisig with authority to freeze/kill gauges or pools and, under governance-approved authorizations, conduct bounded emergency actions.

A February 2026 proposal authorized it to deploy up to 400,000 crvUSD from the DAO treasury and adjust specified pool parameters during severe stress. This is an emergency bypass without the normal governance delay, so the DAO is substantive but not the sole immediate control layer. The standard governance path has a one-week execution delay (168 hours) between vote start and executable result; a separate universal smart-contract timelock delay is Not verifiable as of September 13, 2026.

Current multisig signer identities and independence are Not verifiable as of September 13, 2026; the documented structure is 5-of-9, with historical governance records naming nine members. No company-controlled entity, jurisdiction, registration number, directors, or applicable corporate ToS were established. Frontend and development operations appear delegated to DAO-approved contributors such as Swiss Stake, but their ability to alter core contracts is constrained by DAO-controlled agents. Contradiction / risk finding: prior records characterized admin_can_drain as false and emergency authority as limited; the 2026 treasury authorization shows the Emergency DAO can move a bounded amount of DAO funds without a fresh token-holder vote.

This does not establish the ability to drain depositor LP balances, but it is a material treasury-control exception.

Timelock
Yes
Timelock delay hours
168
Multisig threshold
5
Multisig owners
9
Admin can drain
No
Emergency bypass
Yes
Dao governance
Yes
Evidence (4)

legal & regulatory

two sources

Entity & jurisdiction

  • On-chain governance: Curve is governed by the Curve DAO, a decentralized system controlled by veCRV holders; no separate foundation exists.
  • Off-chain development company: Swiss Stake AG “created Curve and is still contracted to run development” and is based in Switzerland; it has no formal control over the DAO, treasury, or protocol parameters.
  • Some court filings involving Curve’s founder reference Swiss jurisdiction for investment contracts, reinforcing Switzerland as the main off-chain nexus. Legal structure vs. actual risk
  • Legal structure is a DAO plus a Swiss development contractor, with protocol ownership and admin functionality controlled by on-chain governance addresses (Community DAO, Parameter Admin, Emergency DAO).
  • This distributes control but does not eliminate regulatory exposure for key individuals or entities seen as “operators” or “developers,” especially in jurisdictions that look through DAOs. Classification
  • Curve is generally described as a decentralized automated market maker (AMM) / DEX governed by CRV/veCRV holders.
  • No clear official classification by a major regulator (e.g., SEC, ESMA) is visible in recent public sources. Not verifiable as of 2026-09-04. KYC/AML
  • Core Curve DEX smart contracts are permissionless; users interact via wallets without embedded KYC.
  • Third‑party platforms referencing “Curve” and imposing KYC/AML (e.g., centralized interfaces or exchanges with Curve-branded products) are distinct entities and not native to the Curve DAO protocol itself. Any KYC/AML obligations stem from those platforms, not from on-chain Curve. Terms of service / restrictions
  • Curve’s own docs emphasize DAO control and do not present a conventional ToS with user age, residency or asset‑trading restrictions comparable to centralized exchanges.
  • Any ToS‑style restrictions found in Curve‑branded CeFi products (e.g., e‑money institutions) are for different entities and not for the Curve DEX. Warnings, enforcement, sanctions, court cases
  • No direct regulatory enforcement action against Curve DAO or Swiss Stake AG is identified in recent public data. Not verifiable as of 2026-09-04.
  • A civil dispute involving Curve’s founder and VC firms resulted in a jurisdictional ruling (California court finding Swiss jurisdiction) but was not a regulatory enforcement case against Curve itself.
  • Searches of major sanctions lists (e.g., OFAC consolidated lists) show no listing of Curve DAO, Curve Finance, Swiss Stake AG, or CRV token as sanctioned entities/tokens. Not verifiable as of 2026-09-04. Data protection
  • On-chain Curve DEX does not collect personal data; interactions are pseudonymous wallet addresses.
  • Any data‑protection obligations relate to off-chain services (web front‑ends, CeFi products) and would follow their local laws (e.g., EU GDPR for EU‑based services), but concrete policies for the DAO itself are not clearly documented in public sources. Not verifiable as of 2026-09-04. Chain coverage
  • Curve operates the same DAO‑governed AMM design across multiple chains (Ethereum L1 and L2s, alternative L1s), but legal and regulatory exposure is anchored in the Swiss development company and globally distributed DAO participants, not in any single chain jurisdiction.
Sanctioned
No
Entity
Curve DAO / Swiss Stake AG (development company)
Jurisdiction
DAO: none / global; development company: Switzerland
Evidence (12)

legal registries

two sources

No exact GLEIF LEI record for 'Curve DAO', 'Swiss Stake AG', 'Curve DEX'. OFAC SDN screening of 'Curve DAO', 'Swiss Stake AG', 'Curve DEX': no match. SEC litigation and administrative release feeds: no mention.

Screened names
  • Curve DAO
  • Swiss Stake AG
  • Curve DEX
Sanctioned
No
Evidence (4)

Stability

stability

one source

Curve issues its own stablecoin, crvUSD, so own_stablecoin = true. A depeg did happen: the last verifiable event found was on 2023-08-03, when crvUSD briefly fell by as much as 0.35% before regaining peg. The exact total number of depeg events and the worst historical depeg beyond that incident are Not verifiable as of 2026-09-06; therefore stable = null, depeg_count = 1 minimum, max_depeg_pct = 0.35 minimum, and last_depeg_date = 2023-08-03.

CrvUSD is the only stablecoin identifier clearly evidenced here, so stablecoin_ids = ["crvUSD"].

Own stablecoin
Yes
Depeg count
1
Max depeg pct
0.35%
Last depeg date
2023-08-03
Stablecoin ids
  • crvUSD
Evidence (2)

Risks & Strengths

risks

two sources

Curve’s main risks are concentrated in smart-contract/toolchain security, permissionless pool and token integration, oracle and stablecoin feedback loops, cross-chain messaging, and governance concentration. Historical exploitation and current cross-chain expansion make these risks material, although audits, timelocks, bridge limits, and ongoing risk-provider onboarding reduce—but do not eliminate—exposure. On-chain TVL, exposure by chain, and current concentration metrics: Not verifiable as of September 5, 2026.

RiskImpactSeverityProbabilityMitigation in placeResidual risk
Smart-contract and compiler vulnerabilitiesA flaw in pool logic, compiler output, or upgradeable components can cause direct LP or protocol-fund loss across multiple deployments; the July 30, 2023 Vyper incident demonstrates correlated failure potential.HighMediumAudits, security reviews, incident procedures, restricted implementations, and ongoing risk-provider onboarding are in place.High-impact unknown vulnerabilities remain possible; audits are time-boxed and do not guarantee safety.
Permissionless pool and token integrationFactories allow permissionless pool deployment and support diverse assets; malicious, defective, or economically unsafe tokens can attract liquidity and create user losses or reputational contagion.HighMediumFactory parameter validation, audited blueprints, governance-controlled gauges, and selective emissions removal reduce incentives for unsafe pools.Medium-High; permissionless deployment and asset-specific risks remain.
Oracle manipulation and depeg feedbackLow-volume or thinly arbitraged pools can provide stale or manipulable prices; collateral liquidations may reinforce price declines when Curve pools are the primary liquidity source.HighMediumTime-weighted/oracle mechanisms, collateral caps, and recommendations to use deeper external oracles are documented.High for illiquid collateral, long-tail assets, and stressed markets.
Cross-chain bridge and messaging failureCurve’s multi-chain architecture depends on messaging, bridges, and cross-chain governance; provider failure, misconfiguration, or chain outage can misroute rewards, freeze transfers, or create inconsistent state.HighMediumLayerZero plus emergency-DAO fallback, reduced bridge daily limits, and bridge-pause procedures are being used.Medium-High; third-party and chain-specific dependencies remain.
Governance concentration and captureVoting power can concentrate in liquid-locker ecosystems, enabling coordinated parameter, gauge, or emissions decisions that may disadvantage LPs or redirect incentives.HighMediumveCRV lock periods, quorum requirements, timelocks, DAO voting, and proposed delegation controls provide checks.Medium-High; concentration, voter apathy, and bribery remain structural risks.
Evidence (5)

strengths

two sources

Curve DEX’s top strengths are: 1) Very low slippage for stablecoin and other pegged-asset swaps, driven by its StableSwap design; 2) Low fees relative to general-purpose DEXs; 3) Capital efficiency / deep liquidity, meaning large trades can clear with less price impact; 4) Passive liquidity provision, since LPs do not need to manage price ranges or rebalance manually; and 5) Multi-chain deployment and broad liquidity footprint, which helps users find liquidity across several ecosystems. These strengths are repeatedly emphasized in Curve’s own docs and in independent reviews focused on its stablecoin-specialized AMM design.

Evidence (4)

Methodology & Limitations

  • On-chain metrics: not verifiable — Dune phase 2 is not enabled.
  • 0 of 25 fact categories not yet collected.
  • Fact verifiability: 20 two independent sources, 29 one source, 14 unverified.
  • Oldest fact verification date: 2026-08-29.