Skip to main content
Schema: somnia.defi Table: ez_lending_deposits Type: View

What

This table tracks all deposit transactions across lending protocols on EVM blockchains. Deposits represent users supplying liquidity to lending pools, earning yield while enabling their assets to serve as collateral for borrowing.

Key Use Cases

  • Calculating total value locked (TVL) by protocol
  • Analyzing deposit and withdrawal patterns
  • Tracking user liquidity provision behavior
  • Monitoring asset distribution across protocols
  • Identifying whale depositor activity

Important Relationships

  • Links to ez_lending_borrows for collateralization analysis
  • Joins with ez_lending_withdraws to track position lifecycle
  • References protocol-specific token contracts (aTokens, cTokens, etc.)
  • Connects to price.ez_prices_hourly for USD valuations

Commonly-used Fields

  • depositor: Address supplying liquidity
  • platform: Lending protocol name
  • token_address/token_symbol: Deposited asset details
  • amount/amount_usd: Deposit quantity and USD value
  • block_timestamp: When deposit occurred

Sample queries

-- Daily deposit volume and TVL calculation
WITH daily_metrics AS (
    SELECT 
        DATE_TRUNC('day', block_timestamp) AS date,
        platform,
        SUM(amount_usd) AS daily_deposits_usd,
        COUNT(DISTINCT depositor) AS unique_depositors
    FROM <blockchain_name>.defi.ez_lending_deposits
    WHERE block_timestamp >= CURRENT_DATE - 30
        AND amount_usd IS NOT NULL
    GROUP BY 1, 2
),
daily_withdrawals AS (
    SELECT 
        DATE_TRUNC('day', block_timestamp) AS date,
        platform,
        SUM(amount_usd) AS daily_withdrawals_usd
    FROM <blockchain_name>.defi.ez_lending_withdraws
    WHERE block_timestamp >= CURRENT_DATE - 30
        AND amount_usd IS NOT NULL
    GROUP BY 1, 2
)
SELECT 
    m.date,
    m.platform,
    m.daily_deposits_usd,
    COALESCE(w.daily_withdrawals_usd, 0) AS daily_withdrawals_usd,
    m.daily_deposits_usd - COALESCE(w.daily_withdrawals_usd, 0) AS net_flow_usd,
    SUM(m.daily_deposits_usd - COALESCE(w.daily_withdrawals_usd, 0)) 
        OVER (PARTITION BY m.platform ORDER BY m.date) AS cumulative_tvl_estimate
FROM daily_metrics m
LEFT JOIN daily_withdrawals w ON m.date = w.date AND m.platform = w.platform
ORDER BY m.date DESC, m.platform;

-- Wallet level deposit and withdraw analysis
SELECT 
    d.depositor,
    d.token_address AS collateral_token_address,
    d.token_symbol AS collateral_token_symbol,
    DATE_TRUNC('week', d.block_timestamp) AS weekly_block_timestamp,
    SUM(d.amount) AS total_deposit_amount,
    SUM(d.amount_usd) AS total_deposit_usd,
    SUM(w.amount) AS total_withdraw_amount,
    SUM(w.amount_usd) AS total_withdraw_usd,
    SUM(d.amount) - SUM(w.amount) AS net_collateral_amount,
    SUM(d.amount_usd) - SUM(w.amount_usd) AS net_collateral_usd
FROM 
    <blockchain_name>.defi.ez_lending_deposits d
LEFT JOIN <blockchain_name>.defi.ez_lending_withdraws w
    ON d.depositor = w.depositor
    AND d.token_address = w.token_address
WHERE 
    d.depositor = LOWER('<user_address>')
GROUP BY 1, 2, 3, 4;

-- Depositor behavior analysis
WITH depositor_activity AS (
    SELECT 
        depositor,
        COUNT(DISTINCT platform) AS platforms_used,
        COUNT(DISTINCT token_address) AS unique_assets,
        SUM(amount_usd) AS total_deposited_usd,
        MAX(block_timestamp) AS last_deposit,
        MIN(block_timestamp) AS first_deposit
    FROM <blockchain_name>.defi.ez_lending_deposits
    WHERE amount_usd IS NOT NULL
    GROUP BY 1
)
SELECT 
    CASE 
        WHEN platforms_used = 1 THEN 'Single Protocol'
        WHEN platforms_used = 2 THEN 'Two Protocols'
        ELSE 'Multi-Protocol'
    END AS user_type,
    COUNT(*) AS user_count,
    AVG(total_deposited_usd) AS avg_deposit_size,
    AVG(unique_assets) AS avg_assets_deposited,
    AVG(DATEDIFF('day', first_deposit, last_deposit)) AS avg_active_days
FROM depositor_activity
GROUP BY 1
ORDER BY 2 DESC;

-- Asset distribution by protocol
SELECT 
    platform,
    token_symbol,
    COUNT(*) AS deposit_transactions,
    SUM(amount) AS total_amount,
    SUM(amount_usd) AS total_usd,
    SUM(amount_usd) * 100.0 / SUM(SUM(amount_usd)) OVER (PARTITION BY platform) AS pct_of_protocol
FROM <blockchain_name>.defi.ez_lending_deposits
WHERE block_timestamp >= CURRENT_DATE - 30
    AND amount_usd IS NOT NULL
    AND token_symbol IS NOT NULL
GROUP BY 1, 2
ORDER BY 1, 6 DESC;

-- Large deposits monitoring (whale activity)
SELECT 
    block_timestamp,
    tx_hash,
    platform,
    depositor,
    token_symbol,
    amount,
    amount_usd
FROM <blockchain_name>.defi.ez_lending_deposits
WHERE amount_usd > 1000000
    AND block_timestamp >= CURRENT_DATE - 7
ORDER BY amount_usd 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: Important: Block numbers are chain-specific. Block 15000000 on Ethereum ≠ block 15000000 on Polygon.
BLOCK_TIMESTAMPTIMESTAMP_NTZUTC 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: Note: Use for time-series analysis, but be aware that block production rates vary by chain.
TX_HASHTEXTUnique 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
CONTRACT_ADDRESSTEXTSmart 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
EVENT_NAMETEXTThe 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:
EVENT_INDEXNUMBERZero-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:
ORIGIN_FUNCTION_SIGNATURETEXTFunction 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_ADDRESSTEXTThe 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:
ORIGIN_TO_ADDRESSTEXTThe 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: Note: For token transfers, this is the token contract, not the recipient. See eztokentransfers tables for recipient.
PLATFORMTEXTThe lending protocol where the transaction occurred. Example: ‘aave’
PROTOCOL_MARKETTEXTThe lending protocol’s receipt token issued to depositors. Example: ‘0xfedcbafedcbafedcbafedcbafedcbafedcbafed’
DEPOSITORTEXTThe address that supplied liquidity to the lending protocol. Example: ‘0x9876543210987654321098765432109876543210’
TOKEN_ADDRESSTEXTThe contract address of the underlying asset being lent or borrowed. Example: ‘0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48’
TOKEN_SYMBOLTEXTThe ticker symbol of the asset involved in the lending transaction. Example: ‘USDC’
AMOUNT_UNADJNUMBERThe raw amount of tokens borrowed or repaid without decimal adjustment. Example: 1000000000
AMOUNTFLOATThe decimal-adjusted quantity of tokens in the transaction. Example: 1000.5
AMOUNT_USDFLOATThe USD value of tokens at transaction time. Example: 1500.75
EZ_LENDING_DEPOSITS_IDTEXTPrimary 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(blocknumber, txhash, 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_TIMESTAMPTIMESTAMP_NTZUTC 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:
MODIFIED_TIMESTAMPTIMESTAMP_NTZUTC 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: