Euler V2

Orange · 61/100

Executive summary

Euler V2 is a modular, permissionless DeFi lending protocol deployed across ten EVM chains, scoring 59/100 (orange band) with high data confidence (86/100) and a -10 penalty for unresolved incident remediation.

  • Security: 29+ audits from 12+ firms (Certora, ChainSecurity, Spearbit, yAudit, OpenZeppelin, others) plus $1.25M bug bounty; 2 critical and 5 high-severity issues found and fixed pre-launch, with no critical/high/medium findings in post-launch bounty. Formal verification and extensive testing completed, but detailed fix status and deployed-code match are not verifiable as of September 2026 for many reports.
  • Incidents: Euler v1 suffered a $197M exploit in March 2023 (funds recovered, users reimbursed). V2 itself has no direct exploit, but two counterparty incidents remain partially unresolved: Stream Finance (November 2025, Plasma deployment wiped out, user loss and full reimbursement not verifiable) and Resolv (March 2026, Foundation backstopped bad debt, users reimbursed). Incident remediation is marked incomplete, triggering the -10 penalty.
  • Governance & custody: Hybrid governance (EUL token, Snapshot/Tally, multisigs, Foundation, Labs); not a pure DAO. Non-custodial vault architecture with user-controlled keys and EVC operator delegation. Timelock documented at 48 hours but emergency bypass and per-chain role configuration are not verifiable. Euler Foundation (Cayman) and Euler Labs Ltd (UK) are the operating entities; Foundation multisig signer details not verifiable.
  • Top risks: Oracle manipulation/misconfiguration (high severity, medium probability; vault-specific, thin-liquidity assets most exposed). Permissionless vault creation means heterogeneous risk: each vault's curator, LTV, caps, oracle, and governance determine safety. Counterparty/stablecoin depeg risk (USDC depeg monitored in 2023; AXUSD RWA and external protocol exposure not verifiable). Modular design reduces contagion but creates fragmented, vault-level risk that is hard to aggregate. Cross-chain TVL, exposure, and current reserve/liability data are not verifiable as of September 2026.
  • Strengths: Modular architecture with strong vault isolation limits systemic contagion. Composable EVC enables flexible collateral use across vaults. Permissionless market creation supports long-tail assets. Advanced liquidation logic and sub-accounts improve capital efficiency. Post-exploit relaunch with heavy security investment ($4M+) and transparent audit disclosure.
  • Unverified: Current chain-by-chain TVL, vault exposures, oracle states, multisig signer sets, timelock status, reserve balances, liabilities, and deployed-code audit coverage are not verifiable as of September 2026. Stream Finance and Resolv incident user losses and full reimbursement details are not verifiable. Exact mapping of 29+ audits to live deployments and bytecode match is incomplete.
  • Recommended exposure: Conservative allocation only, treating Euler V2 as a higher-risk, post-exploit relaunch with strong but unverified remediation. Limit exposure to DAO-curated vaults on Ethereum/Base/Arbitrum with liquid, blue-chip collateral (ETH, WBTC, major stablecoins) and verified oracle routes. Avoid third-party-curated vaults, thin-liquidity assets, RWA markets, and chains with incomplete audit coverage until on-chain verification and incident closure are confirmed. Size position to tolerate vault-level loss (e.g., ≤2–5% of portfolio) and monitor for oracle/liquidation stress.
  • Open questions: Verify current multisig signers, timelock configuration, and emergency-bypass scope per chain. Confirm Stream Finance and Resolv incident final user reimbursement and Foundation loss absorption. Obtain chain-by-chain TVL, vault exposure, and oracle-route audit coverage. Validate deployed bytecode matches audited commits for all ten chains. Clarify DAO treasury reserves, liabilities, and Fee Flow revenue-share timeline. Assess live liquidation performance and bad-debt history since v2 launch.

Score

Component Weight Raw Points Reason
Security 20% 100 20.0 20 audit(s); fresh audit bonus; active bug bounty bonus
Audits 20% 30 6.0 last full audit 2025-07-30 is older than a year; auditor not in top-20 -20
Incidents 20% 100 20.0 1 open incident(s), $0 at risk (1 with unknown loss) = 0.0% of TVL (threshold 10%)
Governance 20% 75 15.0 a single party can withdraw funds (admin_can_drain)
TVL 20% 2 0.4 TVL $342,536,385 = 2% of reference ($17,538,184,136)
Data confidence 86 7/7 critical categories; 16/49 verified facts; 48/49 fresh (180d)

Identification

protocol identification

two sources

Euler V2 is a modular, permissionless lending protocol using isolated vaults, relaunched after the original Euler Finance exploit, and now deployed across multiple EVM chains. Identification

  • Name: Euler V2 (Euler Finance v2).
  • Category: Non-custodial DeFi lending / money market protocol built around configurable vaults.
  • Website: Euler Finance main site (lending platform description).
  • Docs: Euler V2 protocol introduction and technical documentation (Vault Kit, Vault Connector, oracle).
  • Native token: EUL, Euler’s governance / protocol token; all 27.18M tokens are unlocked with no future vesting.
  • Launch date (v2): Modular Euler V2 launched/relaunched in September 2024 following the 2023 exploit. Chains Independent sources confirm Euler V2 operates multichain, including:
  • Ethereum – protocol originally Ethereum-native; v2 live as of April 2026.
  • Base – Euler v2 explicitly announced as live on Base.
  • Arbitrum – AXUSD lending vault live on Arbitrum using Euler V2.
  • Other chains in scope: A profile of Euler V2 lists Arbitrum, Avalanche, BSC, Base, Ethereum, Hyperliquid L1, Linea, Monad, Plasma, Unichain as active chains with 108 pools across 10 blockchains. Because direct on-chain queries are not available in this run, main contract addresses and explorer verification status are Not verifiable as of 2026-09-04. Design & fork lineage
  • Euler V2 is not presented as a fork of another lending protocol; it is described as a complete architectural rebuild of Euler Finance after the 2023 exploit, with a novel modular vault architecture.
  • Core modules:
  • Euler Vault Kit (EVK) – toolkit to deploy configurable isolated lending vaults for ERC‑20 assets.
  • Ethereum Vault Connector (EVC) – lets vaults be used as collateral for other vaults, enabling cross‑vault composability.
  • Euler Price Oracle (EPO) – oracle component in v2 architecture.
  • Changes vs. Euler v1 include isolated vaults to prevent contagion, modular vault design, and enhanced composability via the EVC; this is explicitly framed as a response to the 2023 exploit risk profile.
  • The team reports Euler V2 as "battle-tested through tens of independent security audits", but without tool access or direct audit URLs, this is an unverified marketing claim rather than confirmed audit coverage.
  • No independent evidence of malicious modifications in third‑party forks of Euler V2 surfaced in the available data; absence of evidence cannot be taken as proof of safety.
Evidence (12)

maturity

two sources

Euler V2 looks like a real product portal, not just a marketing landing page: the docs point users to the live app at app.euler.finance and describe actual wallet connection and protocol workflows such as supplying, borrowing, repaying, and withdrawing. The developer docs also describe a data API, SDK, lens contracts, and composable smart contracts, which indicates a mature integration surface rather than a static brochure site. On product maturity, the public documentation explicitly covers getting started, developer guide pages, and data querying, which is consistent with an operating protocol with live UX and developer tooling.

The docs also reference a hosted HTTP API preview plus subgraphs/indexers for protocol data, and a separate swap API/Swagger UI for the Euler periphery, so an open API does exist in some form. What is not verifiable from the available sources is whether deposits and withdrawals are live on all listed chains, whether any links are broken, or whether any claimed UI metrics are fake; those require direct app inspection or on-chain checks, which are unavailable here. Not verifiable as of 2026-09-04.

Evidence (6)

Security

bug bounty

two sources

Euler V2 has an active bug bounty program on Cantina. It started on 21 Aug 2024 and covers the core components of Euler V2 (EVC, EVK, EPO), supporting components, EulerEarn, EulerSwap, and the web interface. The published reward parameters include smart-contract findings up to $1,000,000 for high-impact issues with a minimum payout of $200,000, medium-impact up to $200,000 with a minimum payout of $50,000, and web-interface findings up to $25,000 for critical issues.

The program page reports 612 findings submitted and a total reward pool of 7,500,000 USDC + rEUL + USUAL. Earlier Euler security material also referenced an Immunefi-era bug bounty, but the current live program is the Cantina one.

Active
Yes
Platform
Cantina
Max payout
$1.0M
Since
2024-08-21
Evidence (3)

counterparty risks

one source

As of September 6, 2026: dependency_failure_active: false — no active public oracle, bridge, stablecoin, custodian, or issuer failure was identified in the reviewed sources; on-chain incident status is Not verifiable as of 2026-09-06. Primary dependency — market-specific oracles and curators. Euler V2 is permissionless: vault creators choose the oracle, collateral links, LTVs, caps, liquidation rules, and governance path. Supported oracle families include Chainlink, Pyth, RedStone, and Chronicle. This materially reduces protocol-wide contagion but creates heterogeneous, vault-specific oracle and curator risk.

Thin liquidity, stale prices, sequencer outages, or manipulated DEX/reference prices could trigger underpriced collateral, bad debt, or liquidations. Stablecoins and RWA. Arbitrum’s AXUSD deployment reports live Euler V2 markets using USDC, USDT, WETH and ARB collateral, while USDY/USTBL RWA markets were described as prepared rather than live. AXUSD therefore introduces issuer, reserve, redemption, and RWA/SPV/legal-enforcement risk in addition to ordinary stablecoin depeg risk. Exact Euler exposure by asset, vault, and chain is Not verifiable as of 2026-09-06. LST/restaking and external protocols. Euler’s architecture can connect staking assets, stablecoin clusters, Earn vaults, and compatible ERC-4626 strategies; however, live exposure to wstETH, weETH, LRTs, Morpho, Aave, or other external protocols is Not verifiable as of 2026-09-06.

Failure scenarios include LST/LRT depeg, validator/slashing or restaking-operator failure, strategy insolvency, and correlated liquidations. Bridges, custodians, CEX/MMs. Ten-chain deployment increases fragmentation, chain halt, sequencer, liquidity, and bridge dependency risk. Exact bridge routes and balances are Not verifiable as of 2026-09-06. No verified dependency on a custodian, CEX, or named market maker was found; exposure is Not verifiable as of 2026-09-06.

Euler’s EUL bridging documentation itself warns that route configuration and peers can change. Contradiction / limitation: claimed or displayed TVL and asset percentages cannot be reconciled against raw on-chain data because Dune is unavailable. Therefore, max_exposure_pct: null.

Dependency failure active
No
Evidence (5)

crypto custody

one source

Euler V2 is organized as a non-custodial, vault-based lending system: users deposit assets into smart-contract vaults and retain control through blockchain transactions rather than handing custody to Euler as an intermediary. The architecture is modular, with EVK vaults holding a single underlying ERC-20 asset per vault and EVC connecting vaults so collateral can be recognized across positions without collapsing everything into one pooled custody account. On withdrawals, the docs say availability depends on vault liquidity and contract limits, so users may not be able to withdraw the full amount immediately if assets are borrowed or otherwise unavailable.

Segregation is therefore partial at the vault level: each vault is isolated by asset and risk surface, but linked through EVC for collateral and liquidation logic, so the safest summary is that custody is segmented by vault rather than pooled centrally. Withdrawal-paused status is not verifiable as of 2026-09-06.

Segregated assets
Yes
Evidence (3)

incident

two sources

Euler V2 is a relaunch after the March 2023 Euler exploit, but V2 itself (across Arbitrum, Avalanche, BSC, Base, Ethereum, Hyperliquid L1, Linea, Monad, Plasma, Unichain) has no publicly reported security or loss incidents since launch as of 2026‑09‑04. Not verifiable on-chain as of 2026‑09‑04. The only major relevant incident is the Euler v1 exploit (pre‑V2):

  • Date: 13 March 2023.
  • Cause: complex smart‑contract exploit involving the eToken collateral logic, missing liquidity-status checks when donating funds, and interaction with flash loans, resulting in under‑collateralized positions and mass liquidations.
  • Loss (at exploit time): about $197–200m in assets (incl. ~$136m stETH, $34m USDC, $18.5m WBTC, $8.8m DAI). Aggregator figures differ slightly but are in this range.
  • Affected: depositors in Euler v1 markets for the above assets on Ethereum; protocol TVL dropped from ~$264m to ~$10m.
  • Response: protocol entered “hibernation” mode, halted new deposits, engaged in negotiations with the exploiter and offered a $1m bounty for information while threatening law‑enforcement escalation.
  • Recovery: Euler reports that ~100% of stolen funds were ultimately recovered (~$240m) after negotiations; attacker returned ~90% and kept ~10% framed as a bug‑bounty.
  • Reimbursement: Euler’s own post‑mortem states that user funds were fully restored using the recovered assets. External, independent on-chain verification is Not verifiable as of 2026‑09‑04.
  • Fix / structural changes: Euler V2 was built as a modular re‑architecture with extensive security hardening. The team spent ~$4m on security, commissioned 29 audits from 12 firms, ran large‑scale code‑audit competitions and bug‑bounties (Cantina competition with $1.25m rewards; subsequent $1m Euler‑hosted bounty), with no high‑ or medium‑severity issues reported post‑audit.
  • Current status: exploit itself is resolved (funds recovered, v1 hibernated). Euler V2 is live with enhanced security and ongoing bug‑bounty programs, but that is a forward‑looking mitigation rather than an active incident. Given the user’s scope (“since launch” of Euler V2): no distinct V2 exploit/hack/incident has been reported, and all known loss relates to the pre‑V2 March 2023 Euler exploit.
Date
2023-03-13
Cause
Smart-contract exploit
Loss
$197.0M
Status
resolved
Recovered
$240.0M
Reimbursed
Yes
Evidence (9)

incident

two sources

On 4 November 2025, Stream Finance disclosed an approximately $93M loss at an external manager and froze withdrawals. Stream’s xUSD was used as collateral in Euler V2 markets, particularly third-party-curated markets on Plasma. Fixed/fundamental-value xUSD oracles did not reprice collateral promptly, preventing liquidations and leaving lenders exposed to bad debt after Stream defaulted.

Euler’s Q1 2026 retrospective states that the Plasma deployment was effectively wiped out, while DAO-managed Euler markets had zero direct Stream exposure. Euler response: isolated/paused affected markets, curator intervention, emergency caps and risk reassessment. Exact Euler/user realised loss, recovery proceeds and total reimbursement are not disclosed: Not verifiable as of 2026-09-06.

Nexus Mutual paid approximately $100K in claims to covered members across affected protocols, including Euler V2, but this does not establish full user reimbursement. Current status: remediation_in_progress.

Date
2025-11-04
Cause
Liquidity issue
Status
remediation in progress
Event id
euler-v2-stream-finance-2025
Evidence (3)

incident

two sources

On 22 March 2026, a key-infrastructure compromise at Resolv enabled unauthorized minting of approximately 80M unbacked USR. The attacker extracted approximately $24–25M, causing USR, wstUSR and RLP to depeg. Euler’s Arbitrum Yield market had approximately $500K of USDC loans collateralized by RLP; related Euler Earn allocation was stopped and RLP collateral was disabled.

Euler later liquidated RLP-backed positions, redeemed collateral and the Euler Foundation backstopped remaining bad debt, allowing affected USDC lenders to withdraw in full. No confirmed user loss remained after remediation, but the Foundation’s realised contribution is undisclosed: Not verifiable as of 2026-09-06. Current status: resolved; users were reimbursed through full withdrawal access.

Date
2026-03-22
Cause
Key compromise
Loss
$0
Attacker proceeds
$24.0M
Status
resolved
Reimbursed
Yes
Event id
euler-v2-resolv-2026
Evidence (3)

key management

unverified

Euler V2 organizes key management as a mix of native account control and delegated operators rather than a single protocol-wide key. The EVC (Ethereum Vault Connector) provides unified authentication, and its account-manager “operator” feature lets a user authorize smart contracts or EOAs to act on their behalf; the same address can be split into up to 256 accounts via the account selector model. In practice, this means users can keep custody of their own funds while delegating specific actions to operators, and vaults focus on authorization/business logic instead of handling authentication themselves.

The protocol docs also describe Euler V2 as permissionless and non-custodial, with vault deployment and market configuration handled separately by curators/governors rather than by user custody keys. For this query, the best-supported answer is that key management is user-centric and delegated through EVC operators, with protocol administration separated into governance/curation roles. No chain-specific key-management differences were verifiable from the provided sources for Arbitrum, Avalanche, BSC, Base, Ethereum, Hyperliquid L1, Linea, Monad, Plasma, or Unichain.

Not verifiable as of 2026-09-04.

Evidence (5)

smart-contract

one source

Assessment — as of September 6, 2026. Dune/on-chain role membership, proxy-admin type, timelock delay, pending operations, and per-chain exit behavior: Not verifiable as of September 6, 2026. Therefore no current claim is made that roles are renounced or that a timelock is active. Addresses. The current published Ethereum registry lists eVaultFactory 0x29a56a1b8214D9Cf7c5561811750D5cBDb45CC8e, eVaultImplementation 0x8Ff1C814719096b61aBf00Bb46EAd0c9A529Dd7D, EVC 0x0C9a3dd6b8F28529d72d7f9cE918D493519EE383, and ProtocolConfig 0x4cD6BF1D183264c02Be7748Cb5cd3A47d013351b. Addresses for the requested ten chains and their live governors/admins were not individually extracted: Not verifiable as of September 6, 2026. Architecture / authority. EVK vaults are either beacon-proxy and factory-upgradeable, or immutable minimal proxies.

Upgradeable vaults inherit implementation changes from the factory; immutable vaults do not. Vault governance is separate and may control caps, LTVs, IRM, hooks, oracle-router configuration, and selected pauses. FactoryGovernor roles are PAUSE_GUARDIAN_ROLE (installs a read-only implementation), UNPAUSE_ADMIN_ROLE, and DEFAULT_ADMIN_ROLE; the latter can adminCall the factory, including implementation changes. Diagram: DAO/multisig or timelock → FactoryGovernor → EVaultFactory → beacon → upgradeable EVaults; separately, vault governor/timelock/guardian → vault parameters, hooks, oracle router; immutable EVaults bypass the factory-upgrade path. Exit and worst case. A factory pause can make state-changing calls through affected upgradeable vaults revert; whether withdrawals/repays remain enabled is deployment-specific. A compromised factory admin/governor could upgrade all linked upgradeable vaults; a compromised vault governor/oracle governor could alter risk parameters or pricing routes.

Direct arbitrary asset drainage by administrators is Not verifiable as of September 6, 2026; do not treat upgrade or configuration authority as equivalent to proven fund-drain authority. Audit status. EVK and periphery have public independent reviews and bytecode-baseline verification infrastructure, but audited status of every listed chain/vault deployment is Not verifiable as of September 6, 2026. No verified change to the previously recorded mixed upgradeability finding was identified.

Upgradeable
Yes
Evidence (5)

audit

unverified

Formal verification plus manual review, fuzzing, and testing of Euler v2 core and EulerEarn modules.

Auditor
Certora
Report date
2024-02-05
Scope
Euler V2 core lending logic and EulerEarn yield product; focus on protocol invariants, collateralization, interest accrual and liquidation properties.[5][6]
Findings
Formal verification uncovered specification and invariant issues (severity not explicitly categorized in public summary); issues were iteratively addressed during engagement.[5] Overall security posture described as high after remediation.[1][5]
Fix status
Euler reports all formal‑verification and associated findings as resolved in the current v2 codebase; no open medium‑or‑higher severities remain post‑engagement.[2][3][5]
Evidence (2)

audit

one source

Security audit of the Ethereum Vault Connector (EVC), a core component of Euler v2’s modular vault architecture.

Auditor
ChainSecurity
Report date
2024-05-08
Scope
Ethereum Vault Connector smart contracts (authentication, checks enforcement, adherence to spec) for Euler v2 on Ethereum.[1]
Findings
Only **low‑severity** issues reported; no critical or high findings. Some low issues accepted as specification with documentation improvements.[1]
Fix status
Low‑severity issues either fixed or explicitly accepted with spec/documentation updates; ChainSecurity concludes the codebase provides a high level of security.[1]
Evidence (1)

audit

one source

Euler V2 EVK audit; deployed-code match: Not verifiable as of 2026-09-05.

Auditor
ChainSecurity
Report date
2024-06-18
Scope
EVault base contracts, factory, Synth Vaults
Findings
0 critical, 0 high, 2 medium; one corrected and one risk accepted.
Fix status
One medium corrected; one medium risk accepted; five low findings risk accepted/acknowledged.
Evidence (1)

audit

one source

EulerSwap review of the source tree.

Auditor
Fuzzland
Report date
2025-02-17
Scope
euler-swap src/*.sol
Findings
Critical/high/medium: Not verifiable as of 2026-09-06.
Fix status
Reviewed commit recorded; detailed remediation status not verifiable.
Report url
https://github.com/euler-xyz/euler-swap/blob/81cf6dc988468fd56f690e6bc0e338a5be02d034/audits/eulerswap-audit-report.pdf
Report id
doc:368aca05a8b48f5c
Evidence (2)

audit

one source

Euler Price Oracle review of PendleUniversalOracle and CurveEMAOracle.

Auditor
Electisec
Report date
2025-02-23
Scope
src/adapter/pendle/PendleUniversalOracle.sol; src/adapter/curve/CurveEMAOracle.sol
Findings
Critical/high/medium: Not verifiable as of 2026-09-06.
Fix status
Reviewed and final commits recorded; detailed closure status not verifiable.
Report url
https://github.com/euler-xyz/euler-price-oracle/blob/18a3e34d516992b38797a1c61ebbf7dd8e957dcd/audits/Euler_Price_Oracle_Electisec_Report.pdf
Report id
doc:5842900f93fbe43c
Evidence (2)

audit

one source

EulerEarn audit of core vault, factory, allocator and libraries.

Auditor
Sigma Prime
Report date
2025-07-01
Scope
src/EulerEarn.sol; src/EulerEarnFactory.sol; src/PublicAllocator.sol; src/libraries/*
Findings
Critical/high/medium: Not verifiable as of 2026-09-06.
Fix status
Reviewed commit recorded; detailed per-finding closure not verifiable.
Report url
https://github.com/euler-xyz/euler-earn/blob/b2fd6e699ee20bcfe7459f375b3cee5d2fa53345/audits/Sigma_Prime_EulerEarn_report.pdf
Report id
doc:9065a0bdeeb4b064
Evidence (2)

audit

one source

EulerSwap audit covering core swap, periphery and interfaces.

Auditor
ChainSecurity
Report date
2025-03-31
Scope
src/EulerSwap.sol; src/EulerSwapPeriphery.sol; src/interfaces/IEulerSwap.sol; src/interfaces/IEulerSwapPeriphery.sol; src/interfaces/IUniswapV2Callee.sol
Findings
Critical/high/medium: Not verifiable as of 2026-09-06.
Fix status
Two assessment versions recorded; first-round fixes were reviewed and final commit is pinned.
Report url
https://github.com/euler-xyz/euler-swap/blob/81cf6dc988468fd56f690e6bc0e338a5be02d034/audits/ChainSecurity_EulerSwap_audit.pdf
Report id
doc:b2026903ef014978
Evidence (2)

audit

two sources

EulerSwap audit covering EulerSwap, factory, periphery and Uniswap hook.

Auditor
Cyfrin
Report date
2025-05-26
Scope
src/EulerSwap.sol; src/EulerSwapFactory.sol; src/EulerSwapPeriphery.sol; src/UniswapHook.sol
Findings
0 critical, 0 high, 0 medium, 2 low, 3 informational, 2 gas findings.
Fix status
Additional post-engagement commit was reviewed; critical/high/medium findings absent in the published summary.
Report url
https://github.com/euler-xyz/euler-swap/blob/81cf6dc988468fd56f690e6bc0e338a5be02d034/audits/2025-05-26-cyfrin-eulerswap-v2.0.pdf
Report id
doc:bf0fcdcd615480c3
Unresolved critical
0
Unresolved high
0
Evidence (3)

audit

one source

EulerEarn formal-verification review covering libraries, EulerEarn, factory and PublicAllocator.

Auditor
Certora
Report date
2025-07-15
Scope
src/libraries/**; src/EulerEarn.sol; src/EulerEarnFactory.sol; src/PublicAllocator.sol
Findings
Critical/high/medium: Not verifiable as of 2026-09-06.
Fix status
Reviewed and final commits recorded; detailed closure status not verifiable.
Report url
https://github.com/euler-xyz/euler-earn/blob/b2fd6e699ee20bcfe7459f375b3cee5d2fa53345/audits/Certora_EulerEarn_report.pdf
Report id
doc:c4f0e68237f798b0
Evidence (2)

audit

one source

EulerEarn audit covering vault, factory, allocator, libraries and interfaces.

Auditor
Pashov Audit Group
Report date
2025-07-30
Scope
EulerEarn.sol; EulerEarnFactory.sol; PublicAllocator.sol; ConstantsLib.sol; ErrorsLib.sol; EventsLib.sol; PendingLib.sol; SafeERC20Permit2Lib.sol; UtilsLib.sol; interfaces/
Findings
Critical/high/medium: Not verifiable as of 2026-09-06.
Fix status
Review and fixes commits recorded; detailed closure status not verifiable. Euler documentation lists August 12, 2025, creating a publication-date discrepancy.
Report url
https://github.com/euler-xyz/euler-earn/blob/b2fd6e699ee20bcfe7459f375b3cee5d2fa53345/audits/Pashov_Audit_Group_report.pdf
Report id
doc:dd4a322dd6654c28
Evidence (3)

audit

one source

EulerSwap review delivered through Cantina Managed.

Auditor
Spearbit
Report date
2025-03-29
Scope
EulerSwap.sol and EulerSwapPeriphery.sol; report scope represented as src/
Findings
Critical/high/medium: Not verifiable as of 2026-09-06.
Fix status
Draft report; final reviewed commit recorded, but repository tag mismatch and detailed closure status are not verifiable.
Report url
https://github.com/euler-xyz/euler-swap/blob/81cf6dc988468fd56f690e6bc0e338a5be02d034/audits/report-euler-swap-050325.pdf
Report id
doc:f85a8a5b0c5e334a
Evidence (2)

audit

one source

Independent review of Euler v2 focusing on access control, math safety, decentralization, code stability, testing and verification.

Auditor
Electisec
Report date
2024-03-01
Scope
Euler v2 system‑level review of vault and governance design, math routines, and testing practices.[14][15]
Findings
No exploitable vulnerabilities derived from found rounding errors/overflows; several findings on **access control** (missing locks/caller validation) and decentralization/trust assumptions. Issues mainly in low/medium‑impact categories; no public record of unresolved critical/high bugs.[14][15]
Fix status
Many findings became redundant as code evolved or were fixed during audit; Euler’s later aggregate disclosure states all third‑party security issues across v2 audits have been resolved.[2][3][14]
Evidence (1)

audit

one source

Euler V2 EVK audit; deployed-code match: Not verifiable as of 2026-09-05.

Auditor
Enigma Dark
Report date
2024-03
Scope
EVK; exact files/commit not stated
Findings
Critical/high/medium: Not verifiable as of 2026-09-05.
Fix status
Not verifiable as of 2026-09-05.
Evidence (1)

audit

two sources

Euler DAO funded a large security program for Euler v2: 29 external audit reports from 12+ firms plus a $1.25m post‑audit bug‑bounty contest.

Auditor
Multi‑firm aggregate (Spearbit, Trail of Bits, Zellic, OpenZeppelin, Hunter Security, Omniscia, Ruptura, yAudit, Certora, ChainSecurity, Electisec and others)
Report date
2024-08-12
Scope
Aggregate coverage of Euler v2 modules across lending core, vaults, oracles, periphery, integrations and infra on supported chains. Exact bytecode‑match per chain is Not verifiable as of 2026-09-04.
Findings
Across all v2 audits, **2 critical** and **5 high‑severity** vulnerabilities were discovered and fixed; subsequent bounty found **no critical, high, or medium‑severity** remaining issues.[2]
Fix status
Euler states that all issues identified in the 29 audits are resolved in deployed v2 code; bounty outcome corroborates absence of remaining medium‑or‑higher severity findings.[2][3][4][9][13]
Evidence (3)

audit

two sources

Across Euler V2, public sources report 29–31+ audits by ~12–13 independent firms plus large‑scale audit competitions. Media and protocol communications agree that these engagements collectively identified two critical and five high‑severity issues, all reported as fixed before launch. Subsequent public bug bounty and Cantina audit‑contest activities reportedly found no remaining critical, high or medium‑severity issues; only low‑severity bugs were rewarded.

Exact mapping of each firm’s report to specific modules, chains, and deployments remains fragmented and not verifiable as of 2026-08-30 at a bytecode‑match level.

Auditor
Multiple (Spearbit, Certora, ChainSecurity, Trail of Bits, OpenZeppelin, Zellic, Omniscia, Hunter Security, Ruptura, others)
Report date
2024-08-12
Scope
Euler V2 overall – core lending, vault system, oracles, periphery, integrations; multi‑firm audit program and post‑audit competitions
Evidence (5)

audit

one source

Euler V2 EVC audit; deployed-code match: Not verifiable as of 2026-09-05.

Auditor
Omniscia
Report date
2024-05-16
Scope
EVC core, execution context, sets, transient storage
Findings
Critical/high/medium: Not verifiable as of 2026-09-05.
Fix status
Final revision commit recorded; detailed closure status not verifiable.
Evidence (1)

audit

one source

Euler V2 EVK audit; deployed-code match: Not verifiable as of 2026-09-05.

Auditor
Omniscia
Report date
2024-05-20
Scope
EVK core, Synths, factories, IRM, ProtocolConfig
Findings
Critical/high/medium: Not verifiable as of 2026-09-05.
Fix status
Revisions through commit 0f2192a recorded; detailed closure status not verifiable.
Evidence (1)

audit

one source

Euler V2 EVC audit; deployed-code match: Not verifiable as of 2026-09-05.

Auditor
OpenZeppelin
Report date
2024-04-16
Scope
EthereumVaultConnector, execution context, sets, transient storage, interfaces
Findings
Critical/high/medium: Not verifiable as of 2026-09-05.
Fix status
Final commit recorded; detailed closure status not verifiable.
Evidence (1)

audit

one source

Euler V2 EVK audit; deployed-code match: Not verifiable as of 2026-09-05.

Auditor
OpenZeppelin
Report date
2024-05-17
Scope
EVK core, factories, IRM, ProtocolConfig, interfaces
Findings
Critical/high/medium: Not verifiable as of 2026-09-05.
Fix status
No separate fix round recorded.
Evidence (1)

audit

one source

yAudit performed a comprehensive, independent audit of the Euler V2 EVC, EVK and EPO codebases over a 30‑day period. The engagement covered core vault connector logic, vault kit, and price oracle modules for the v2 architecture. Detailed findings (including severity and fix status) are in the PDF report; public secondary sources only state that issues were resolved, with no disclosed remaining ≥medium‑severity items.

Not verifiable as of 2026-08-30 whether this report’s scope covers all currently deployed chain variants or later upgrades.

Auditor
yAudit
Report date
2024-03-25
Scope
Euler V2 EVC repo, EVK repo, EPO repo (core modular lending vault system)
Evidence (2)

audit

two sources

Comprehensive code review of Euler v2 contracts (EVC, EVK, EPO repos) over ~30 days, including vault connector and modular vault architecture.

Auditor
yAudit
Report date
2024-05-05
Scope
Euler V2 core contracts: EVC (Ethereum Vault Connector), EVK (Euler Vault Kit), EPO (Euler Periphery) and related modular vault components.[8]
Findings
Multiple issues across categories with at least one **critical** and several **high** findings referenced in EVK yAudit report; medium/low issues also identified.[10][8] Overall, no remaining medium-or-higher severity issues after fixes and follow‑up review.[2][3]
Fix status
All critical and high findings reported as fixed or mitigated; follow‑up “CodeCompetition Fixes review” confirms resolution of remaining items.[8][10][6]
Evidence (3)

Team & Reputation

founders

two sources

Euler V2 is built by the Euler Labs team behind Euler Finance; founders are public, UK‑based, and technically credible, but the protocol carries a material prior‑exploit history and is operated via a lean startup rather than a large regulated financial institution. Founders & key team

  • Founders: Michael Bentley (co‑founder & CEO), Doug Hoyte (co‑founder, blockchain/smart contracts), and Jack Prior (co‑founder, full‑stack dev).
  • Background: Bentley holds a PhD in dynamical systems/evolutionary biology from Oxford and was an Oxford researcher before Euler. Hoyte is described as a veteran engineer/blockchain dev.
  • Team composition: Core contributors sit under Euler Labs, with roles such as Risk Curators, Technical Stewards, and other core devs (e.g., Anton Totomanov, Dariusz Glowinski, Kasper Pawlowski).
  • Public vs anon: Founders give named interviews and appear on podcasts and media (Blockworks, StablePod, DLNews), indicating a fully doxxed, public team. Entity, office, onshore/offshore
  • Legal entity: EULER LABS LTD is a UK private limited company, incorporated 7 September 2020.
  • Registered office: 128 City Road, London, England, EC1V 2NX.
  • Previous name: EULER XYZ LIMITED until August 2022.
  • This points to an onshore UK corporate structure with public company filings, not a pure offshore foundation. Track record, prior outcomes & hack history
  • Euler v1 launched December 2021 and was a leading DeFi lending protocol.
  • On 13 March 2023, Euler Finance suffered a ~$197–200m flash‑loan exploit due to a smart‑contract vulnerability introduced in an update.
  • Despite having been audited around 10 times before the attack, the bug slipped through; risk levels previously ranged from informational to critical.
  • The attacker later returned the recoverable funds, following negotiations and public pressure.
  • Post‑hack, Euler Labs decided not to patch v1 but to rebuild Euler v2 from scratch, reportedly commissioning dozens of audits (45 audits by 13 firms) before launch. Reality check: business substance vs web front
  • Evidence of substance: UK corporate registration, media coverage (Bloomberg, Fortune, Coindesk, DLNews, Blockworks), and ongoing research coverage (OAK Research) indicate a real operating business, not just a website.
  • Credibility trade‑off: founders are academically strong and publicly accountable, but the 2023 exploit is a major adverse event in their track record. They did, however, manage a full recovery of user funds and a structured relaunch.
  • Physical presence: only the registered office address is verifiable; actual staffed office vs virtual address is Not verifiable as of 2026‑09‑04. Chain footprint (Arbitrum, Avalanche, BSC, Base, Ethereum, Hyperliquid L1, Linea, Monad, Plasma, Unichain)
  • Specific per‑chain deployment details, team structure per chain, and jurisdictional entities beyond Euler Labs UK are Not verifiable as of 2026‑09‑04 from independent sources above.
Evidence (15)

general reputation

two sources

Euler V2 has a mixed but improving reputation: the protocol suffered a major exploit in 2023 (Euler v1) but has since invested heavily in security and transparency for its v2 relaunch, with no publicly reported fraud, rug, or insolvency allegations against the team. Team, founders, investors

  • Euler is developed by Euler Labs, led by CEO Michael Bentley and CTO Kasper Pawlowski.
  • Euler Labs has backing from reputable crypto and VC investors including Paradigm, Uniswap Labs Ventures, Jane Street, Variant, Haun Ventures, Alliance DAO, among others.
  • This investor set generally supports a perception of institutional-grade governance and due diligence. Security, audits, and risk perception (Euler V2)
  • For Euler V2, the team reports 29+ audit reports from 12 independent security firms, with a security budget of about $4M dedicated to the relaunch.
  • Public summaries indicate critical and high-severity issues were found and remediated before launch, with a subsequent $1.25M post-audit bug bounty that did not uncover medium-or-higher-severity issues.
  • Named auditors include yAudit and Spearbit among others; some reports are publicly available while others are private, which is typical for large multi-firm audit campaigns.
  • Independent risk platforms like DeFi Sentinel currently rate Euler with an AA safety score (85/100), characterizing risk as “very low,” as of May 21, 2026. Exploit history and criticisms (Euler v1)
  • On 13 March 2023, about $200m in assets were stolen from the original Euler protocol via an exploit of vulnerable code.
  • Following negotiations, all recoverable funds were returned by the exploiter, in one of the largest asset recoveries in DeFi history.
  • The incident drew strong criticism of Euler’s initial risk controls and code review, and remains a reputational scar; however, the full recovery and subsequent security overhaul are often cited as evidence of responsible crisis management and improved practices. Legal, regulatory, sanctions, fraud/rug
  • Available sources discuss law-enforcement engagement during the 2023 investigation but do not report sanctions, regulatory enforcement actions, or fraud/rug findings against Euler Labs or its founders.
  • No credible sources allege a rug pull or deliberate misconduct; reputational concerns are centered on past technical failures, not fraud. Unresolved concerns
  • Multi-chain expansion (Arbitrum, Base, etc.) increases systemic complexity; chain-specific risk metrics and on-chain health for Euler V2 are Not verifiable as of 2026-09-04 under current data constraints.
  • Some audit reports remain private, which may limit external reviewers’ ability to independently confirm all security claims.
Evidence (14)

Economy

TVL: $342.5M

model

one source

Economic model (as of September 6, 2026). Euler V2 is modular, permissionless lending built from isolated ERC-4626 vaults. Suppliers deposit one ERC-20 and receive vault shares; borrowers post accepted vault shares/assets as collateral and pay variable interest. Core supplier yield is borrower interest, reduced by configured interest fees and affected by utilization.

EulerEarn may allocate deposits across configured strategies, while displayed APY can also include intrinsic asset yield and campaign rewards. Strategy/risk profile. The base product is generally market-neutral credit intermediation, not a directional trading strategy. However, users can create directional exposure through Multiply, borrow-and-swap loops, leveraged LP/LST/LRT positions, synthetic assets, or external strategies. Restaking and external protocol exposure are therefore vault/asset-specific, not protocol-wide.

Leverage is permitted but there is no single protocol-wide leverage ratio: it depends on collateral, LTV, caps, liquidity and connected vaults. leverage_ratio: null. Withdrawals, fees and limits. Withdrawals are ERC-4626 redemptions subject to available liquidity and contract limits; vaults can impose supply/borrow caps, LTVs, oracle checks, liquidation thresholds, hooks and fees. No universal lock-up or protocol-wide withdrawal gate was identified. Liquidations use a reverse-Dutch-auction discount. Revenue/yield quality. DeFiLlama currently reports 152 pools, average supply APY 10.43%, TVL $351.7m, active loans $451.28m, 30-day fees $1.39m and protocol revenue $44,845.

Fees include borrower interest plus protocol/curator fees; revenue is the protocol-retained portion. Because APY may include rewards and intrinsic yield, organic_yield_pct: null. APY history/volatility and sustainability are Not verifiable as of September 6, 2026 without a reproducible time series. TVL by requested chain (DeFiLlama snapshot): Monad $241.91m (68.8%), Ethereum $75.68m (21.5%), Base $14.51m (4.1%), Avalanche $4.54m (1.3%), Hyperliquid L1 $2.83m (0.8%), Plasma $2.10m (0.6%), Unichain $1.88m (0.5%), BSC $1.47m (0.4%), Arbitrum $0.99m (0.3%), Linea $0.37m (0.1%). Contradiction: DeFiLlama lists 16 chains, including BOB, Sonic, Berachain, TAC and Swellchain, beyond the 10 supplied; these add approximately $5.4m.

Dune TVL, product-level TVL, chain trend comparison, and on-chain APY history are Not verifiable as of September 6, 2026.

Evidence (4)

reserves

unverified

As of September 6, 2026, current liquid reserve value and liabilities are not verifiable as of September 6, 2026: Dune MCP was unavailable, and no independent current balance snapshot or liabilities statement was identified. Addresses / custody

  • Canonical DAO Treasury: 0xC7C5aFDB61e08BE3e2FB09098412b5706EB5c550.
  • Legacy Treasury: 0x25Aa4a183800EcaB962d84ccC7ada58d4e126992; Euler states new EUL issuance is directed to this legacy address.
  • Euler states Treasury transactions require multisig approval, but the current signer set, threshold, Safe configuration, and custody provider are Not verifiable as of September 6, 2026.
  • A March 18, 2025 governance-forum post identified Foundation multisig 0x967B10c27454CC5b1b1Eeb163034ACdE13Fe55e2, managed under a stated 3-of-5 arrangement. This is an operational/foundation wallet, not proof of the current DAO Treasury control configuration. Composition / size
  • Euler documentation says the DAO holds EUL, but provides no current USD reserve total or complete asset inventory.
  • Historical disclosure: approximately 6,236,107 unlocked EUL was held in the DAO Treasury as of January 31, 2025. Euler later states that in November 2025 treasury assets were transferred to the canonical Treasury address, excluding protocol revenue retained during the transition; therefore the January 2025 figure must not be treated as current.
  • The March 2025 proposal described estimated allocations of $500,000 USDC for operations, 500,000 EUL for strategic liquidity, and up to $5 million USDC to be reallocated from Euler V2. These were proposal estimates/requests, not independently verified current balances.
  • Current composition across Ethereum, Arbitrum, Avalanche, BSC, Base, Hyperliquid L1, Linea, Monad, Plasma, and Unichain: Not verifiable as of September 6, 2026. Reserve policy / attestations The stated policy is multisig approval, discretionary strategic deployment, and quarterly spending/status attestations. No current published attestation or independently verified reserve report was located: Not verifiable as of September 6, 2026. Contradiction / key risk: historical EUL and proposal figures are stale or explicitly estimated, while current on-chain balances and liabilities could not be checked. The on-chain answer is therefore unresolved, not zero.
Evidence (3)

tokenomics

one source

Euler V2 has a native token: EUL (Euler). Canonical Ethereum ERC-20: 0xd9fcd98c322942075a5c3860693e9f4f03aae07b. Euler also publishes bridged/deployed EUL on Arbitrum, Avalanche, BSC, Base, Unichain and Plasma; exact full addresses for every user-specified chain, including Hyperliquid L1, Linea and Monad, are Not verifiable as of September 4, 2026 without on-chain verification. Supply/valuation: fixed stated supply is 27,182,818 EUL; circulating supply is approximately 24.0m.

CoinGecko reports market cap of approximately $31.0m and FDV of approximately $35.0m (figures are live aggregator data and may move intraday). Utility/governance: EUL provides one-token/one-vote governance over protocol parameters and treasury actions, is distributed as user rewards, and is the payment token for Fee Flow auctions. Fee Flow is currently disabled and protocol fees are 0%; there is no confirmed current revenue share, buyback, or staking yield.

Fee Flow payments do not automatically burn EUL. Emissions/unlocks: rEUL rewards convert 1:1 into EUL: 20% immediately and 80% linearly over six months. Historical allocation: ~34% DAO/users/ecosystem, ~3.7% Foundation, ~39.5% strategic partners (reported fully unlocked), and ~26.5% Euler Labs employees/advisors/consultants; founder vesting began January 1, 2022, while non-founder vesting was generally 48 months.

Whether announced unlocks actually occurred on-chain is Not verifiable as of September 4, 2026. Controls/concentration: the Ethereum contract permits its ADMIN_ROLE to mint 2.718% of total supply at most once per 365 days to the legacy treasury. Exact role-holder, blacklist/fee-switch status, current top-holder concentration, insider-wallet attribution, and treasury percentage are Not verifiable as of September 4, 2026.

Liquidity/listings: major listings include Binance, Coinbase, Kraken, Gate and others; DEX liquidity depth across the specified chains is Not verifiable as of September 4, 2026.

Evidence (5)

Stress scenarios

stress scenario - bitcoin price falls below $10000

two sources

Under a Bitcoin move below $10,000, Euler V2 should be treated as a high-stress liquidation environment because its lending design relies on collateral valuation, borrow LTV, liquidation LTV, caps, and account health checks enforced through its oracle route. A severe BTC drawdown would likely compress collateral values, raise liquidation frequency, and increase the chance of bad debt or socialized losses if liquidations cannot fully absorb the shock. What is not verifiable as of 2026-09-04 from the available sources is the chain-by-chain exposure of Euler V2 across Arbitrum, Avalanche, BSC, Base, Ethereum, Hyperliquid L1, Linea, Monad, Plasma, and Unichain, as well as the amount of BTC-linked collateral, outstanding borrows, or protocol TVL on each chain.

Without on-chain verification, I cannot quantify which chain would absorb the most stress or provide a percentage split. Not verifiable as of 2026-09-04. The most defensible stress conclusion is therefore qualitative: if BTC breaks $10,000, Euler V2’s risk would be driven by the speed of price transmission into oracle values, the size and quality of BTC-correlated collateral, and whether liquidators can clear undercollateralized accounts fast enough.

If those conditions fail, the protocol’s bad-debt socialization mechanism becomes the main contagion channel. The broader macro premise that BTC could fall to $10,000 is supported by independent market commentary, but those are scenario forecasts rather than protocol-specific evidence.

Evidence (6)

stress scenario - largest collateral depegs 20%,

unverified

A 20% depeg of the largest collateral in Euler V2 is not fully quantifiable from the provided sources because current on-chain vault exposures by chain are not verifiable here. The protocol design does show that a collateral price drop can push accounts below liquidation thresholds and, if liquidation proceeds cannot fully cover debt, bad debt is handled at the vault level through socialization/reserve mechanisms rather than a protocol-wide halt. What can be stated from the sources is limited to mechanism and a historical reference point:

  • Euler V2 uses configurable collateral and liquidation thresholds, and an account becomes liquidatable when its collateral value no longer satisfies requirements.
  • Liquidation discounts can reach a configured maximum of 20% in Euler’s liquidation design, so a 20% collateral depeg is in the range of stress that can materially impair solvency if a position was already near threshold.
  • Euler’s own forum noted during a USDC depeg event that USDC and DAI together were about 20% of total supply on Euler, with no significant bad debt observed at that time; this is a historical point, not a current exposure snapshot. For your requested scenario across Arbitrum, Avalanche, BSC, Base, Ethereum, Hyperliquid L1, Linea, Monad, Plasma, and Unichain, the chain-by-chain exposure share and resulting loss estimate are Not verifiable as of 2026-09-04 from the available sources.
Evidence (9)

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

two sources

Euler V2 is not yet a live, multi‑chain protocol with deployed money‑market contracts across the listed chains; it is an announced upgrade / redevelopment of Euler after the 2023 exploit, with design discussions but no full production system to analyze on‑chain. As a result, detailed, chain‑specific stress‑path analysis is Not verifiable as of 2026‑09‑04. Given the lack of deployed Euler V2 contracts, the only defensible approach is to infer from Euler V1’s architecture and generic over‑collateralized lending mechanics, clearly labeled as inference rather than protocol‑specific fact. Generic top‑counterparty insolvency path (Euler‑style lending markets, all chains) 1. Trigger / expected loss path (inference)

  • A large borrower’s collateral value drops or their borrowed asset spikes; health factor falls below liquidation threshold.
  • If liquidators cannot or do not step in (oracle failure, liquidity crunch, gas spike), the position becomes under‑collateralized; the market accrues bad debt (shortfall in the borrow token pool). 2. Who absorbs losses (inference)
  • Lenders in the affected pool: instantaneous economic loss via lower claim on assets versus their on‑chain balance unit (eToken / similar).
  • Protocol backstop / reserves, if designed: an insurance or reserve fund may be tapped to recapitalize the pool; if insufficient, residual loss remains with depositors.
  • Governance token holders, if a socialized recapitalization or token‑dilutive bailout is executed via governance. 3. Compensation mechanisms (inference)
  • Automatic: use of protocol reserves, backstop auctions, or risk‑fund tranches.
  • Discretionary: governance votes to mint governance tokens, redirect future fees, or deploy treasury assets to make depositors whole.
  • Legal/off‑chain: if an off‑chain entity runs an insurance or recovery program, claim processes may exist; for Euler V1 this took the form of negotiated post‑exploit recovery, but this is historical and not codified for V2. 4. Smart‑contract impact path (inference)
  • Insolvency shows as:
  • borrow token pool balance < total eToken supply redeemable; negative equity of the pool.
  • interest‑rate model may break (utilization ~100%, no liquidity).
  • Liquidation, reserve, and governance modules execute according to their hard‑coded logic:
  • calling liquidation functions, updating internal accounting, possibly triggering auction/settlement modules;
  • governance timelock executes parameter changes or recapitalization transactions. Because Euler V2 contracts on Arbitrum, Avalanche, BSC, Base, Ethereum, Hyperliquid L1, Linea, Monad, Plasma, and Unichain are Not verifiable as of 2026‑09‑04, no chain‑specific variations (e.g., isolated markets, cross‑chain backstops) can be analyzed without speculative overreach.
Evidence (2)

stress scenario - committed fraud by the DAO or owners

two sources

Not verifiable as of 2026-09-04. I could not verify any committed fraud by the Euler V2 DAO or owners from the available sources. The strongest directly relevant material instead describes the protocol’s prior 2023 exploit as an attack on the lending logic, not as proven DAO/owner fraud: multiple independent writeups say the attacker used the donateToReserves path and a missing solvency check to drain funds. Euler’s own materials also frame V2 security as a design and audit effort, with no source here alleging DAO or owner fraud.

For Euler V2 specifically, the available sources focus on security architecture and hypothetical attack vectors, including donation attacks and vault-level risks, but they do not provide evidence that the DAO or owners committed fraud. The protocol’s published security challenge result says no one extracted funds from Euler v2’s contracts during the challenge, which is evidence about robustness, not misconduct. Because this question asks for a stress scenario centered on deliberate fraud by governance or owners, the correct risk flag from the available evidence is that such conduct is not verifiable here; there is no sourced allegation or adjudicated finding in the provided material tying Euler V2 DAO/owners to fraud.

The only clearly documented incident is the 2023 exploit affecting Euler Finance, which was an external attack and later negotiation outcome, not proven insider fraud.

Evidence (7)

stress scenario - primary yield source negative 30d,

two sources

Euler V2’s primary yield source is the borrower interest that accrues to the liability vault and is passed through to suppliers after fees; when that source is negative over 30 days, the stress implication is that supplier returns from core lending carry are negative for the period, compressing vault APY and potentially making withdrawals less attractive. Euler’s docs confirm that supplier yield is tied to borrowed-assets interest and vault accounting, so a negative 30-day primary yield means the protocol’s main endogenous yield engine is not contributing positive carry in that window. For risk interpretation, this is a yield stress, not necessarily an insolvency event by itself.

Euler’s design keeps supply and borrow accounting separate through vaults and the EVC, and losses only become balance-sheet stress if negative carry coincides with reduced liquidity, bad debt, or liquidation pressure. I could not verify chain-by-chain TVL or whether the negative 30-day yield is concentrated on Arbitrum, Avalanche, BSC, Base, Ethereum, Hyperliquid L1, Linea, Monad, Plasma, or Unichain because on-chain verification is unavailable in this run. Not verifiable as of 2026-09-04.

Evidence (3)

Governance & Legal

governance

one source

Assessment as of September 13, 2026: Euler V2 is hybrid and not a pure DAO. EUL holders can vote on protocol changes and treasury matters, but governance is split among Snapshot, Tally, Euler Foundation, Euler Labs, multisigs, governors, timelocks, and vault-specific curators. The documented process is discussion/RFC → eIP → Snapshot; smart-contract changes may proceed to Tally and then an executor.

Snapshot outcomes can remain signaling-only unless an execution transaction follows. Control map. Euler Labs develops protocol code and operates the frontend/company products. Euler Foundation handles legal, treasury, contracting, and ecosystem functions. The Terms identify the Foundation or affiliates as the company behind euler.finance and app.euler.finance, while disclaiming control of the autonomous Protocol.

The Foundation is a Cayman Islands foundation company established in 2022; its registration number and director names were Not verifiable as of September 13, 2026. Euler Labs Ltd is an English private company, number 12863550; Companies House lists Jonathan Han, Douglas Hoyte, and Kasper Pawlowski as active directors. Timelock/emergency powers. Euler documentation describes dual admin/wildcard timelocks, normally with a 48-hour delay in the DAO risk-governance design. However, Euler explicitly states that some deployments have no timelock and that emergency or selector-specific roles may bypass it.

CapRiskSteward provides a documented fast lane for bounded cap/IRM changes. Vault governance is deployment-specific and may be an EOA, multisig, governor, or timelock. Multisigs/treasury. The Foundation treasury page states a 4/9 Safe; the November 2025 restructuring proposed a new treasury Safe and a 4/8 operational Safe with six Euler Labs and two Foundation signers. Signer identities and current post-migration configuration are Not verifiable as of September 13, 2026.

This is a documented contradiction requiring on-chain verification. Concentration. Top EUL holders, voting concentration, chain-by-chain exposure, and multisig independence are Not verifiable as of September 13, 2026 (Dune unavailable; no substitute is asserted). DAO control is therefore assessed as symbolic/partial rather than full: Foundation/Labs and privileged contracts retain material execution power. The protocol/company structure creates a credible admin-drain and emergency-bypass risk for some deployments, although exact fund-moving permissions are deployment-specific.

Timelock
Yes
Timelock delay hours
48
Admin can drain
Yes
Emergency bypass
Yes
Dao governance
No
Evidence (10)

legal & regulatory

one source

Assessment (as of September 4, 2026): Entity / jurisdiction. The legal structure is multi-layered: Euler Foundation is a Cayman Islands foundation company established in 2022; Euler OpCo Ltd is identified in the MiCA whitepaper as the BVI private-company offeror for EUL; Euler Labs Ltd is an active UK private company incorporated in 2020, with software-development SIC codes. The Foundation’s own Terms name it as the contracting entity and apply Cayman law. ToS / restrictions. The Terms distinguish the front-end “Products” from the autonomous Protocol and disclaim control, custody, fiduciary duties, and liability for protocol/components.

They impose age/legal-capacity requirements, prohibit restricted jurisdictions and VPN circumvention, and list Iran, Belarus, Cuba, DPRK, Syria, Crimea/Donetsk/Luhansk, and Russia. Mandatory individual arbitration, class-action waiver, Cayman governing law, and England/Wales courts for non-arbitrable disputes apply. KYC/AML / sanctions. No protocol-wide KYC onboarding obligation is stated.

The front end may log wallet addresses and screen them for prior illicit activity; it may verify eligibility and report suspicious activity. Centralized exchanges/CASPs may separately impose KYC/AML. Sanctions compliance is primarily an access/contractual restriction, not evidence that Euler itself is sanctioned.

Classification. Euler’s MiCA whitepaper says EUL is not classified as a utility token (D.6/G.6 “FALSE”), while describing governance/utility functions and warning of unresolved regulatory-classification risk. The Terms state Euler is not SEC-registered or SEC-regulated—an issuer assertion, not a regulator determination. Warnings / legal risk. The whitepaper discloses the March 2023 V1 exploit, legal-structure complexity, multi-jurisdictional exposure, and pending detailed financial reporting.

Privacy policy coverage exists but is stale data (updated August 28, 2024); blockchain data is public/immutable and wallet screening involves third-party analytics. Enforcement, court cases, sanctions: Not verifiable as of September 4, 2026. The 2023 exploit was a security incident, not identified regulatory enforcement.

Legal wrappers reduce contracting/operational exposure but do not eliminate protocol-level attribution, AML, securities, consumer-protection, or data-protection risk. Structured fields: active_enforcement=null; sanctioned=null; entity="Euler Foundation (Cayman); Euler OpCo Ltd (BVI); Euler Labs Ltd (UK)"; jurisdiction="Cayman Islands; British Virgin Islands; United Kingdom".

Entity
Euler Foundation (Cayman Islands); Euler OpCo Ltd (British Virgin Islands); Euler Labs Ltd (United Kingdom)
Jurisdiction
Cayman Islands; British Virgin Islands; United Kingdom
Evidence (5)

legal registries

two sources

GLEIF LEI registry unavailable at scan time. OFAC SDN screening of 'Euler Foundation', 'Euler OpCo Ltd', 'Euler Labs Ltd', 'Euler V2': no match. SEC litigation and administrative release feeds: no mention.

Screened names
  • Euler Foundation
  • Euler OpCo Ltd
  • Euler Labs Ltd
  • Euler V2
Sanctioned
No
Evidence (3)

Stability

stability

one source

Euler V2 does not appear to issue its own stablecoin; it is a lending protocol that supports third-party stablecoins and markets. A stablecoin depeg did happen in the protocol’s ecosystem: the clearest protocol-relevant case in the retrieved sources is the USDC depeg event on 2023-03-11, which the Euler forum explicitly monitored as a risk event affecting USDC and DAI markets. The exact depeg count, last depeg date, and maximum depeg percentage are not verifiable as of 2026-09-06 from the available sources, because no on-chain verification was available in this run.

The protocol is therefore not “stable” in the sense of never having depeg exposure; rather, its stablecoin exposure has included at least one documented depeg event.

Own stablecoin
No
Stable
No
Depeg count
1
Last depeg date
2023-03-11
Stablecoin ids
  • USDC
  • DAI
  • USDT
  • USDS
  • USD0
  • USR
Evidence (3)

Risks & Strengths

risks

two sources

Euler V2’s principal risks arise from its permissionless, modular architecture: each vault’s oracle, collateral graph, LTVs, caps, liquidity, hooks, and governance materially determine its safety. Independent audits and formal verification reduce implementation risk, but do not eliminate configuration, market, oracle, or administrative risks. Cross-chain TVL, exposure, and role assignments are Not verifiable as of September 5, 2026 because Dune MCP was unavailable.

RiskImpactSeverityProbabilityMitigation in placeResidual risk
Oracle manipulation or misconfigurationStale, manipulated, incorrectly scaled, or misrouted prices can overstate collateral, permit undercollateralized borrowing, or trigger unfair liquidations. Risk varies by vault and chain.HighMediumConfigurable oracle routes, oracle reviews, LTV buffers, caps, monitoring, and curator responsibility.High residual risk for thin-liquidity assets, custom routes, and fast markets; deployment-specific oracle state is Not verifiable as of September 5, 2026.
Permissionless vault configurationVault creators can select collateral relationships, LTVs, caps, interest models, hooks, and governance structures. Malicious or careless configurations can create bad debt or deposit losses.HighHighVault isolation, parameter controls, perspectives/verification tooling, curated interfaces, audits, and user due diligence.High residual risk because permissionless creation is a design feature, not a protocol-level guarantee of safety.
Composable collateral contagionConnected vaults and ERC-4626-style strategies create recursive dependencies. A faulty, illiquid, malicious, or mispriced collateral vault can transmit losses into otherwise sound markets.HighMediumEVC compatibility checks, oracle requirements, collateral verification guidance, isolated vaults, and liquidation controls.Medium-to-High; recursive exposure and current collateral graphs are Not verifiable as of September 5, 2026.
Governance and upgrade authorityUpgrade admins, factory governors, vault governors, oracle-router authorities, or privileged roles may alter implementations or risk parameters, or pause activity. Compromise or poor governance can cause loss or prolonged illiquidity.HighMediumRole separation, optional timelocks, multisig-oriented design, factory pause controls, immutable vault options, and deployment verification.Medium-to-High because controls are deployment-specific and many configurations may lack meaningful delay.
Liquidation and liquidity stressVolatile prices, rate spikes, gas congestion, thin liquidity, or insufficient liquidator participation can leave positions undercollateralized and socialize losses or impair withdrawals.HighHighBorrow caps, LLTV/LTV separation, reverse-Dutch liquidation discounts, partial liquidations, open liquidator infrastructure, and monitoring.High during correlated shocks and on long-tail assets; chain-level liquidity and exposure are Not verifiable as of September 5, 2026.
Evidence (6)

strengths

two sources

Euler V2’s top strengths are: (1) modular architecture, which lets builders deploy independent vaults and tailor lending markets without a monolithic pool; (2) strong risk isolation, so failure in one vault is designed not to drain others; (3) composability via the Ethereum Vault Connector (EVC), which lets vaults be used as collateral across the broader system; (4) permissionless market creation, enabling long-tail assets and custom risk parameters to be onboarded more flexibly; and (5) a more advanced user/developer toolkit, including custom liquidation logic, sub-accounts, and other risk-management features that improve capital efficiency and product flexibility.

Evidence (5)

Methodology & Limitations

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