metrics.bridge_tokens_daily holds one row per token per day, totalled up from Transfers. It is keyed on the token_id that already exists in dimensions.tokens, and carries the money leaving and the money arriving as two separate columns.
Columns
| Column | Type | Description |
|---|---|---|
timestamp | TIMESTAMP | Day the row aggregates, truncated to UTC midnight. |
token_id | STRING | Token the row measures. Joins dimensions.tokens. |
source_transfer_volume | BIGNUMERIC | USD value of the token leaving its chain, counted on the day it left. Empty, not zero, on a day nothing left. |
destination_transfer_volume | BIGNUMERIC | USD value of the same money arriving, counted on the day it arrived. Leaves out transfers whose arriving token cannot be identified; CCIP arrivals name no token in the event, so this can read below the app tableβs arriving figure. |
Sample queries
- One token, both directions
- Tokens by outbound volume
Read one tokenβs daily bridge activity in both directions.
Notes
There is no single counted-once figure on this table. A transfer touches two chains, so one figure for it cannot sit on a key that names a single chainβs token; count transfers once from Transfers when the question needs it.source_transfer_volume and destination_transfer_volume describe one set of transfers from opposite ends, so adding the two together counts the same money twice.