Skip to content
Docs
Daemons
List of Daemons

List of Daemons

📰 Data from Yearn Meta

The Yearn Meta repository and API contains all the metadata of the Yearn ecosystem. Contents of the data directory are synced to IPFS for storage, accessible through our API meta.yearn.finance. Consistency of the stored data is verified by smalls scripts and schemas.
Yearn Meta is mostly used to provide some human classification or overwrite for some data.

Vaults from Meta

  • Endpoint: https://meta.yearn.finance/api/:chainID/vaults/all
  • Description: The vaults directory contains a bunch of relevant information about each Yearn Vaults.
  • Trigger: The Daemon will refresh the data every 24 hours to assert the data is up-to-date.
  • Automation: An external webhook is connected to the API to ask for a refresh of the data once a new commit to the master branch is performed on the Yearn Meta repository.

Tokens from Meta

  • Endpoint: https://meta.yearn.finance/api/:chainID/tokens/all
  • Description: The tokens directory contains a bunch of relevant information about each tokens that may exits in Yearn's ecosystem.
  • Trigger: The Daemon will refresh the data every 24 hours to assert the data is up-to-date.
  • Automation: An external webhook is connected to the API to ask for a refresh of the data once a new commit to the master branch is performed on the Yearn Meta repository.

Strategies from Meta

  • Endpoint: https://meta.yearn.finance/api/:chainID/strategies/all
  • Description: The strategies directory contains a bunch of relevant information about each strategies that may be attached to a Yearn Vault.
  • Trigger: The Daemon will refresh the data every 24 hours to assert the data is up-to-date.
  • Automation: An external webhook is connected to the API to ask for a refresh of the data once a new commit to the master branch is performed on the Yearn Meta repository.

🕸 Data from Subgraph

The Graph is an indexing protocol for querying networks like Ethereum and IPFS. Anyone can build and publish open APIs, called subgraphs, making data easily accessible. The Yearn's Subgraph repository is used to deploy and handle our subgraphs on the supported chainID.

💡

Subgraph is divided in two "versions", hosted and self-hosted. One is community driven while the other is the official one. Both are used the same way and both can be trusted, the community one acting as a fallback.

Token List from subgraph

  • Endpoint: The subgraph address if different for each chainID. For Mainnet, uri is https://thegraph.com/hosted-service/subgraph/rareweasel/yearn-vaults-v2-subgraph-mainnet.
  • Description: Perform a graphql request to get the list of all tokens that are registered in the subgraph, via a simple query: {vaults {shareToken {id} token {id}}}.
  • Trigger: The Daemon will refresh the data every 1 hour to assert the data is up-to-date.
  • Automation: No other automated is performed.

🔮 Data from Lens Oracle

Yearn Lens is a series of smart contracts that aggregate and format Yearn family protocol data into standardized interfaces. The oracle contract is responsible for fetching price information from various sources and is intended for non-critical off-chain calculations. Prices are returned in USDC.

Prices from Lens

  • Endpoint: Lens contract endpoints depends on the selected chain. Address for Mainnet is 0x83d95e0D5f402511dB06817Aff3f9eA88224B030.
  • Description: Call the getPriceUsdcRecommended function withing a multicall for each token supported by the Yearn ecosystem in order to get the USD price of each of them.
  • Trigger: The Daemon will refresh the data every 1 minute to assert the data is up-to-date.
  • Automation: No other automated is performed.

🪦 Data from v1 API

The Yearn V1 API is built based on the Yearn Exporter system, which collects realtime on-chain numeric data about all Yearn products and exposes it in multiple formats with an update every 30 minutes. The code is written in Python and mix data analysis with API purposes.

APY from V1

  • Endpoint: https://api.yearn.finance/v1/chains/:chainID/vaults/all.
  • Description: The API v1 is called in order to retrieve the APY information for all supported vaults.
  • Trigger: The Daemon will refresh the data every 10 minute to assert the data is up-to-date. Note that the endpoint is actually updated every 30 minutes.
  • Automation: No other automated is performed.