How the Liquid Staking Map collects, processes, and presents protocol data across liquid staking, liquid restaking, and restaking categories.
Protocol-level data for all liquid staking, liquid restaking, and restaking protocols. Covers TVL (total and per-chain breakdown), multi-chain deployment data, audit history, hack/exploit events, and protocol metadata (launch date, category, social links).
Pool-level yield data for staking protocols. Provides base APY (organic staking yield), reward APY (token incentives), TVL per pool, underlying tokens, and chain. Pools are filtered to the three tracked categories with TVL above $10,000.
Per-protocol detail pages source audit reports, security incidents, governance links, and historical TVL breakdowns. Each protocol profile on the map links back to the DeFiLlama detail page for verification.
Protocols that accept native PoS tokens and issue a transferable liquid derivative (LST). The LST accrues staking rewards while remaining usable as DeFi collateral.
Protocols that wrap restaked ETH positions into transferable tokens (LRTs). The underlying ETH secures both Ethereum consensus and additional Actively Validated Services.
Base restaking platforms where staked ETH or LSTs opt into additional slashing conditions to provide economic security to external protocols (AVSs).
The pipeline runs every 6 hours as a scheduled cron job on a dedicated VPS. Each step runs sequentially.
Fetch all DeFiLlama protocols, filter to Liquid Staking + Liquid Restaking + Restaking categories, upsert into vault_protocols table
Fetch all DeFiLlama yield pools, match to tracked protocols by project name, upsert TVL, APY, and chain data per pool
Aggregate per-chain TVL and protocol counts from the multi-chain deployment data on each protocol record
Fetch audit count, hack history, and detail metadata per protocol. Served via ISR on protocol detail pages
Compute aggregate stats (total protocols, total TVL, chain count, average APY) for the homepage overview widget
All data on the Liquid Staking Map comes from public APIs with no manual curation or editorial filtering. Protocol inclusion is determined by DeFiLlama category classification. TVL and APY figures are reported as-is from DeFiLlama with no adjustments. The complete pipeline code is maintained by DIA and runs on infrastructure operated by DIA.