Registry

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

Bridges by app

List the bridges active over a recent window.

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

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 documents every column, including the three above.

⌘I

Overview

Core entities

Market verticals

Chain verticals

Sample queries

Notes

​Sample queries

​Notes

Sample queries

Notes