Euler primary sources — 2026-05-08

Classification takeaway

Euler is best treated as modular lending infrastructure rather than as just another pooled money market. The important design move is the separation between a shared account-and-collateral coordination layer (EVC) and many vault-level policy surfaces built with the Euler Vault Kit (EVK). That makes Euler a useful comparison point for Blend, Morpho, Wildcat, and other projects that relocate risk control away from one global market engine.

Primary sources reviewed

1. Official docs landing page — https://docs.euler.finance/

   • Frames Euler as a platform to “lend, borrow and build without limits,” with separate sections for users, developers, creators, and security.
   • The structure itself is a clue that Euler is trying to be a builder platform, not only a retail lending app.

2. Lite paper — https://docs.euler.finance/lite-paper/

   • Gives the clearest high-level description of Euler v2 as a system of ERC-4626 vaults built with the EVK and connected by the EVC.
   • Distinguishes several vault classes: escrowed collateral vaults, governed vaults, ungoverned vaults (0x and nzx), and yield-aggregator vaults.
   • Says vault governors or managers can control risk, interest rates, LTVs, and allocator behavior, which is the key practical-authority surface in the design.
   • Describes additional modules including RewardStreams, FeeFlow, synthetic-asset support, reverse-Dutch-auction fee conversion, operators, batching, flash-liquidity-style refinancing, and 256 virtual sub-accounts.

3. Concepts docs — https://docs.euler.finance/concepts/

   • Organizes the protocol around core components like the EVC, vaults, markets, and price oracles, plus risk curators, hooks, operators, and sub-accounts.
   • Reinforces that Euler is a stack of interoperable primitives rather than one uniform market template.

4. EVC site — https://evc.wtf/

   • Presents the Ethereum Vault Connector as an open-source layer that connects ERC-4626 and other vault types so they can be used as collateral for one another.
   • Emphasizes generalized flash loans and batching, advanced position management, external operators, and support for irregular collateral classes such as RWAs, NFTs, IOUs, and synthetics.
   • This makes the connector look like a reusable lending kernel for many downstream products, not just an internal Euler helper.

5. EVC README — https://raw.githubusercontent.com/euler-xyz/ethereum-vault-connector/master/README.md

   • Describes the EVC as a foundational layer for lending markets that mediates between vaults and reduces complexity in lending/borrowing contracts.
   • Explicitly points readers to the EVC whitepaper and playground examples, which supports the idea that Euler wants outside builders to treat the EVC as a standalone primitive.

6. EVC whitepaper markdown — https://raw.githubusercontent.com/euler-xyz/ethereum-vault-connector/master/docs/whitepaper.md

   • Explains controller relationships, collateral enablement, deferred account-status checks, batching, sub-accounts, operators, simulations, and liquidation interfaces in more detail.
   • The most important analytical point is that enabling a controller vault submits the account to that vault’s rules, making controller design a central trust and governance surface.
   • Also makes clear that collateral validity and vault-status logic remain application-specific, so the EVC standardizes orchestration without standardizing risk judgment.

7. EVK README — https://raw.githubusercontent.com/euler-xyz/euler-vault-kit/master/README.md

   • Defines EVK vaults as ERC-4626 credit vaults with added borrowing functionality and distinguishes them from typical actively managed yield vaults.
   • Confirms that the EVK is aimed at constructing passive lending pools and that separate whitepaper material exists for limitations and security considerations.

8. GitHub org — https://github.com/euler-xyz

   • Shows public repos for the docs, EVC, EVK, fee-flow, and related tooling.
   • Helps confirm that the protocol is shipping a modular builder stack, not just narrative docs.

Whitepaper / technical-doc status

• Canonical official technical docs clearly exist.
• The most legible references in this pass were:
  • the official Lite Paper at https://docs.euler.finance/lite-paper/
  • the EVC whitepaper markdown at https://raw.githubusercontent.com/euler-xyz/ethereum-vault-connector/master/docs/whitepaper.md
  • EVK and EVC repository READMEs referencing additional whitepaper material
• The EVK whitepaper page itself did not yield useful parsed text in this pass, but the lite paper and EVC whitepaper were sufficient to classify the project confidently.

Why it stays in the active corpus

• Strong comparison class for modular lending and credit-vault design, especially versus Morpho, Blend, Wildcat, and borrower- or curator-defined market systems.
• Useful for understanding where authority sits when account orchestration becomes shared infrastructure but collateral policy, fee logic, risk management, and liquidation design stay vault-local.
• Important because it makes sub-accounts, operators, and cross-vault collateral recognition first-class primitives rather than app-level conveniences.