Ez Lending Deposits

-- 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;

-- 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)

-- 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

-- 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;
``` |
| 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**:
```sql
-- 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;
``` |
| 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**:
```sql
-- 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)

-- 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;
``` |