Skip to main content
Schema: near.defi Table: fact_bridge_activity Type: Base Table

​
Description

This table contains all cross-chain bridge transactions on the NEAR Protocol blockchain, capturing token movements between NEAR and other blockchains through various bridge protocols including Rainbow Bridge, Wormhole, Multichain, Allbridge, and Omni. The data includes bridge-specific details such as source/destination chains, token addresses, amounts, and bridge protocol metadata. This table provides the foundation for cross-chain analytics, bridge volume analysis, and multi-chain ecosystem monitoring.

​
Key Use Cases

  • Cross-chain bridge volume analysis and flow monitoring
  • Bridge protocol comparison and performance benchmarking
  • Cross-chain token flow analysis and liquidity tracking
  • Bridge security analysis and risk assessment
  • Multi-chain portfolio tracking and analysis
  • Bridge protocol adoption and user behavior analysis
  • Cross-chain arbitrage opportunity detection

​
Important Relationships

  • Links to core.fact_transactions through tx_hash for transaction context
  • Connects to core.fact_blocks through block_id for temporal context
  • Provides bridge data for defi.ez_bridge_activity with enhanced metadata
  • Supports defi.ez_intents with cross-chain intent analysis
  • Enables analysis in stats.ez_core_metrics_hourly for bridge metrics
  • Powers cross-protocol analysis with other DeFi activities

​
Commonly-used Fields

  • tx_hash: Essential for linking to transaction details and verification
  • block_timestamp: Primary field for time-series analysis and trend detection
  • source_chain and destination_chain: Critical for cross-chain flow analysis
  • token_address: Important for token-specific bridge activity analysis
  • amount_raw and amount_adj: Essential for bridge volume calculations
  • platform: Important for bridge protocol comparison and analysis
  • direction: Critical for understanding bridge flow direction (inbound/outbound)

​
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.
AMOUNT_ADJNUMBERDecimal adjusted amount of tokens (as float, rounded - use this generally). This field provides the token amount after applying the appropriate decimal precision adjustments based on the token’s decimal places. For example, if transferring 1 NEAR token, the amount_adj would be 1.0 after dividing the raw amount (1e24) by 10^24. This field is the most commonly used representation for token amounts in analytics and reporting as it provides human-readable values.
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. | | FACT_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. |