Skip to main content
Find answers to the most common questions about how vaults.fyi collects data, calculates yields, and decides which vaults to include.
While other applications calculate interest rates using varying assumptions and methodologies, vaults.fyi standardizes yield calculations across the entire platform.Yields are calculated as 1-day, 7-day, and 30-day trailing averages by observing changes in vault share price over each time frame. This approach provides a more accurate representation of vault performance compared to more volatile interest rates measured over shorter timeframes (such as a single block).Data for these calculations is fetched directly from the blockchain, minimizing assumptions and reliance on external APIs. For full details, see the Methodology page.
Data updates hourly. Onchain data is fetched once per hour.For use cases requiring more frequent data, the near-real-time (NRT) alpha endpoints return current vault share price, total assets, total supply, and underlying asset price outside the hourly cycle.
Vaults.fyi uses specialized smart contracts that fetch and transform onchain data in a single function call. These contracts are deployed as static calls — temporary reads that do not write to blockchain storage and therefore incur no gas costs.This architecture allows data from one read to feed directly into the next calculation within the same call, which is not possible with standard multi-call approaches. RPC providers including Infura, Alchemy, and Ankr are used to execute these calls. Once retrieved, the data is stored in the vaults.fyi backend database.Learn more in the Indexing Onchain Data methodology doc.
Some vaults update their earnings at irregular intervals rather than on every block. When a vault that has been accumulating yield for hours or days finally posts an update, the resulting share price jump creates a large but temporary spike in the calculated APY.Understanding this behavior is essential for accurately interpreting APY figures on vaults.fyi. For a detailed explanation, see Calculating APY.
Follow @vaultsfyi on X (formerly Twitter) for new product updates, newly added vaults, and insights on DeFi yield and TVL trends. The account also posts on Farcaster.You can also check the Changelog page for a week-by-week log of API and app updates.
Reach out to @vaultsfyi directly on X or Farcaster. The team actively monitors both channels for integration and feature requests.If you represent a protocol and want your vault added, submit the protocol request form. The team reviews each protocol before integrating and welcomes direct communications from protocol teams.
New vaults are added based on customer requests, with priority given to protocols with significant traction. The team started with yield opportunities for stablecoins, ETH, and liquid staking tokens across established DeFi protocols — including Aave, Compound, MakerDAO, Yearn, Lido stETH, and Rocket Pool rETH — and has since expanded coverage through user demand.If you represent a protocol, submit the protocol request form. The team researches each protocol before integrating.
For a vault to be included, all key data must be available onchain. From a contract address (or set of addresses), the following fields must be extractable:
  • tvl — total value locked in the vault, denominated in the underlying token
  • totalSupply — total supply of the LP token issued by the vault (if applicable)
  • pricePerShare — normally tvl / totalSupply, or an equivalent growth indicator if LP tokens are not used
  • maxDeposit — maximum amount of tokens any user can deposit
  • liquidity — amount of tokens directly available for withdrawal
  • asset — address of the underlying ERC-20 token
  • name — name of the vault
  • lpTokenAddress — address of the LP token issued by the vault
  • rewardTokens — addresses of reward tokens distributed by the vault
  • rewardTokenEmissionsPerSecond — emission rate of reward tokens
Vaults that conform to the ERC-4626 standard make this data straightforward to access. For vaults that require reading data from multiple contracts through a chain of calls, the team appreciates protocol teams reaching out with instructions on how to locate the fields above.