Overview
ClyptQ collects onchain data from two complementary sources:- RPC Direct Collection — Hourly granularity (1h). Direct blockchain node queries for gas, DeFi rates, stablecoin supply, DEX pools, exchange flow, whale transfers, and network metrics.
- DeFiLlama API — Daily granularity (1d). Aggregate chain-level TVL, DEX volume, fees/revenue, and stablecoin circulating supply across 20 chains.
1. RPC Direct Collection (1h)
Chain × Data Type Matrix
Data sources: Bitcoin = Mempool.space, EVM = Archive Node RPC, Others = chain-native RPC.
EVM DeFi Protocol Support
Not all EVM chains support the same DeFi protocols:DeFi Rates Fields (per chain)
Stablecoin Supply Fields
Data Types per Chain (Summary)
2. DeFiLlama API (1d)
All 27 chains receive the same 4 data types at daily granularity. No API key required.Supported Chains (from collect.yaml)
Chain slug-to-API-name mapping is loaded dynamically from
/v2/chains, with hardcoded fallback for offline use.
3. Coverage Summary
Tradeable Chains (Binance Futures)
RPC Configuration
EVM chains use Alchemy archive nodes by default for exchange flow and whale transfer data (requires archive access). Each chain reads its RPC URL from an environment variable, with public fallback for non-archive data:Using Onchain Data in Alphas
Onchain metrics flow into the graph as FIELD inputs, just like OHLCV data:Related Pages
- Data Sources Overview — All supported data types
- FRED Macro Data — Federal Reserve economic indicators
- AlphaOperator DSL — Using onchain data in alpha formulas

