Ez Bridge Activity

Schema: sui.defi Table: ez_bridge_activity Type: Base Table

​

Description

This table provides cross-chain bridge analytics consolidating Sui Bridge and Wormhole events with protocol metadata, token pricing, and USD normalization. It tracks both inbound and outbound bridge transfers, enabling comprehensive analysis of cross-chain capital flows and bridge protocol usage.

​

Data Coverage

​

Key Use Cases

• Cross-chain capital flow tracking and bridge volume analysis
• Bridge protocol comparison and adoption metrics
• Security monitoring and risk assessment for bridge activity
• Multi-chain ecosystem studies and token migration tracking
• Bridge fee analysis and protocol economics
• Inbound vs. outbound flow analysis for Sui ecosystem

​

Important Relationships

• Sources data from bridge-specific event tables (Sui Bridge and Wormhole)
• Joins token metadata from core.dim_tokens for symbol/decimals
• Joins price data for USD value calculations
• Links to core.fact_transaction_blocks via tx_digest
• Links to core.fact_checkpoints via checkpoint_number

​

Commonly-used Fields

• tx_digest: Unique transaction identifier
• platform: Bridge protocol name (Sui Bridge or Wormhole)
• bridge_address: Smart contract address of the bridge
• source_chain: Origin blockchain for the transfer
• destination_chain: Target blockchain for the transfer
• amount_normalized: Decimal-adjusted transfer amount
• amount_usd: USD value of the bridge transfer
• token_symbol: User-friendly token identifier
• block_timestamp: Primary field for time-series analysis

​

Columns

Data type: Integer Example:

• 12345678
• 98765432

Business Context:

• Primary identifier for linking to checkpoint-level analysis.
• Essential for checkpoint-based filtering and aggregation.
• Enables correlation to consensus milestones. | | BLOCK_TIMESTAMP | TIMESTAMP_NTZ | The date and time at which the bridge transfer was finalized on the Sui blockchain.

Data type: Timestamp Example:

• 2025-01-15 14:30:25.123456

Business Context:

• Primary field for time-series analysis and temporal filtering of bridge activity.
• Essential for trend analysis, volume calculations, and historical comparisons.
• Enables time-based grouping and aggregation for analytics and reporting. | | TX_DIGEST | TEXT | 32-byte cryptographic transaction hash (Base58) identifying the transaction containing this bridge transfer.

Data type: String Example:

• 8vKzD3qFqE9yH2wN1xR5tB7aL4mP6sC3jG9kF1nV8xT2

Business Context:

• Primary identifier for linking bridge transfers to transaction context.
• Essential for transaction verification and correlation.
• Enables joining with other transaction-related data. | | TX_SENDER | TEXT | The Sui address that initiated the bridge transaction.

Data type: String Example:

• 0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef

Business Context:

• Essential for user activity tracking and wallet behavior analysis.
• Critical for identifying bridge users and usage patterns.
• Enables address-based filtering and user analytics. | | EVENT_INDEX | NUMBER | Zero-based sequential index of this bridge event within the transaction.

Data type: Integer Example:

• 0 (first bridge event in transaction)
• 1 (second bridge event in transaction)

Business Context:

• Essential for uniquely identifying bridge events within transactions.
• Critical for precise event ordering and analysis.
• Enables multi-event transaction tracking. | | PLATFORM | TEXT | The bridge platform name (Sui Bridge or Wormhole).

Data type: String Example:

• Sui Bridge
• Wormhole

Business Context:

• Essential for cross-protocol bridge comparison.
• Critical for platform-specific analytics and filtering.
• Enables bridge market share and adoption analysis. | | BRIDGE_ADDRESS | TEXT | Smart contract address of the bridge protocol.

Data type: String Example:

• 0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef

Business Context:

• Essential for protocol identification and verification.
• Critical for contract-level analytics.
• Enables protocol tracking and monitoring. | | SOURCE_CHAIN | TEXT | The blockchain from which tokens are being bridged.

Data type: String Example:

• Sui
• Ethereum
• Solana
• Arbitrum

Business Context:

• Essential for understanding capital flow origins.
• Critical for multi-chain ecosystem analysis.
• Enables source chain distribution tracking. | | DESTINATION_CHAIN | TEXT | The blockchain to which tokens are being bridged.

Data type: String Example:

• Sui
• Ethereum
• Solana
• Arbitrum

Business Context:

• Essential for understanding capital flow destinations.
• Critical for multi-chain ecosystem analysis.
• Enables destination chain distribution tracking. | | SOURCE_ADDRESS | TEXT | The address on the source chain sending the tokens.

Data type: String Example:

• 0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef

Business Context:

• Essential for cross-chain address tracking.
• Critical for multi-chain user analytics.
• Enables cross-chain portfolio analysis. | | DESTINATION_ADDRESS | TEXT | The address on the destination chain receiving the tokens.

Data type: String Example:

• 0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef

Business Context:

• Essential for cross-chain address tracking.
• Critical for multi-chain user analytics.
• Enables cross-chain portfolio analysis. | | COIN_TYPE | TEXT | The full Move type identifier for the token being bridged.

Data type: String Example:

• 0x2::sui::SUI
• 0x5d4b302506645c37ff133b98c4b50a5ae14841659738d6d733d59d0d217a93bf::coin::COIN

Business Context:

• Essential for token-specific filtering and analysis.
• Critical for linking to token metadata.
• Enables token flow tracking across chains. | | TOKEN_SYMBOL | TEXT | User-friendly symbol for the bridged token.

Data type: String Example:

• SUI
• USDC
• WETH

Business Context:

• Used for user-friendly displays and reports.
• Enables token-based filtering and grouping.
• Supports cross-token bridge analysis. | | TOKEN_DECIMALS | NUMBER | Decimal places for the bridged token.

Data type: Integer Example:

• 9 (SUI)
• 6 (USDC)
• 18 (WETH)

Business Context:

• Critical for converting raw amounts to decimal-adjusted values.
• Essential for accurate value calculations.
• Enables proper amount normalization. | | AMOUNT | NUMBER | The non-decimal adjusted (raw) amount of tokens bridged.

Data type: Integer Example:

• 1000000000 (for 1 SUI with 9 decimals)
• 1500000 (for 1.5 USDC with 6 decimals)

Business Context:

• Essential for reconstructing exact on-chain bridge values.
• Used for technical audits and precise calculations.
• Enables accurate volume tracking. | | AMOUNT_NORMALIZED | FLOAT | The decimal-adjusted amount of tokens bridged.

Data type: Decimal Example:

• 1.0
• 1.5
• 100.5

Business Context:

• Used for financial analysis and user-friendly reporting.
• Enables value-based calculations.
• Supports dashboards and analytics. | | AMOUNT_USD | FLOAT | The USD value of the bridged tokens at the time of transfer.

Data type: Decimal Example:

• 1.50
• 100.00
• null (if price unavailable)

Business Context:

• Used for financial analysis in USD terms.
• Enables value-based volume tracking.
• Supports cross-chain flow analysis in standardized currency. | | EZ_BRIDGE_ACTIVITY_ID | TEXT | Unique primary key identifier for each row.

Data type: String Example:

• 0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef

Business Context:

• Essential for data integrity.
• Critical for join operations.
• Enables precise data retrieval. | | INSERTED_TIMESTAMP | TIMESTAMP_NTZ | UTC timestamp when the row was inserted.

Data type: Timestamp Example:

• 2025-01-15 14:30:25.123456

Business Context:

• Essential for data lineage tracking.
• Critical for data freshness monitoring.
• Enables pipeline performance analysis. | | MODIFIED_TIMESTAMP | TIMESTAMP_NTZ | UTC timestamp when the row was last modified.

Data type: Timestamp Example:

• 2025-01-15 14:30:25.123456

Business Context:

• Essential for update tracking.
• Critical for data quality monitoring.
• Enables change detection. |