Euler 백서

Euler

원문

bitpro가 원문에서 글자만 모은 내용이에요. 표·그림·수식은 빠지거나 깨질 수 있어요. 전체 26쪽 중 2쪽

an be found at evc.wtf. One of the goals of the EVC is to abstract away many of the features common to all credit-based protocols in order to let developers focus on product features tailored to specific types of users. In this way it helps developers build their own lending protocols, stablecoins, yield aggregators, margin trading apps, and much else. In the long run, it is expected to usher in a wave of innovation in lending as it supports lending products backed not only ERC20 tokens, but also irregular asset classes, such as RWAs, NFTs, IOUs, synthetics, and more. Growth of vaults designed to work with the EVC expands the Euler ecosystem and leads to more flexibility for lenders and borrowers alike. This leads to higher yields and powerful network effects over the long term. #### Account Managers for advanced trading and risk management For developers building on the EVC, it provides a range of important features for more advanced users of lending protocols out of the box. These include multicall-like batching, flash liquidity for efficient refinancing of loans, simulations, gasless transactions, and more. One of the powerful features of the EVC is account manager functionality implemented through a smart contract called an operator. Operators can be smart contracts or EOAs that can be delegated responsibility to act on a user’s behalf. Amongst other use cases, this feature can be used to implement advanced trading and risk management strategies, including conditional orders like stop-loss and take-profit, custom liquidation flows, or intent-based systems. Developers can build their own operator smart contracts to implement risk management and position automation strategies and make them available to users as separate products. The EVC is a multicall contract with a special user authentication layer. It allows any external contracts to be called without needing adaptor contracts. This not only means that all the functionality is accessible to both EOAs and smart contract wallets, but also allows for limitless expansion of the ecosystem through the development of new EVC-compatible products in a permissionless fashion. Although the EVC allows only one outstanding liability at any given time, it provides each address with 256 virtual addresses (“sub-accounts”), which provide a gas-efficient way for users to isolate and manage risk without the need to maintain multiple separate wallet accounts. #### Collateral direct from a user’s wallet An alternative path to creating a collateral-only asset is to create an ERC20Collateral token, which is a simple extension to the ERC20 token standard to enforce compatibility with the EVC. Project making use of this extension can unlock an entirely new wave of composability. Users are no longer required to deposit their tokens into vaults in order to use them as collateral, they can do so directly from their wallet. This helps them retain their governance rights and other token privileges, whilst also helping avoid generating unnecessary taxable events. Whenever the user's balance decreases (outgoing transfer/token burn), the token contract calls into the EVC to check whether the outstanding loan rules are not violated. With an addition of a simple modifier which routes transfer calls through the EVC, mentioned account status checks can be deferred until the end of a batch of multiple operations, allowing a user to freely use their tokens within a batch as long as their account is solvent at the end. ERC20Collateral also makes the token compatible with EVC sub-accounts system out of the box. ### Use-cases and examples #### Leverage by chaining LRT/LST/ETH vaults * Create an vault for each major LST allowing all major LRTs as collateral. * Create a WETH vault that allows each of those major LSTs and each of the LRTs as collateral. * Use-case: LRTs depositors borrow LSTs, and LRTs + LSTs depositors borrow WETH, swap, re-deposit, and leverage their yield. Consequence: this special Euler WETH vault has the highest demand for borrowing of any vault in DeFi. #### Leveraged liquidity provision * Create a WETH vault and a LST vault that allow WETH/LST LP as collateral. * Use-case: LP token holders borrow more WETH and LST against their LP tokens and deposit into an AMM to get more LP tokens. * Consequence: LP token holders can leverage their LP positions whilst using simple, gas-efficient AMM protocols. #### Impermanent loss hedge * Create a WETH/USDC LP token vault that allows WETH and USDC as collateral. * Use-case: WETH and USDC token holders can borrow LP tokens to hedge or go short. * Consequence: LP token holders earn additional yield on their tokens, helping compensate against impermanent loss. #### USD carry trades * Create a custom vault pair that allows USDC to borrow USDT, and USDT to borrow USDC on high leverage. * Use-case: if USDC APY is higher than USDT APY, users can deposit USDC, borrow USDT, swap to USDC, and re-deposit to carry out a carry trade. * Consequence: users can hedge exposure to stablecoin depeg risk, carry out interest rate arbitrage, and profit from carry trades. #### Margin-trading real-world assets * Create a vault for USDC allowing a high-yielding RWAs as collateral, using hooks to enable secondary-transfer restrictions to be observed. * Use-case: RWA depositors borrow USDC at lower yield, swap to more RWA, and re-deposit, looping to go long. * Consequence: Margin trading on real-world assets as RWA depositors can leverage their yield and earn the interest rate spread on leverage ### Long-term picture The ability to lend and borrow digital assets is the foundation on which DeFi is built. Lending protocols are typically composed with decentralised exchanges (DEXs) in order to hedge risk and construct leveraged positions. In this way, borrowers pay interest to lenders, forming the foundation for capital markets in DeFi. Whilst lenders today have many options from which to earn sustainable and passive forms of yield, the trading experience for borrowers and traders remains remarkably poor. Monolithic lending protocols restrict borrowing with limited asset selections and conservative, one-size-fits-all loan-to-value (LTV) requirements, and then punish traders with heavy fines when they face liquidation. Meanwhile, isolated lending markets offer more flexibility, but often fragment liquidity and increase net costs for traders by disallowing rehypothecation and therefore extra yield on collateral. Moreover, in many cases traders are forced to navigate multiple protocols, governance systems, and user interfaces, paying leveraged fees to each along the way. Together, these market constraints and inefficiencies mean that many traders end up turning to CeFi platforms and relying on perpetual futures markets to put on trades, rather than using decentralised spot markets. This means lower yields for DeFi lenders and, consequently, lower liquidity in less capital efficiency in DeFi across the board. Euler v2 is a modular lending platform that aims to fix these problems and become the primary liquidity layer for DeFi. Monolithic lending protocols like Aave v3 help foster greater capital efficiency because they pool collateral used for different purposes together and enable rehypothecation. However, they only allow new collateral types to be added under restrictive economic conditions and typically only via governance actions. Isolated lending protocols like Compound v3 or Morpho Blue tend to allow greater flexibility in collateral use, but tend to fragment collateral and prevent rehypothecation, leading to lower capital efficiency. Euler’s modular architecture helps to solve the liquidity fragmentation problem associated with isolated pools by allowing permissionless creation of vaults that can use any other vault in the broader ecosystem as collateral. This ability to connect together different types of vaults from different product lines via the EVC provides unparalleled flexibility and modularity for lenders, borrowers, builders, traders, and more. Thanks to the modular design of the system, this can all be achieved without compromising on security or risk management. Vault-chaining via the EVC promises to enable new yield opportunities available nowhere else in DeFi today. With time, whole new product lines can be innovated and brought into the ecosystem helping to power vast network effects. Real-world assets, non-fungible tokens, IOUs for un-collateralised lending, peer-to-peer lending, oracle-free lending, and much more, are all possible directions for the growth of the ecosystem. With this design, together with other developments yet to be announced, Euler aims to become a global liquidity layer and one-stop shop for lending, borrowing, and trading on EVM-based networks. ### Acknowledgements With special thanks to Certora, Alberto Cuesta Cañada, Christoph Michel, and StErMi for helpful feedback on some of the mechanisms described herein. ## Reference Use this index to find Euler's canonical sources. For executable behavior, rely on deployed contracts and the relevant versioned repository. | Need | Canonical source | | ----------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | | Deployment addresses | [Contract addresses](/build/contract-addresses) and the [Euler interfaces repository](https://github.com/euler-xyz/euler-interfaces) | | ABIs and Solidity interfaces | [Euler interfaces](https://github.com/euler-xyz/euler-interfaces) and the relevant versioned contract repository | | Indexed API schemas | [Euler Data API V3](/build/data-querying/euler-v3-api) and its [OpenAPI document](https://v3.euler.finance/v3/openapi.json) | | Current aggregated onchain reads | [Lens contracts](/build/data-querying/lens-contracts) | | Display metadata and known-vault status | [Vault metadata](/build/data-querying/perspectives) and [labels](/curate/vaults/labeling) | | EUL token addresses and routes | [EUL addresses](/EUL/addresses) and [Multichain](/EUL/multichain) | | Governance proposals and treasury context | [DAO proposals](/euler-dao/proposals) and [DAO treasury](/euler-dao/treasury) | | Security review scope | [Audit index](/security/audits) and the linked report for the exact component and revision | For concepts and historical context, use the [Glossary](/glossary) and [Lite paper](/lite-paper). For task-oriented navigation, start with [Learn](/learn/vaults), [Use](/use/getting-started), [Build](/build), or [Curate](/curate). ## Coming from Aave or Morpho? If you know Aave or Morpho, Euler's core actions will feel familiar: supply, borrow, monitor account health, repay, and withdraw. The main difference is how lending markets are assembled. The comparison below is about protocol structure, not relative risk or performance. * Aave is built around shared lending markets, with asset-specific controls and risk settings applied inside those markets. * Morpho is built around immutable market definitions, often paired with curator-managed vault allocation. * Euler is built around isolated vaults that can connect into configurable markets. Each market defines its collateral, caps, oracle routes, LTVs, hooks, and governance. On Aave, you typically start from a reserve or market. On Morpho, you start from a market or vault. On Euler, start from a vault, then inspect how it connects to other vaults. The vault view shows the asset, accepted collateral, governor, oracle, interest-rate model, and limits that define the position. ### Quick translation | If you know\... | In Euler, think... | | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------ | | Aave reserve | A lending vault for one asset. | | Aave market | A group of connected lending vaults. | | Morpho Blue market | A lending relationship between a loan asset, collateral asset, oracle, rate model, and LTV. | | MetaMorpho vault | The closest analogue is an EulerEarn vault: one user position with allocation across configured strategies. | | Account health | A controller checks each Euler account against the collateral enabled for that account. Sibling sub-accounts are checked separately. | ### How Aave, Morpho, and Euler compare | Question | Aave | Morpho | Euler | | --------------------------- | ------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- | | What is the starting point? | A shared lending market with listed reserves. | An isolated market definition, often accessed through vaults. | Isolated vaults that can connect into configurable markets. | | How are assets added? | Assets are listed through governance or market-specific configuration. | Markets are defined by loan asset, collateral asset, oracle, rate model, and LTV choices. | Curators or builders deploy and configure vaults for assets, then connect them as supply, borrow, or collateral assets with the relevant parameters. | | How is risk isolated? | Risk settings apply across the market and its listed assets. | Each isolated market has its own risk settings, and vaults may allocate across markets. | Risk can be isolated at the vault or market level, while collateral can still compose where configured. | | How does collateral work? | Listed assets can be enabled as collateral within a market. | Each market pairs a loan asset with a collateral asset. | Vaults can accept other vault positions as collateral, so curators and builders can choose which vaults support which borrowing markets. | | What should users inspect? | Reserve configuration, caps, rates, collateral settings, and liquidation rules. | Market parameters, vault allocation, curator choices, oracle, rate model, and LTV. | Vault asset, collateral relationships, governor or curator depending on configuration, caps, LTVs, oracle routes, hooks, liquidity, and liquidation settings. | ### Where to start | Goal | Start here | | ----------------------- | ------------------------------------------------------------------------------------------------------------ | | Supply or borrow | [Use Euler](/use/getting-started), then review [Vaults](/learn/vaults) and [Markets](/learn/markets). | | Use an Earn vault | [EulerEarn](/use/euler-earn). | | Launch a lending market | [Curate](/curate) and the [EVK introduction](/curate/vaults/evk/introduction). | | Create an Earn vault | [EulerEarn vaults](/curate/vaults/euler-earn/introduction). | | Build an integration | [Build](/build), the [Euler SDK](/build/sdk), and the [EVC integration guide](/build/evc/integration-guide). | ## Protocol introduction **Euler V2** is a modular lending protocol built around independent vaults. Suppliers can lend assets, borrowers can use accepted collateral to borrow, and curators can assemble markets for different assets and risk preferences. EulerEarn adds single-asset vaults that allocate deposits across configured strategies. The protocol is permissionless: using the **Euler Vault Kit (EVK)**, anyone can deploy a configurable lending vault for an ERC20 asset. A market is formed by connecting vaults and choosing which collateral relationships, price oracles, interest-rate models, caps, and risk parameters apply. This design supports anything from a single collateral-and-debt pair to a larger cluster of connected vaults without forcing every user into one shared pool. ### What you can do * **Supply:** deposit an asset into an EVK lending vault or EulerEarn vault and receive ERC-4626 shares. * **Borrow:** provide collateral in a separate account and borrow from a vault that accepts it. * **Multiply:** use the app's prepared borrow-and-swap flow to build a leveraged position where a route is available. * **Curate:** deploy and configure vaults, connect collateral, and manage supported parameters. * **Build:** integrate with EVK vaults and coordinate multi-vault actions through the EVC. ### Key concepts * [**Euler Vault Kit (EVK):**](/learn/vaults) The smart contract framework used to create and manage individual lending and borrowing vaults. Each EVK vault is an ERC-4626 vault with borrowing logic. * **Vaults:** Lending vaults for a specific underlying asset. Users deposit assets and receive shares. Deposits may serve as collateral where another vault accepts them. Some vaults are **non-borrowable**, meaning deposits can be used as collateral but cannot be borrowed from that vault. * [**Oracles:**](/learn/price-oracles) Price feed contracts used for collateral valuation, debt valuation, and liquidation checks. Euler V2 supports multiple oracle types, including Chainlink, Pyth, Redstone, and Chronicle, with custom configurations per vault or router. * [**Interest-rate models (IRMs):**](/learn/interest-rates#irm-types) Configured models that provide a vault's borrow-rate input according to the model's logic. Supplier returns are derived from borrower interest, utilisation, fees, and vault accounting. Not every IRM is utilisation-based. * **Hook Targets:** Optional contracts that can check, restrict, or block selected vault operations before actions such as deposit, borrow, or liquidation. Hooks call designated **Hook Target** contracts, such as `HookTargetAccessControl` or `HookTargetAccessControlKeyring`, that implement the configured logic. * [**Ethereum Vault Connector (EVC):**](/build/evc) A core contract that acts as an alternate entry point for EVK vaults. The EVC coordinates cross-vault actions, batching, deferred checks, sub-accounts, operator permissions, and [permit-based execution (EIP-712)](https://eips.ethereum.org/EIPS/eip-712). * **Controller (EVC Context):** When a user borrows from a vault via the EVC, they designate that vault (or another contract) as a Controller for their EVC account. This grants the Controller authority over the user's enabled collateral set within the EVC, allowing it to enforce the borrowing vault's rules (e.g., prevent collateral withdrawal, seize collateral via `controlCollateral` during liquidation). * **Risk Management:** V2 uses isolated vaults and markets, vault-to-vault loan-to-value factors, caps, oracle configuration, and liquidation mechanisms. A vault's risk profile depends on its live configuration and market conditions. ### Euler V2 vs v1 While sharing the goal of efficient lending and borrowing, Euler V2 differs significantly from earlier versions: * **Architecture:** Earlier versions had a single, monolithic pool for all assets with cross-collateralization. V2 uses **isolated, permissionlessly deployable vaults** via the EVK. * **Risk:** Earlier shared-pool exposure is replaced by vault-specific assets, collateral links, oracle routes, LTVs, caps, and governance settings. Risk follows those settings and any connected collateral relationships. * **Asset Listing:** Earlier versions combined permissionless listing with governance-managed risk tiers. V2 keeps listing permissionless through **permissionless vault creation** for any ERC20, with risk parameters set by the vault creator instead of governance. * **Oracles:** V2 introduces a configurable oracle framework supporting multiple providers and per-vault or per-router configurations. * **Modularity:** V2 lets IRMs, oracles, hook targets, and governance models be tailored per market. ### Lending position mechanics 1. A supplier deposits an underlying asset into an EVK vault and receives ERC-4626 shares. Withdrawals depend on the vault's available liquidity and contract limits. 2. A borrower enables accepted collateral in an EVC account and designates a liability controller. The liability vault va
프로젝트로 돌아가기