Bridge Events
The arbitrum.bridge_events
table provides indexed views of all bridge transactions from or to a specified chain, and includes the other chain involved. All bridge events tables follow the same database schema presented below.
Columns
Name | Type | Description |
---|---|---|
block_number | integer |
The block number at which the event occurred. |
bridge_name | text |
The name of the bridge protocol that facilitated the event. |
contract_address | text |
The contract address where tokens were deposited to. |
contract_version | text |
The version of the bridge contract interacted with (e.g. v1 or v2 ). |
direction | text |
The direction of the bridge events with respect to the chain being queried (e.g. 'IN' or 'OUT'). |
from_address | text |
The address that sent tokens on the from_chain_id (null if not found). |
from_chain_id | text |
The name of the from chain (e.g. 'ETHEREUM', 'SOLANA', 'AVALANCHE'). |
from_quantity | numeric |
The quantity of the from_token_address . |
from_token_address | text |
The token address deposited on the from_chain_id (null if not found). |
from_transaction_hash | text |
The transaction hash on the from_chain_id in which tokens were bridged out of. |
log_index | integer |
The log index at which the event occurred. |
metadata | jsonb |
Protocol-specific metadata for the event (e.g. txn ID that links txns on each chain). |
timestamp | timestamp without time zone |
The timestamp at which the event occurred. |
to_address | text |
The address that received tokens on the to_chain_id (null if not found). |
to_chain_id | text |
The name of the to chain (e.g. 'ETHEREUM', 'SOLANA', 'AVALANCHE'). |
to_quantity | numeric |
The quantity of the to_token_address . |
to_token_address | text |
The token address unlocked on the to_chain_id (null if not found). |
to_transaction_hash | text |
The transaction hash on the to_chain_id in which tokens were bridged into. |
transaction_hash | text |
The transaction hash at which the event occurred. |
__block_number | integer |
An internal identifier for the indexer that updates this row. Use block_number instead when querying. |
__confirmed | boolean |
Flag indicating whether the transfer has been confirmed. |
Supported Protocols
Protocol | |||
---|---|---|---|
across-l2 | across-v1 | across-v2 | allbridge-core |
ankr-v1 | apex-pop-v2 | arbitrum-l1 | arbitrum-l2 |
arbitrum-native | arbitrum-outbox | arbitrum-v1 | arbitrum-v2 |
axelar-squid | axelar-v1 | battlefly-l2 | celer-original-token-vault |
celer-pegged-token-bridge | celer-v2 | celer-vault | chainbridge-v1-forks |
chainlink-v1 | chainlink-v2 | chainport-v1 | circle-v1 |
connext-v1 | debridge-dln | debridge-v1 | defiway-v1 |
deri-v2 | dforce-l2 | ethereum-max-l2 | evodefi-v1 |
frax-ferry | hashgold-l2 | hop-DAI | hop-ETH |
hop-HOP | hop-USDC | hop-USDT | hop-v1 |
hyperliquid-v1 | hyperliquid-v2 | hyphen-v2 | injective-outbox |
inspace-l1 | inspace-outbox | inspace-v2 | layer0-aptos |
layerswap-v1 | lido-l2 | lumiterra-l1 | lumiterra-outbox |
lumiterra-v2 | maya-v1 | merkly-v1 | meter-v1 |
multibit-v1 | multichain-v3 | multichain-v4 | multichain-v6 |
multichain-v7 | muster-l1 | muster-outbox | muster-v2 |
nativ3-l1 | nativ3-outbox | neuron-v1 | orb3-outbox |
orb3-v2 | orbiter-v1 | polychain-monsters-outbox | polynetwork-v1 |
rari-l1 | rari-outbox | rari-v2 | ren-v1 |
rhino-v1 | router-v1 | socket-dl | socket-refuel |
socket-supertoken | sphynx-v1 | stargate-v1 | swftswap-v1 |
sygma-v1-forks | symbiosis -v1 | symbiosis-v1 | synapse-v1 |
the-graph-l2 | wanchain-v1 | wormhole-core | wormhole-hashflow |
wormhole-l2 | xai-l1 | xai-outbox |
Indexes
Index |
---|
block_number, log_index |
__indexer_id, __block_number |
__indexer_id WHERE __confirmed = false |
transaction_hash, log_index |
timestamp, log_index |
from_token_address, timestamp, log_index |
to_token_address, timestamp, log_index |
from_address, timestamp, log_index |
to_address, timestamp, log_index |
from_chain_id, timestamp, log_index |
to_chain_id, timestamp, log_index |
bridge_name, timestamp, log_index |
metadata |
Got questions? Join our Discord
Discord is the primary home of the Transpose developer community. Join us to ask questions, share your work, and get help.