Ez Lending Repayments

-- Daily repayment volume and metrics
SELECT
    DATE_TRUNC('day', block_timestamp) AS date,
    platform,
    COUNT(*) AS repayment_count,
    COUNT(DISTINCT borrower) AS unique_borrowers,
    SUM(amount_usd) AS total_repaid_usd,
    AVG(amount_usd) AS avg_repayment_size_usd
FROM <blockchain_name>.defi.ez_lending_repayments
WHERE block_timestamp >= CURRENT_DATE - 30
    AND amount_usd IS NOT NULL
GROUP BY 1, 2
ORDER BY 1 DESC, 5 DESC;

-- Loan duration analysis
WITH loan_lifecycles AS (
    SELECT
        b.borrower,
        b.platform,
        b.token_symbol,
        b.block_timestamp AS borrow_time,
        MIN(r.block_timestamp) AS first_repayment_time,
        SUM(b.amount_usd) AS borrowed_usd,
        SUM(r.amount_usd) AS total_repaid_usd
    FROM <blockchain_name>.defi.ez_lending_borrows b
    INNER JOIN <blockchain_name>.defi.ez_lending_repayments r
        ON b.borrower = r.borrower
        AND b.platform = r.platform
        AND b.token_address = r.token_address
        AND r.block_timestamp > b.block_timestamp
    WHERE b.block_timestamp >= CURRENT_DATE - 90
        AND b.amount_usd IS NOT NULL
        AND r.amount_usd IS NOT NULL
    GROUP BY 1, 2, 3, 4
)
SELECT
    platform,
    token_symbol,
    AVG(DATEDIFF('day', borrow_time, first_repayment_time)) AS avg_days_to_first_repayment,
    PERCENTILE_CONT(0.5) WITHIN GROUP (ORDER BY DATEDIFF('day', borrow_time, first_repayment_time)) AS median_days,
    COUNT(*) AS loan_count,
    AVG(total_repaid_usd / NULLIF(borrowed_usd, 0) - 1) * 100 AS avg_interest_paid_pct
FROM loan_lifecycles
GROUP BY 1, 2
HAVING COUNT(*) > 10
ORDER BY 3;

-- Repayment patterns by user segment
WITH user_repayment_stats AS (
    SELECT
        borrower,
        COUNT(*) AS repayment_count,
        SUM(amount_usd) AS total_repaid_usd,
        AVG(amount_usd) AS avg_repayment_size,
        COUNT(DISTINCT DATE_TRUNC('month', block_timestamp)) AS active_months,
        COUNT(DISTINCT token_address) AS unique_assets_repaid
    FROM <blockchain_name>.defi.ez_lending_repayments
    WHERE block_timestamp >= CURRENT_DATE - 180
        AND amount_usd IS NOT NULL
    GROUP BY 1
)
SELECT
    CASE
        WHEN total_repaid_usd < 1000 THEN 'Micro (<$1K)'
        WHEN total_repaid_usd < 10000 THEN 'Small ($1K-$10K)'
        WHEN total_repaid_usd < 100000 THEN 'Medium ($10K-$100K)'
        WHEN total_repaid_usd < 1000000 THEN 'Large ($100K-$1M)'
        ELSE 'Whale (>$1M)'
    END AS borrower_segment,
    COUNT(*) AS borrower_count,
    AVG(repayment_count) AS avg_repayments_per_user,
    AVG(avg_repayment_size) AS avg_repayment_size,
    AVG(active_months) AS avg_active_months
FROM user_repayment_stats
GROUP BY 1
ORDER BY 2 DESC;

-- Asset-specific repayment velocity
SELECT
    token_symbol,
    platform,
    COUNT(*) AS repayment_transactions,
    COUNT(DISTINCT borrower) AS unique_repayers,
    SUM(amount_usd) AS total_usd_repaid,
    AVG(amount_usd) AS avg_repayment_usd,
    SUM(amount_usd) / COUNT(DISTINCT DATE_TRUNC('day', block_timestamp)) AS daily_velocity_usd
FROM <blockchain_name>.defi.ez_lending_repayments
WHERE block_timestamp >= CURRENT_DATE - 30
    AND token_symbol IS NOT NULL
    AND amount_usd IS NOT NULL
GROUP BY 1, 2
HAVING COUNT(*) > 50
ORDER BY 8 DESC;

-- Large repayments monitoring
SELECT
    block_timestamp,
    tx_hash,
    platform,
    borrower,
    payer,
    token_symbol,
    amount_usd,
    CASE WHEN borrower = payer THEN 'Self' ELSE 'Third-party' END AS repayment_type
FROM <blockchain_name>.defi.ez_lending_repayments
WHERE amount_usd > 500000
    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

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

-- 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;
``` |
| 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 |
| 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;
``` |
| PLATFORM | TEXT | The lending protocol where the transaction occurred.

Example: 'aave' |
| PAYER | TEXT | The address that paid the loan or deposit.

Example: '0x5555555555555555555555555555555555555555' |
| BORROWER | TEXT | The address that initiated a borrow or repayment transaction.

Example: '0x1234567890123456789012345678901234567890' |
| PROTOCOL_MARKET | TEXT | The lending protocol's receipt token issued to depositors.

Example: '0xfedcbafedcbafedcbafedcbafedcbafedcbafed' |
| TOKEN_ADDRESS | TEXT | The contract address of the underlying asset being lent or borrowed.

Example: '0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48' |
| TOKEN_SYMBOL | TEXT | The ticker symbol of the asset involved in the lending transaction.

Example: 'USDC' |
| AMOUNT_UNADJ | NUMBER | The raw amount of tokens borrowed or repaid without decimal adjustment.

Example: 1000000000 |
| AMOUNT | FLOAT | The decimal-adjusted quantity of tokens in the transaction.

Example: 1000.5 |
| AMOUNT_USD | FLOAT | The USD value of tokens at transaction time.

Example: 1500.75 |
| EZ_LENDING_REPAYMENTS_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;
``` |