Skip to main content
Schema: aptos.defi Table: ez_bridge_activity Type: Base Table

​
Description

This table provides enriched bridge activity data for Aptos, combining raw on-chain bridge events from multiple protocols with token metadata (symbols, decimals) and price information. It includes decimal-adjusted amounts, token symbols, and USD values, making it suitable for analytics and reporting.

​
Key Use Cases

  • Analyzing cross-chain bridge flows and protocol usage in USD
  • Building dashboards for bridge volume, user activity, and token flows
  • Comparing bridge activity across protocols and tokens
  • Supporting DeFi and cross-chain research, monitoring, and reporting
  • Powering downstream models for DeFi and bridge aggregations

​
Important Relationships

  • Sources raw bridge data from defi.fact_bridge_activity
  • Joins token metadata from core.dim_tokens for symbol/decimals
  • Joins price data from price.ez_prices_hourly for USD values
  • Can be related to DEX swap data in defi.ez_dex_swaps for DeFi flow analysis

​
Commonly-used Fields

  • tx_hash, event_index: Unique identifiers for each bridge event
  • platform: Bridge protocol name
  • symbol: Token symbol being bridged
  • amount, amount_usd: Decimal-adjusted and USD value of bridge amount
  • sender, receiver: Addresses involved in the bridge event
  • block_timestamp: Time of the bridge event
  • source_chain, destination_chain: Names of source and destination chains

​
Columns

Column NameData TypeDescription
BLOCK_NUMBERNUMBERAlso known as block height. The block number indicates the position of a block in the blockchain, increasing sequentially after the addition of each new block.
Data type: Integer Example:
  • 12345678
  • 98765432
Business Context:
  • Primary identifier for ordering and filtering blockchain data chronologically.
  • Essential for block-level analysis and network growth tracking.
  • Enables correlation of transactions, transfers, and events to specific blocks. | | BLOCK_TIMESTAMP | TIMESTAMP_NTZ | The date and time at which the block was produced on the Aptos blockchain.
Data type: Timestamp Example:
  • 2024-01-15 14:30:25.123456
Business Context:
  • Primary field for time-series analysis and temporal filtering of blockchain activity.
  • Essential for trend analysis, volume calculations, and historical comparisons.
  • Enables time-based grouping and aggregation for analytics and reporting. | | VERSION | NUMBER | The version number, also known as the height, represents the sequential position of a transaction in the Aptos blockchain. The first transaction has a version of 0, and each subsequent transaction increments by 1.
Data type: Integer Example:
  • 0 (genesis transaction)
  • 12345678
  • 98765432
Business Context:
  • Unique identifier for ordering transactions chronologically across the entire blockchain.
  • Essential for transaction sequencing and version-based analysis.
  • Enables precise transaction tracking and blockchain state verification. | | TX_HASH | TEXT | Transaction hash is a unique 66-character identifier that is generated when a transaction is executed on the Aptos blockchain.
Data type: String Example:
  • 0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef
Business Context:
  • Primary identifier for linking transaction data across all related tables.
  • Essential for transaction verification and blockchain explorer lookups.
  • Enables correlation of transfers, events, and state changes to specific transactions. | | PLATFORM | TEXT | The platform or protocol from which the bridge transaction or event originates.
Data type: String Example:
  • LayerZero
  • Wormhole
  • Stargate
Business Context:
  • Used for identifying and analyzing bridge protocol usage.
  • Enables platform-level analytics, volume tracking, and protocol comparisons.
  • Supports bridge ecosystem analysis and user behavior insights. | | BRIDGE_ADDRESS | TEXT | The address of the contract responsible for handling the bridge deposit or transfer. This contract mediates the transfer and ensures that assets are sent and received appropriately.
Data type: String Example:
  • 0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef
Business Context:
  • Used for identifying bridge contracts and their deployment locations.
  • Enables contract-level analytics, security analysis, and bridge protocol tracking.
  • Supports bridge ecosystem monitoring and contract verification. | | EVENT_NAME | TEXT | The third segment of the event type, representing the specific resource or event name.
Data type: String Example:
  • DepositEvent
  • WithdrawEvent
  • TransferEvent
Business Context:
  • Essential for identifying the specific event type and resource.
  • Critical for event categorization and specific event analysis.
  • Enables resource-specific analytics and event type correlation. | | DIRECTION | TEXT | | | TX_SENDER | TEXT | The address of the originator account that initiated and signed the transaction on the Aptos blockchain.
Data type: String Example:
  • 0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef
Business Context:
  • Essential for user behavior analysis and wallet activity tracking.
  • Critical for transaction attribution and sender-based analytics.
  • Enables correlation with address labels for enhanced user profiling. | | SENDER | 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.
Data type: String Example:
  • 0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef
Business Context:
  • Used for tracking bridge users and their cross-chain activity.
  • Enables user-level analytics, bridge usage patterns, and sender behavior analysis.
  • Supports linking to address labels and user profiles. | | RECEIVER | TEXT | The designated address set to receive the bridged tokens on the target chain after the completion of the bridge transaction. For non-evm chains, the hex address is decoded/encoded to match the data format of the destination chain, where possible.
Data type: String Example:
  • 0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef
Business Context:
  • Used for tracking bridge recipients and cross-chain asset flows.
  • Enables user-level analytics, bridge destination patterns, and receiver behavior analysis.
  • Supports linking to address labels and user profiles across chains. | | SOURCE_CHAIN | TEXT | The name of the blockchain network from which the assets are being bridged.
Data type: String Example:
  • Ethereum
  • Polygon
  • Arbitrum
  • Optimism
Business Context:
  • Used for analyzing cross-chain asset flows and source chain preferences.
  • Enables chain-level analytics, volume tracking, and cross-chain comparisons.
  • Supports bridge ecosystem analysis and user behavior insights. | | DESTINATION_CHAIN | TEXT | The name of the blockchain network to which the assets are being bridged.
Data type: String Example:
  • Ethereum
  • Polygon
  • Arbitrum
  • Optimism
Business Context:
  • Used for analyzing cross-chain asset flows and destination preferences.
  • Enables chain-level analytics, volume tracking, and cross-chain comparisons.
  • Supports bridge ecosystem analysis and user behavior insights. | | TOKEN_ADDRESS | TEXT | The address associated with the token that is being bridged. It provides a unique identifier for the token within its origin blockchain.
Data type: String Example:
  • 0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef
Business Context:
  • Used for identifying bridged tokens and their cross-chain flows.
  • Enables token-level analytics, volume tracking, and cross-chain token analysis.
  • Supports bridge ecosystem monitoring and token flow visualization. | | SYMBOL | TEXT | The symbol of the token involved in the action (e.g., APT, USDC, USDT). Used to identify the asset type in analytics and reporting.
Data type: String Example:
  • APT
  • USDC
  • USDT
Business Context:
  • Enables grouping and filtering of transfers by token.
  • Supports analytics on asset flows, protocol usage, and user preferences.
  • Provides human-readable identification for tokens in reports and dashboards. | | AMOUNT_UNADJ | NUMBER | Original token amount without decimal adjustment.
Example: 1000500000 | | AMOUNT | FLOAT | Decimal-adjusted token amount for human-readable values. Example: 1000.50 | | AMOUNT_IN_USD | FLOAT | | | TOKEN_IS_VERIFIED | BOOLEAN | A flag indicating if the asset has been verified by the Flipside team. | | EVENT_INDEX | NUMBER | Unique identifier for an event within a transaction, representing the sequential order of events emitted during transaction execution. Data type: Integer Example:
  • 0 (first event in transaction)
  • 1 (second event in transaction)
  • 5 (sixth event in transaction)
Business Context:
  • Essential for determining the chronological order of events within a transaction.
  • Critical for event correlation and transaction flow analysis.
  • Enables precise event sequencing and debugging of complex transactions. | | EZ_BRIDGE_ACTIVITY_ID | TEXT | | | INSERTED_TIMESTAMP | TIMESTAMP_NTZ | The UTC timestamp when the row was inserted into the table, representing when the data was first recorded.
Data type: Timestamp Example:
  • 2024-01-15 14:30:25.123456
Business Context:
  • Essential for data lineage tracking and insertion timing analysis.
  • Critical for understanding data freshness and processing delays.
  • Enables data quality analysis and processing performance monitoring. | | MODIFIED_TIMESTAMP | TIMESTAMP_NTZ | The UTC timestamp when the row was last modified, representing when the data was most recently updated.
Data type: Timestamp Example:
  • 2024-01-15 14:30:25.123456
Business Context:
  • Essential for data freshness analysis and update tracking.
  • Critical for understanding data modification patterns and change frequency.
  • Enables data quality monitoring and update performance analysis. |