Skip to main content
Schema: near.defi Table: ez_bridge_activity Type: View

​
Description

This table provides an enhanced view of all cross-chain bridge transactions on the NEAR Protocol blockchain, combining raw bridge data with token metadata, pricing information, and cross-chain mapping details. The table includes both raw and adjusted amounts, USD values, and comprehensive token context across multiple bridge protocols including Rainbow Bridge, Wormhole, Multichain, Allbridge, and Omni. This easy view eliminates the need for complex joins and calculations, providing ready-to-use data for cross-chain analytics and bridge analysis.

​
Key Use Cases

  • Cross-chain bridge volume analysis with accurate decimal-adjusted amounts and USD values
  • Bridge protocol comparison and performance benchmarking with value context
  • Cross-chain token flow analysis and liquidity tracking
  • Bridge security analysis and risk assessment with economic impact
  • Multi-chain portfolio tracking and analysis
  • Bridge protocol adoption and user behavior analysis
  • Cross-chain arbitrage opportunity detection with value calculations

​
Important Relationships

  • Enhances defi.fact_bridge_activity with pricing and metadata from price.ez_prices_hourly
  • Combines token metadata from core.dim_ft_contract_metadata for complete token context
  • Enables analysis in stats.ez_core_metrics_hourly for bridge metrics
  • Provides foundation for all cross-chain analytics and reporting
  • Powers cross-protocol analysis with other DeFi activities

​
Commonly-used Fields

  • amount and amount_usd: Essential for accurate bridge volume analysis
  • block_timestamp: Primary field for time-series analysis and trend detection
  • source_chain and destination_chain: Critical for cross-chain flow analysis
  • platform: Important for bridge protocol comparison and analysis
  • direction: Critical for understanding bridge flow direction (inbound/outbound)
  • symbol: Important for token identification and cross-chain mapping
  • token_address: Essential for token-specific bridge activity analysis

​
Columns

Column NameData TypeDescription
BLOCK_IDNUMBERThe height of the chain this block corresponds with.
BLOCK_TIMESTAMPTIMESTAMP_NTZThe date and time at which the block began.
TX_HASHTEXTUnique identifier (hash) of this transaction.
TOKEN_ADDRESSTEXTThe contract address corresponding to the token, view details of the contract by following this address on the chain explorer.
AMOUNT_UNADJNUMBERUnadjusted amount of tokens as it appears on-chain (not decimal adjusted). This is the raw token amount before any decimal precision adjustments are applied. For example, if transferring 1 NEAR token, the amount_raw would be 1000000000000000000000000 (1e24) since NEAR has 24 decimal places. This field preserves the exact on-chain representation of the token amount for precise calculations and verification.
SYMBOLTEXTToken symbol (e.g., ‘wNEAR’, ‘SWEAT’). This field contains the abbreviated identifier for the token as commonly used in trading pairs, price feeds, and user interfaces. Token symbols are typically 2-6 characters long and provide a quick way to identify tokens without using their full contract addresses. Examples include ‘NEAR’ for the native token, ‘wNEAR’ for wrapped NEAR, and ‘USDC’ for USD Coin.
AMOUNTFLOATThe amount of tokens transferred
If in the ez* view, this number is decimal adjusted to actual amount. If in silver level or a fact* view, the raw amount is presented
PRICEFLOAT
AMOUNT_USDFLOATUSD value of the token transfer (null if hourly price not available). This field provides the dollar equivalent value of the token transfer by multiplying the decimal-adjusted token amount by the token’s USD price at the time of the transfer. This field is null when price data is unavailable, which can occur for new tokens, tokens with low liquidity, or during periods when price feeds are unavailable.
TOKEN_IS_VERIFIEDBOOLEANBoolean flag indicating whether the token or price record is verified by Flipside’s crosschain curation process. Verified tokens are prioritized for analytics and are considered reliable for most use cases. Unverified tokens may be incomplete, deprecated, or experimental.
DESTINATION_ADDRESSTEXTThe address tokens are being sent to, in a transfer or bridge transaction.
SOURCE_ADDRESSTEXTThe originating address from which tokens are being sent, in a transfer or bridge transaction.
This addressed is ascertained as best as possible, but may be null depending on the available information. Example 1 - tx CzPRdoiU74bo9yqqt9fCP5Xdab2mPVqxr9gU5xeaQA4a stores just “signer_public_key 0x0x1589…f694” on chain. Example 2 - tx FA7tQeGQnhminbas28YgaizwmT4vnEUiCr3vdXmN3Xjn does not log any signing address at all. | | PLATFORM | TEXT | The protocol utilized for the operation, likely a swap or bridge. | | BRIDGE_ADDRESS | TEXT | The address of the deployed contract for the token, nft, or other smart contract. | | DESTINATION_CHAIN | TEXT | The recipient blockchain in a bridge transaction. | | SOURCE_CHAIN | TEXT | The originating blockchain in a bridge transaction. | | METHOD_NAME | TEXT | Name of the method(s) approved for use. NULL if permission is FullAccess. | | DIRECTION | TEXT | Direction of funds through a bridge. Inbound = tokens bridged to Near ecosystem. Note - for the Rainbow bridge, inbound means Near or Aurora as tokens pass through Near to get to Aurora. | | RECEIPT_SUCCEEDED | BOOLEAN | Boolean indicating whether the receipt was successfully processed. This field tracks the execution status of the receipt, which is crucial for understanding transaction outcomes. While most transactions succeed, individual receipts within a transaction can fail due to various reasons such as insufficient gas, contract errors, or invalid parameters. This field is essential for filtering successful operations and analyzing failure patterns. | | EZ_BRIDGE_ACTIVITY_ID | TEXT | A unique identifier for the record. | | INSERTED_TIMESTAMP | TIMESTAMP_NTZ | The timestamp at which the record was initially created and inserted into this table. | | MODIFIED_TIMESTAMP | TIMESTAMP_NTZ | The timestamp at which this record was last modified by an internal process. |