Transfers
Track movement of assets across major blockchain networks.
Transfers
The bridges.transfers
aggregates transaction-level bridge transfers across multiple blockchains indexed by Allium.
We are actively improving bridge protocol & blockchain coverage and data completeness for the bridges vertical.
Blockchain Coverage
The bridges.transfers
includes bridge transfers indexed from the following blockchains.
Blockchains | Total Blockchains Supported |
---|---|
arbitrum, avalanche, base, blast, bsc, ethereum, fantom, linea, mode, optimism, polygon, scroll, worldchain | 13 |
Source and Destination Blockchain Coverage
A bridge event connects a source blockchain (origin of the asset) to a destination blockchain (target for the bridged asset).
The total number of source and destination blockchains covered can be greater than the number of blockchains covered.
An example would be indexing the canonical bridge event of L2 Worldchain will allow us to cover bridge events between Ethereum<>Worldchain without indexing Worldchain events.
Distinct Source Blockchains | Distinct Destination Blockchains |
---|---|
61 | 139 |
Bridge Types
We broadly classify bridges into the following types:
- Applications bridges: bridges that have their underlying liquidity/mechanism to transfer assets across to typically more than one blockchain.
- Canonical bridges are bridges from Ethereum to a Rollup and serve as the “official” bridge for the roll-up/blockchain and service 1 destination blockchain.
- For Canonical Bridges protocols, OP (Optimism Stack) bridges and Arbitrum Bridges will include blockchains under the same ecosystem:
- Optimism Stack Bridges: includes Optimism, Base, Worldchain, Mode, Mint, Redstone, RSS3, Mantle, Manta, Blast, Fraxtal, Zora bridge and more
- Arbitrum Orbit Bridges: Arbitrum, Arbitrum Nova, Alienx
- For Canonical Bridges protocols, OP (Optimism Stack) bridges and Arbitrum Bridges will include blockchains under the same ecosystem:
Protocol Coverage
The bridge transfer schema supports both protocols across canonical and application bridge types.
Bridge Type | Direction | Protocols | Count |
---|---|---|---|
application | outbound only | circle_cctp, hop, across, synapse, celer, axelar, zkbridge, stargate, symbiosis, debridge, ybridge, eywa | 11 |
canonical | inbound and outbound | op, arbitrum, polygon, polygon_zkevm, near, sui, zk_shared_bridge, zksync, immutable_x, starknet, ronin | 11 |
Directional Coverage
Bridge transfer events include both inbound and outbound transfers. We include inbound and outbound bridge transfers for canonical bridges only.
- Canonical Bridges on Etheruem Mainnet
- Bridging direction
- Inbound: bridging from the Ethereum to the destination chain
- Outbound: briding back to Ethereum. E.g. for Base Bridge, this will be from Base -> Ethereum
- Bridging direction
- Application and Asset Bridges on EVM-Blockchains (including Ethereum)
- Bridging direction
- Outbound only: bridging from the source chain (if the transaction originated from Ethereum, this will be the source chain) to the destination
- Bridging direction
Sample Query
Finding the most popular bridge flows in the last month.
Columns
Unique key: unique_id
Column Name | Data Type | Description |
---|---|---|
bridge | VARCHAR | The slug or name of the bridge. For canonical bridges, the bridge name corresponds to the destination chain name. |
protocol | VARCHAR | The protocol associated with the bridge transfer. Optimism stack bridge events will share the same bridge protocol, op. |
contract_address | VARCHAR | The contract address of the bridge. |
event_name | VARCHAR | The name of the event that triggered the transfer. |
sender_address | VARCHAR | The address that initiated the transfer. |
recipient_address | VARCHAR | The address that received the transfer on the destination chain, if applicable. |
direction | VARCHAR | The direction of the transfer (e.g., inbound or outbound), based on the chain. |
source_chain_id | VARCHAR | The ID of the source chain. Note that for non-EVM chains, there is typically no chainID. |
source_chain | VARCHAR | The name of the source chain, i.e. the chain on which a token was originally deployed and minted. |
destination_chain_id | VARCHAR | The ID of the destination chain. Note that for non-EVM chains, there is typically no chainID. |
destination_chain | VARCHAR | The name of the destination chain, i.e. the chain on which a bridge user wants to have their tokens. |
token_in_address | VARCHAR | The address of the token being transferred. |
token_in_name | VARCHAR | The name of the token being transferred. |
token_in_symbol | VARCHAR | The symbol of the token being transferred. |
token_in_amount_raw | VARCHAR | The raw amount of the token being transferred. |
token_in_amount | FLOAT | The normalized amount of the token being transferred. |
usd_in_amount | FLOAT | The USD equivalent of the token being transferred. |
token_out_address | VARCHAR | (Nullable) The address of the token being transferred out. |
token_out_name | VARCHAR | (Nullable) The name of the token being transferred out. |
token_out_symbol | VARCHAR | (Nullable) The symbol of the token being transferred out. |
token_out_amount_raw | VARCHAR | (Nullable) The raw amount of the token being transferred out. |
token_out_amount | FLOAT | (Nullable) The normalized amount of the token being transferred out. |
usd_out_amount | FLOAT | (Nullable) The USD equivalent of the token being transferred out. |
usd_amount | FLOAT | The USD equivalent of the transfer, capped at a maximum value. |
extra_fields | VARIANT | Additional fields related to the transfer. |
transaction_from_address | VARCHAR | The address from which the transaction was sent. |
transaction_to_address | VARCHAR | The address to which the transaction was sent. |
transaction_hash | VARCHAR | The hash of the transaction. |
transaction_index | BIGINT | The index of the transaction within the block. |
log_index | BIGINT | The index of the log within the transaction. |
block_number | BIGINT | The number of the block containing the transaction. |
block_timestamp | TIMESTAMP_NTZ(9) | The timestamp of the block containing the transaction. |
block_hash | VARCHAR | The hash of the block containing the transaction. |
unique_id | VARCHAR | A unique identifier for the transfer. |
created_at | TIMESTAMP_NTZ(9) | The timestamp when the record was created. |
updated_at | TIMESTAMP_NTZ(9) | The timestamp when the record was last updated. |