Skip to main content
Schema: ethereum.defi Table: ez_liquid_staking_deposits Type: View

What

This table provides comprehensive tracking of liquid staking deposits across major liquid staking derivative (LSD) protocols on Ethereum. It captures when users stake ETH and receive liquid staking tokens in return, enabling analysis of staking adoption, protocol market share, and capital flows into the liquid staking ecosystem.

Key Use Cases

  • Tracking liquid staking adoption and growth trends
  • Analyzing protocol market share and competitive dynamics
  • Understanding staker behavior and deposit patterns
  • Monitoring large deposits and whale activity
  • Calculating exchange rates between ETH and LSD tokens

Important Relationships

  • Links to core.fact_event_logs via tx_hash and event_index
  • Joins with ez_liquid_staking_withdrawals for full lifecycle tracking
  • References core.dim_contracts for protocol metadata
  • Connects to price.ez_prices_hourly for USD conversions

Commonly-used Fields

  • staker: Address performing the staking action
  • platform: Liquid staking protocol name
  • eth_amount: Amount of ETH staked
  • token_amount: LSD tokens received
  • token_symbol: Symbol of the LSD token (stETH, rETH, etc.)
  • block_timestamp: When the deposit occurred

Sample queries

-- Daily liquid staking deposits by protocol
SELECT
    DATE_TRUNC('day', block_timestamp) AS date,
    platform,
    COUNT(DISTINCT tx_hash) AS deposit_txns,
    COUNT(DISTINCT staker) AS unique_stakers,
    SUM(eth_amount) AS eth_staked,
    SUM(eth_amount_usd) AS usd_staked,
    AVG(eth_amount) AS avg_stake_size
FROM defi.ez_liquid_staking_deposits
WHERE block_timestamp >= CURRENT_DATE - 30
    AND eth_amount_usd IS NOT NULL
GROUP BY 1, 2
ORDER BY 1 DESC, 6 DESC;

-- Protocol market share analysis
WITH protocol_totals AS (
    SELECT
        platform,
        SUM(eth_amount) AS total_eth_staked,
        COUNT(DISTINCT staker) AS unique_stakers,
        COUNT(*) AS total_deposits
    FROM defi.ez_liquid_staking_deposits
    WHERE block_timestamp >= CURRENT_DATE - 90
        AND eth_amount IS NOT NULL
    GROUP BY platform
)
SELECT
    platform,
    total_eth_staked,
    total_eth_staked * 100.0 / SUM(total_eth_staked) OVER () AS market_share_pct,
    unique_stakers,
    total_deposits,
    total_eth_staked / total_deposits AS avg_deposit_size
FROM protocol_totals
ORDER BY total_eth_staked DESC;

-- Staker behavior patterns
WITH staker_activity AS (
    SELECT
        staker,
        COUNT(DISTINCT platform) AS protocols_used,
        COUNT(*) AS total_deposits,
        SUM(eth_amount) AS total_eth_staked,
        MIN(block_timestamp) AS first_stake,
        MAX(block_timestamp) AS last_stake,
        COUNT(DISTINCT DATE_TRUNC('month', block_timestamp)) AS active_months
    FROM defi.ez_liquid_staking_deposits
    WHERE eth_amount IS NOT NULL
    GROUP BY staker
)
SELECT
    CASE
        WHEN total_eth_staked < 1 THEN '< 1 ETH'
        WHEN total_eth_staked < 10 THEN '1-10 ETH'
        WHEN total_eth_staked < 32 THEN '10-32 ETH'
        WHEN total_eth_staked < 100 THEN '32-100 ETH'
        ELSE '100+ ETH'
    END AS staker_tier,
    COUNT(*) AS staker_count,
    AVG(total_deposits) AS avg_deposits_per_staker,
    AVG(protocols_used) AS avg_protocols_used,
    SUM(total_eth_staked) AS tier_total_eth
FROM staker_activity
GROUP BY staker_tier
ORDER BY MIN(total_eth_staked);

-- Exchange rate analysis (token received per ETH)
SELECT
    platform,
    token_symbol,
    DATE_TRUNC('day', block_timestamp) AS date,
    AVG(token_amount / NULLIF(eth_amount, 0)) AS avg_exchange_rate,
    MIN(token_amount / NULLIF(eth_amount, 0)) AS min_rate,
    MAX(token_amount / NULLIF(eth_amount, 0)) AS max_rate,
    COUNT(*) AS sample_size
FROM defi.ez_liquid_staking_deposits
WHERE eth_amount > 0
    AND token_amount > 0
    AND block_timestamp >= CURRENT_DATE - 30
GROUP BY 1, 2, 3
ORDER BY 1, 3 DESC;

-- Large deposits monitoring (whale activity)
SELECT
    block_timestamp,
    tx_hash,
    platform,
    staker,
    eth_amount,
    eth_amount_usd,
    token_symbol,
    token_amount,
    token_amount / NULLIF(eth_amount, 0) AS exchange_rate
FROM defi.ez_liquid_staking_deposits
WHERE eth_amount >= 100
    AND block_timestamp >= CURRENT_DATE - 7
ORDER BY eth_amount DESC;

-- Weekly staking momentum
WITH weekly_deposits AS (
    SELECT
        DATE_TRUNC('week', block_timestamp) AS week,
        platform,
        SUM(eth_amount) AS weekly_eth_staked,
        COUNT(DISTINCT staker) AS unique_stakers
    FROM defi.ez_liquid_staking_deposits
    WHERE block_timestamp >= CURRENT_DATE - 84
        AND eth_amount IS NOT NULL
    GROUP BY 1, 2
)
SELECT
    week,
    platform,
    weekly_eth_staked,
    LAG(weekly_eth_staked) OVER (PARTITION BY platform ORDER BY week) AS prev_week_eth,
    (weekly_eth_staked / NULLIF(LAG(weekly_eth_staked) OVER (PARTITION BY platform ORDER BY week), 0) - 1) * 100 AS week_over_week_pct,
    unique_stakers
FROM weekly_deposits
ORDER BY week DESC, weekly_eth_staked DESC;

Columns

Column NameData TypeDescription
BLOCK_NUMBERNUMBERSequential counter representing the position of a block in the blockchain since genesis (block 0).
Key Facts:
  • Immutable once finalized
  • Primary ordering mechanism for blockchain data
  • Increments by 1 for each new block
  • Used as a proxy for time in many analyses
Usage in Queries:
-- Recent data
WHERE block_number >= (SELECT MAX(block_number) - 1000 FROM fact_blocks)

-- Historical analysis
WHERE block_number BETWEEN 15000000 AND 16000000

-- Join across tables
JOIN <blockchain_name>.core.fact_event_logs USING (block_number)
Important: Block numbers are chain-specific. Block 15000000 on Ethereum ≠ block 15000000 on Polygon. | | BLOCK_TIMESTAMP | TIMESTAMP_NTZ | UTC timestamp when the block was produced by validators/miners. Format: TIMESTAMP_NTZ (no timezone) Precision: Second-level accuracy Reliability:
  • Set by block producer
  • Can have minor variations (±15 seconds)
  • Always increasing (newer blocks = later timestamps)
Best Practices:
-- Time-based filtering (most efficient)
WHERE block_timestamp >= DATEADD('day', -7, CURRENT_TIMESTAMP)

-- Hourly aggregations
DATE_TRUNC('hour', block_timestamp) AS hour

-- UTC date extraction
DATE(block_timestamp) AS block_date
Note: Use for time-series analysis, but be aware that block production rates vary by chain. | | ORIGIN_FUNCTION_SIGNATURE | TEXT | Function signature (first 4 bytes) of the called method. Format: 0x + 8 hex characters Common Signatures:
  • 0xa9059cbb: transfer(address,uint256)
  • 0x095ea7b3: approve(address,uint256)
  • 0x23b872dd: transferFrom(address,address,uint256)
Note: NULL for simple transfers or invalid calls | | ORIGIN_FROM_ADDRESS | TEXT | The externally-owned account (EOA) or contract address that initiated the transaction. Key Points:
  • Always 42 characters (0x + 40 hex chars)
  • Lowercase normalized in all tables
  • Cannot be NULL for valid transactions
  • For contract creation: sender of creation transaction
Common Patterns:
  • EOA → EOA: Simple transfer
  • EOA → Contract: User interaction
  • Contract → Contract: Internal calls (see fact_traces)
  • Known addresses: Exchange hot wallets, protocol deployers
Query Examples:
-- User activity analysis
SELECT from_address, COUNT(*) as tx_count
FROM <blockchain_name>.core.fact_transactions
WHERE block_timestamp >= CURRENT_DATE - 30
GROUP BY 1
ORDER BY 2 DESC;

-- New user detection
SELECT DISTINCT from_address
FROM <blockchain_name>.core.fact_transactions t1
WHERE NOT EXISTS (
    SELECT 1 FROM <blockchain_name>.core.fact_transactions t2
    WHERE t2.from_address = t1.from_address
    AND t2.block_number < t1.block_number
);
``` |
| ORIGIN_TO_ADDRESS | TEXT | The destination address for the transaction - either an EOA or contract address.

**Special Cases**:
- NULL: Contract creation transaction
- Contract address: Interacting with smart contract
- EOA address: Simple transfer or receiving funds

**Important Patterns**:
```sql
-- Contract deployments
WHERE to_address IS NULL

-- Popular contracts
SELECT to_address, COUNT(*) as interactions
FROM <blockchain_name>.core.fact_transactions
WHERE to_address IS NOT NULL
GROUP BY 1
ORDER BY 2 DESC;

-- Direct transfers only
WHERE to_address NOT IN (SELECT address FROM dim_contracts)
Note: For token transfers, this is the token contract, not the recipient. See ez_token_transfers tables for recipient. | | TX_HASH | TEXT | Unique 66-character identifier for the transaction. Format: 0x + 64 hexadecimal characters Usage:
  • Primary key for transaction lookups
  • Join key for traces, logs, and token transfers
  • Immutable once confirmed
Example: 0x5c504ed432cb51138bcf09aa5e8a410dd4a1e204ef84bfed1be16dfba1b22060 | | EVENT_INDEX | NUMBER | Zero-based sequential position of the event within a transaction’s execution. Key Facts:
  • Starts at 0 for first event
  • Increments across all contracts in transaction
  • Preserves execution order
  • Essential for deterministic event ordering
Usage Example:
-- Trace event execution flow
SELECT
    event_index,
    contract_address,
    topic_0,
    SUBSTRING(data, 1, 10) AS data_preview
FROM <blockchain_name>.core.fact_event_logs
WHERE tx_hash = '0xabc...'
ORDER BY event_index;
``` |
| EVENT_NAME | TEXT | The event name as defined in the contract's ABI.

**Format**: PascalCase event identifier
**Examples**:
- `Transfer` - Token transfers
- `Swap` - DEX trades
- `OwnershipTransferred` - Admin changes
- `Approval` - Token approvals

**Usage Pattern**:

```sql
-- Find all event types for a contract
SELECT DISTINCT event_name, COUNT(*) as occurrences
FROM ez_decoded_event_logs
WHERE contract_address = LOWER('0x...')
GROUP BY 1
ORDER BY 2 DESC;
``` |
| CONTRACT_ADDRESS | TEXT | Smart contract address that emitted this event or received the transaction.

**Key Points**:
- Always the immediate event emitter for logs
- May differ from transaction to_address
- Lowercase normalized format
- Never NULL for valid events |
| STAKER | TEXT | The address performing the staking or unstaking action.

Example: '0x1234567890123456789012345678901234567890' |
| PLATFORM | TEXT | The liquid staking protocol processing the transaction.

Example: 'lido' |
| TOKEN_SYMBOL | TEXT | The symbol of the liquid staking derivative token.

Example: 'stETH' |
| TOKEN_ADDRESS | TEXT | The contract address of the liquid staking token.

Example: '0xae7ab96520de3a18e5e111b5eaab095312d7fe84' |
| TOKEN_AMOUNT_UNADJ | NUMBER | The raw amount of liquid staking tokens without decimal adjustment.

Example: 999500000000000000 |
| TOKEN_AMOUNT | FLOAT | The decimal-adjusted amount of liquid staking tokens minted or burned.

Example: 0.9995 |
| TOKEN_AMOUNT_USD | FLOAT | The USD value of liquid staking tokens minted or burned.

Example: 2498.75 |
| ETH_AMOUNT_UNADJ | FLOAT | The raw amount of ETH without decimal adjustment.

Example: 1000000000000000000 |
| ETH_AMOUNT | FLOAT | The decimal-adjusted amount of ETH staked or withdrawn.

Example: 1.0 |
| ETH_AMOUNT_USD | FLOAT | The USD value of ETH staked or withdrawn.

Example: 2500.50 |
| EZ_LIQUID_STAKING_DEPOSITS_ID | TEXT | Primary key - unique identifier for each row ensuring data integrity.

**Format**: Usually VARCHAR containing composite key generated using MD5 hash of the relevant columns.
**Example**: MD5(block_number, tx_hash, trace_index)

**Usage**:
- Deduplication in incremental loads
- Join operations for data quality checks
- Troubleshooting specific records

**Important**: Implementation varies by table - check table-specific documentation. |
| INSERTED_TIMESTAMP | TIMESTAMP_NTZ | UTC timestamp when the record was first added to the Flipside database.

**Format**: TIMESTAMP_NTZ

**Use Cases**:
- Data freshness monitoring
- Incremental processing markers
- Debugging data pipeline issues
- SLA tracking

**Query Example**:
```sql
-- Check data latency
SELECT
    DATE_TRUNC('hour', block_timestamp) as block_hour,
    DATE_TRUNC('hour', inserted_timestamp) as insert_hour,
    AVG(TIMESTAMPDIFF('minute', block_timestamp, inserted_timestamp)) as avg_latency_minutes
FROM <blockchain_name>.core.fact_transactions
WHERE block_timestamp >= CURRENT_DATE - 1
GROUP BY 1, 2;
``` |
| MODIFIED_TIMESTAMP | TIMESTAMP_NTZ | UTC timestamp of the most recent update to this record.

**Format**: TIMESTAMP_NTZ

**Triggers for Updates**:
- Data corrections
- Enrichment additions
- Reprocessing for accuracy
- Schema migrations

**Monitoring Usage**:
```sql
-- Recently modified records
SELECT *
FROM <blockchain_name>.core.fact_transactions
WHERE modified_timestamp > inserted_timestamp
AND modified_timestamp >= CURRENT_DATE - 1;

-- Data quality tracking
SELECT
    DATE(modified_timestamp) as mod_date,
    COUNT(*) as records_updated,
    COUNT(DISTINCT block_number) as blocks_affected
FROM <blockchain_name>.core.fact_transactions
WHERE modified_timestamp > inserted_timestamp
GROUP BY 1
ORDER BY 1 DESC;
``` |