Indexed BOBBlockchain Data
BOB, short for Build on Bitcoin, is an OP Stack rollup in the Superchain that exists for bitcoin held onchain, with tBTC deposits verified against Bitcoin by contracts.
How to query BOB data with SonarX
Instant Data Share
Available todaySnowflake, and file dumps to your object storage
Query BOB blockchain data with plain SQL from a live database inside your own Snowflake account, populated with the indexed chain dataset. There is no pipeline to build and no second copy to store. The same dataset ships as file dumps to your own object storage for lakes and warehouses that are not Snowflake.
- Full history as a Snowflake data-share
- File dumps to S3 or your own object storage
- Real-time delivery, current to chain tip — on request
Used for:
- Analytics teams already on Snowflake that want BOB data beside their existing tables
- Fund accounting and treasury reporting that reconciles against a fixed history
- Cross-chain questions answered in one SQL statement instead of one query per chain
- Loading BOB history into BigQuery, Databricks, Redshift or a Spark lake
- Replacing a self-hosted indexer and the engineering time that keeps it running
- Serving one governed dataset to several desks without copying it per team
Kafka Streaming
Enabled on requestEvent stream
Consume BOB activity as a continuous stream of normalized records, produced as the chain is indexed instead of polled for.
Used for:
- Trading and execution systems that act on BOB activity within seconds
- Fraud and anomaly detection that has to fire before settlement
- Live dashboards and alerting on BOB wallet or protocol activity
- Feeding a stream processor that already reads from Kafka
- Keeping an internal store hot without waiting for a batch window
- Event-driven services that would otherwise poll on a timer
Balances
Enabled on requestTables and REST
Read what a BOB address held, either as it stands now or exactly as it stood at a past block or timestamp.
- Point-in-time balance tables, as at any block or timestamp
- Real-time balances API for latest and historical balances
- Batch API for wallets, tokens and balances in bulk
Used for:
- Reconstructing BOB portfolios and NAV as at a reporting date
- Audit and reconciliation work that has to be repeatable months later
- Wallet and portfolio products that render BOB balances on page load
- Compliance checks that read one BOB address at one block height
- Refreshing holdings for a whole book of accounts on a schedule
- Tax and cost-basis workflows that need holdings at each event
Realtime API
Enabled on requestREST over the indexed dataset
Query indexed BOB records over REST, reading the same dataset the share reads, with no warehouse in the path.
Used for:
- Applications that need one answer rather than a table scan
- Customer-facing screens where query latency is visible to a user
- Services that have no data warehouse and do not want to run one
- Prototyping against production data before committing to a share
- Backend checks that run per request instead of per batch
- Teams that want indexed BOB data behind their own API layer
BOB data: frequently asked questions
What is BOB?
BOB, short for Build on Bitcoin, is an EVM rollup that has settled to Ethereum since 2024 and belongs to the Superchain, the group of chains sharing Optimism’s stack. A sequencer orders transactions, batch data is posted to Ethereum as blobs, and withdrawals wait out the fault-proof window before they can be claimed on the L1 side. Gas is paid in ETH, execution is the EVM with twenty-byte addresses, and the network answers to chain ID 60808. What makes it its own network is the asset mix rather than the machinery: it exists for bitcoin held onchain, including tBTC, whose deposits are verified against Bitcoin by contracts rather than taken on trust. Bitcoin itself records nothing about this chain, so the two ledgers meet only where a bridge writes to both.
BOB data on SonarX
SonarX indexes BOB blocks and headers, transactions and receipts, decoded event logs, execution traces including internal value transfers, and token transfers and balances. Each BTC representation keeps its own contract identity.
Full historical coverage is available today as a data-share or a file delivery. Real-time delivery is enabled on request. Balance tables and the balance APIs can be enabled for BOB on request. Kafka streaming can be enabled for BOB on request.
How SonarX indexes BOB
A bitcoin position here is not one number. BTC cannot be native on an Ethereum rollup, so it arrives as several token contracts with different custody models and decimals, and exposure is the sum across them rather than a native balance. Mint and burn events on those contracts are the only onchain trace of what happened on Bitcoin, and that side is not in this dataset, so custody reconciliation needs both chains. Fees behave like any OP Stack chain’s, which keeps the cost model on Ethereum’s side even when the assets are Bitcoin’s.
What teams build with BOB data
Wrapped-BTC accounting is the first workload: stating how much bitcoin an address controls means resolving several contracts to one asset, and stating what the chain holds in total means doing that across every holder. Custody reconciliation is the second, matching mints and burns here against the Bitcoin transactions behind them, which is the check an auditor asks for rather than a summary. Position-level DeFi analytics is the third, since lending and liquidity on this chain are denominated in BTC and a return has to be measured in the same asset. Cost attribution runs underneath, because the L1 data component of a transaction is priced in ETH even where the position is not.
Getting BOB data from SonarX
Tell us the delivery target, how far back you need and how fresh it has to be, and the share is scoped against that. History is available now as a share or a file delivery, and Bitcoin coverage can be scoped beside it for the custody side. The published coverage matrix for every network SonarX indexes lives in the data documentation, and the rest of the catalogue is at all indexed chains.
Is there a BOB data API?
Real-time and batch APIs over indexed BOB data are enabled on request: the same indexed dataset the Snowflake share reads, served over REST once provisioned. Tell us the lookup pattern you need.
How do I get BOB data into Snowflake?
SonarX provisions a data-share into your own Snowflake account. The share appears as a database you query with SQL, so there is no pipeline to build and no second copy to store, and it stays current as SonarX advances the indexing pipeline.
How far back does BOB coverage go?
The historical data-share and file delivery cover the chain from its 2024 launch forward, and are available today. Deposits that funded positions here often start on Bitcoin, which is a separate history on a separate chain, so tell us if a flow model needs both sides and Bitcoin coverage is provisioned alongside.
How is a BTC balance on BOB put together?
By summing across several token contracts rather than reading one balance. Bitcoin cannot be native on an Ethereum rollup, so BTC arrives here as bridged and wrapped representations, each with its own contract, custody model and decimal convention. A holder's exposure is the total across them, and mint and burn events on those contracts are the only onchain trace of what happened on Bitcoin.
