> ## Documentation Index
> Fetch the complete documentation index at: https://tokenterminal.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Registry

> Bridge identity travels on the transfers table itself.

There is no separate list of bridges. Every row of `facts.bridge_transfers` carries `app_id` for the bridge app, `product_id` for its version, and `project_id` for the project running it, which names the bridge a transfer went through without a join.

That means the list of bridges in the data is a group by over the transfers table. Filter on `block_timestamp` to keep the scan cheap.

## Sample queries

<Tabs>
  <Tab title="Bridges by app">
    **List the bridges active over a recent window.**

    ```sql theme={null}
    select
        app_id,
        project_id,
        product_id,
        count(*) as transfers
    from `facts.bridge_transfers`
    where block_timestamp >= timestamp('2026-08-01')
    group by app_id, project_id, product_id
    order by transfers desc
    ```
  </Tab>
</Tabs>

## Notes

The table carries the keys rather than any description, so a bridge's routes are read from the transfers themselves: `source_chain_id` and `destination_chain_id` show which chain pairs each bridge serves. [Transfers](/docs/catalog/bridges/transfers) documents every column, including the three above.