DefiLlama icon

DefiLlama

Access DeFi protocols data using the DefiLlama API

Overview

The node integrates with the DefiLlama API to fetch historical Total Value Locked (TVL) data aggregated across all blockchain chains combined. This operation is useful for users who want to analyze the overall TVL trends in the DeFi ecosystem over time, without focusing on individual chains or protocols.

Typical use cases include:

  • Tracking the growth or decline of total TVL in DeFi markets historically.
  • Feeding historical TVL data into dashboards or reports for financial analysis.
  • Comparing TVL trends with other metrics like volume or fees from different DeFi segments.

Example: A user can retrieve daily historical TVL values for the past months to visualize how the DeFi market capitalization has evolved.

Properties

Name Meaning
Additional Fields Collection of optional parameters to customize the request. For this operation, no specific additional fields are used.

Note: The "Additional Fields" property includes many options but most apply to other resources/operations. For the "TVL" resource and "Get Historical TVL" operation, no additional fields are applicable.

Output

The output JSON contains an array of historical TVL data points representing the combined TVL of all chains over time.

Each item typically includes:

  • date: Timestamp of the data point (likely in UNIX seconds).
  • totalLiquidityUSD or similar field: The total value locked in USD at that date.
  • Possibly other metadata related to the TVL snapshot.

Additionally, the node formats some numeric values into human-readable currency strings (e.g., "$1.23B") under formatted fields if present.

If AI Agent Mode is enabled via additional fields (not typical for this operation), the output will be simplified and include a summary string describing the data.

Dependencies

  • Requires access to the public DefiLlama API endpoint: https://api.llama.fi/v2/historicalChainTvl
  • No mandatory API key or authentication is required, but the node supports using an API key credential if available.
  • Uses the Axios HTTP client internally to perform GET requests.

Troubleshooting

  • No Data Returned: If the API returns no data, ensure the DefiLlama service is operational and the network connection is stable.
  • API Errors: Since this operation does not require parameters beyond resource and operation, errors are unlikely unless the API endpoint changes or is deprecated.
  • Rate Limits: Excessive requests may be throttled by DefiLlama; consider adding delays or caching results.
  • Unexpected Output Format: If the API response structure changes, the node's formatting logic might fail or produce incomplete data.

Links and References


This summary focuses exclusively on the "TVL" resource with the "Get Historical TVL" operation as requested.

Discussion