Are you an LLM? Read llms.txt for a summary of the docs, or llms-full.txt for the full context.
Skip to content

Overview

Euler V2 provides a modular architecture for accessing, analyzing, and visualizing protocol data. This section covers the technical approaches for extracting data from the protocol, whether you're developing dashboards, bots, risk assessment tools, or conducting research.

Main Tools and Interfaces

  • Euler V3 API: A hosted HTTP API for indexed protocol data, including chains, vaults, accounts, prices, APYs, rewards, liquidations, governance actions, and event timelines.
  • Lens Contracts: On-chain read-only contracts that aggregate and expose protocol state for easy querying (e.g., balances, positions).
  • Direct Contract Calls: Query vaults, the EVC, and other core contracts directly using Solidity, web3 libraries or block explorers.
  • Event Logs: Listen to protocol events for real-time or historical data extraction.
  • Subgraphs: Lightweight GraphQL indexes hosted on Goldsky for discovering active deposit and borrow positions across all sub-accounts.
  • Known Vault Endpoints: Public HTTP endpoints for checking which vaults are known (initial configuration reviewed at listing time) and fetching their metadata (name, curator, deprecation status).

What You'll Find in This Section

  • How to use lens contracts for efficient on-chain data access
  • How to use the Euler V3 API for indexed protocol data
  • How to query vaults, the EVC, and sub-accounts directly
  • How to work with protocol events for analytics and monitoring
  • How to discover account positions with the Euler simple subgraphs
  • How to get lists of known vaults and their metadata
  • How to fetch off-chain prices for analytics and valuations
  • How to work with pull-based oracles like Pyth for both querying and transactions

Special Considerations for Pull-Based Oracles

Some Euler V2 vaults rely on pull-based oracles like Pyth, which require special handling:

  • Short staleness periods: Prices are only valid for 2-3 minutes
  • Manual updates required: You must fetch and update prices before interactions
  • Simulation for queries: Use EVC's batchSimulation for data querying without executing transactions