Bridge Events
The polygon.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 |
The last block number in the batch that the data was updated in. |
__confirmed | boolean |
Flag indicating whether the transfer has been confirmed. |
Supported Protocols
Protocol | |||
---|---|---|---|
across-v1 | across-v2 | allbridge-core | allbridge-v1 |
axelar-squid | axelar-v1 | celer-v2 | connext-v1 |
debridge-v1 | hop-DAI | hop-ETH | hop-HOP |
hop-MATIC | hop-USDC | hop-USDT | hop-v1 |
hyphen-v1 | hyphen-v2 | layerswap-v1 | multichain-V4 |
multichain-V6 | multichain-v6 | multichain-v7 | optics-ERC20 |
orbiter-v1 | polygon-pos | swftswap-v1 | synapse-v1 |
wormhole-portal | wormhole-token |
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.