Ez Bridge Activity

​

Description

​

Key Use Cases

• Analyze cross-chain liquidity flows and bridge protocol adoption
• Track token movements between Solana and other blockchains
• Study user behavior and protocol usage patterns for bridging
• Monitor USD-denominated bridge flows and capital movement
• Support analytics on multi-chain DeFi ecosystem growth and integration

​

Important Relationships

• Closely related to defi.fact_bridge_activity (raw bridge events), defi.ez_liquidity_pool_actions (for liquidity flows after bridging), and defi.ez_dex_swaps (for DEX activity of bridged tokens)
• Use defi.fact_bridge_activity for protocol-level bridge event details
• Use defi.ez_liquidity_pool_actions to analyze liquidity provision/removal after bridging
• Use defi.ez_dex_swaps to track trading activity of tokens post-bridge
• core.fact_transactions for transaction context

​

Commonly-used Fields

• block_timestamp: For time-series and bridge flow analysis
• platform: For protocol identification (Wormhole, DeBridge, Mayan, etc.)
• direction: For filtering inbound vs outbound transfers
• source_chain, destination_chain: For cross-chain analytics
• source_address, destination_address: For user and address-level analysis
• amount, amount_usd: For value and USD-denominated analytics
• mint, symbol, token_is_verified: For token and asset analytics
• succeeded: For transaction success analysis

​

Sample Queries

​

Daily bridge volume by protocol

-- Daily bridge volume by protocol
SELECT
    DATE_TRUNC('day', block_timestamp) AS date,
    platform,
    COUNT(DISTINCT tx_id) AS bridge_txns,
    SUM(amount_usd) AS volume_usd,
    COUNT(DISTINCT source_address) AS unique_users
FROM solana.defi.ez_bridge_activity
WHERE block_timestamp >= CURRENT_DATE - 30
    AND amount_usd IS NOT NULL
    AND succeeded = true
GROUP BY 1, 2
ORDER BY 1 DESC, 4 DESC;

​

Top bridge routes (source to destination chains)

-- Top bridge routes (source to destination chains)
SELECT
    source_chain,
    destination_chain,
    platform,
    COUNT(*) AS transfer_count,
    SUM(amount_usd) AS total_volume_usd,
    AVG(amount_usd) AS avg_transfer_usd
FROM solana.defi.ez_bridge_activity
WHERE block_timestamp >= CURRENT_DATE - 7
    AND destination_chain IS NOT NULL
    AND succeeded = true
GROUP BY 1, 2, 3
ORDER BY 5 DESC
LIMIT 20;

​

User bridge activity analysis

-- User bridge activity analysis
SELECT
    source_address,
    COUNT(DISTINCT DATE_TRUNC('day', block_timestamp)) AS active_days,
    COUNT(DISTINCT platform) AS protocols_used,
    COUNT(DISTINCT destination_chain) AS chains_bridged_to,
    SUM(amount_usd) AS total_bridged_usd,
    COUNT(*) AS total_transfers
FROM solana.defi.ez_bridge_activity
WHERE block_timestamp >= CURRENT_DATE - 30
    AND amount_usd > 100  -- Filter small transfers
    AND succeeded = true
GROUP BY 1
HAVING COUNT(*) > 5  -- Active bridgers
ORDER BY 5 DESC
LIMIT 100;

​

Token flow analysis

-- Token flow analysis
SELECT
    symbol,
    mint AS token_address,
    source_chain,
    destination_chain,
    COUNT(*) AS bridge_count,
    SUM(amount) AS total_amount,
    SUM(amount_usd) AS total_volume_usd,
    AVG(amount_usd) AS avg_transfer_usd
FROM solana.defi.ez_bridge_activity
WHERE block_timestamp >= CURRENT_DATE - 7
    AND symbol IS NOT NULL
    AND succeeded = true
GROUP BY 1, 2, 3, 4
HAVING COUNT(*) > 10
ORDER BY 7 DESC;

​

Bridge protocol comparison

-- Bridge protocol comparison
WITH protocol_stats AS (
    SELECT
        platform,
        COUNT(DISTINCT source_address) AS unique_users,
        COUNT(*) AS total_transfers,
        AVG(amount_usd) AS avg_transfer_size,
        PERCENTILE_CONT(0.5) WITHIN GROUP (ORDER BY amount_usd) AS median_transfer_size,
        SUM(amount_usd) AS total_volume
    FROM solana.defi.ez_bridge_activity
    WHERE block_timestamp >= CURRENT_DATE - 30
        AND amount_usd IS NOT NULL
        AND succeeded = true
    GROUP BY 1
)
SELECT
    platform,
    unique_users,
    total_transfers,
    avg_transfer_size,
    median_transfer_size,
    total_volume,
    total_volume * 100.0 / SUM(total_volume) OVER () AS market_share_pct
FROM protocol_stats
ORDER BY total_volume DESC;

​

Inbound vs Outbound flow analysis

-- Inbound vs Outbound flow analysis
SELECT
    DATE_TRUNC('day', block_timestamp) AS date,
    direction,
    platform,
    COUNT(*) AS transfer_count,
    SUM(amount_usd) AS volume_usd,
    COUNT(DISTINCT source_address) AS unique_users
FROM solana.defi.ez_bridge_activity
WHERE block_timestamp >= CURRENT_DATE - 14
    AND amount_usd IS NOT NULL
    AND succeeded = true
GROUP BY 1, 2, 3
ORDER BY 1 DESC, 5 DESC;

​

Large bridge transfers monitoring (whale activity)

-- Large bridge transfers monitoring (whale activity)
SELECT
    block_timestamp,
    tx_id,
    platform,
    direction,
    source_chain,
    destination_chain,
    source_address,
    destination_address,
    symbol,
    amount,
    amount_usd
FROM solana.defi.ez_bridge_activity
WHERE amount_usd >= 100000
    AND block_timestamp >= CURRENT_DATE - 7
    AND succeeded = true
ORDER BY amount_usd DESC;

​

Columns

• 123456789

• Supports block-level analytics, such as block production rate and transaction throughput.
• Useful for tracing transaction inclusion and block explorer integrations.

• All transactions with the same ‘block_id’ share the same ‘block_timestamp’. | | TX_ID | TEXT | The unique transaction signature (hash) for each transaction on the Solana blockchain. This field is a base58-encoded string, typically 88 characters in length, and serves as the primary identifier for transactions across all Solana data models. Used to join transaction data with related tables (blocks, events, transfers, logs, decoded instructions) and to trace the full lifecycle and effects of a transaction. Essential for transaction-level analytics, debugging, and cross-referencing with block explorers or Solana APIs.

• 5Nf6Q2k6v1Qw2k3v4Qw5Nf6Q2k6v1Qw2k3v4Qw5Nf6Q2k6v1Qw2k3v4Qw5Nf6Q2k6v1Qw2k3v4Qw

• Enables precise tracking, auditing, and attribution of on-chain activity
• Used for linking transactions to events, logs, and protocol actions
• Critical for compliance, monitoring, and analytics workflows | | SUCCEEDED | BOOLEAN | Boolean flag indicating whether the transaction was successfully executed and confirmed on the Solana blockchain. A value of TRUE means the transaction was processed without errors; FALSE indicates failure due to program errors, insufficient funds, or other issues.

• true
• false

• Used to filter for successful transactions in analytics and reporting.
• Important for error analysis, user experience, and program debugging. | | INDEX | NUMBER | | | PROGRAM_ID | TEXT | The unique public key (base58-encoded address) of a Solana program. This field identifies the on-chain program (smart contract) responsible for processing instructions, emitting events, or managing accounts. Used throughout Solana analytics models—including events, transactions, IDLs, and program activity tables—to join, filter, and analyze program-level data.

• “4Nd1mY…”
• “TokenkegQfeZyiNwAJbNbGKPFXCWuBvf9Ss623VQ5DA”

• Used as a join key for program activity, deployments, events, and interface changes.
• Supports segmentation of activity by protocol, DEX, NFT marketplace, or other on-chain application. | | PLATFORM | TEXT | The platform or protocol from which the bridge transaction or event originates. | | DIRECTION | TEXT | Indicates the direction in which the assets are being bridged, either inbound to Solana or outbound from Solana. | | SOURCE_CHAIN | TEXT | The name of the blockchain network to which the assets are being bridged from. | | DESTINATION_CHAIN | TEXT | The name of the blockchain network to which the assets are being bridged to. | | SOURCE_ADDRESS | TEXT | The address that initiated the bridge deposit or transfer. This address is the sender of the tokens/assets being bridged to the destination chain. | | DESTINATION_ADDRESS | TEXT | The designated address set to receive the bridged tokens on the target chain after the completion of the bridge transaction. | | AMOUNT | FLOAT | The decimal adjusted amount of tokens involved in the bridge transaction, where available. | | AMOUNT_USD | FLOAT | The value of the bridged tokens in USD at the time of the bridge transaction, where available. | | MINT | TEXT | The address associated with the token that is being bridged. It provides a unique identifier for the token within Solana. | | SYMBOL | TEXT | The symbol representing the token being bridged. This provides a shorthand representation of the token. | | TOKEN_IS_VERIFIED | BOOLEAN | A flag indicating if the asset has been verified by the Flipside team. | | EZ_BRIDGE_ACTIVITY_ID | TEXT | A unique, stable identifier for each record in this table. The primary key (PK) ensures that every row is uniquely identifiable and supports efficient joins, lookups, and data integrity across models. The PK may be a natural key (such as a blockchain transaction hash) or a surrogate key generated from one or more fields, depending on the table’s structure and requirements. | | INSERTED_TIMESTAMP | TIMESTAMP_NTZ | The timestamp when this transaction record was first inserted into the analytics database. Used for data freshness tracking and incremental model logic. Format: YYYY-MM-DD HH:MI:SS. Not derived from the blockchain, but from the ETL process. | | MODIFIED_TIMESTAMP | TIMESTAMP_NTZ | The timestamp when this transaction record was last updated in the analytics database. Used for tracking updates and supporting incremental model logic. Format: YYYY-MM-DD HH:MI:SS. Not derived from the blockchain, but from the ETL process. |