Indexed B2 NetworkBlockchain Data
B2 Network is a Bitcoin layer running an EVM priced in BTC, committing zero-knowledge proofs of its state into Bitcoin transactions rather than to an Ethereum contract.
How to query B2 Network data with SonarX
Instant Data Share
Available todaySnowflake, and file dumps to your object storage
Query B2 Network 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 B2 Network 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 B2 Network 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 B2 Network 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 B2 Network activity within seconds
- Fraud and anomaly detection that has to fire before settlement
- Live dashboards and alerting on B2 Network 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 B2 Network 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 B2 Network 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 B2 Network balances on page load
- Compliance checks that read one B2 Network 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 B2 Network 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 B2 Network data behind their own API layer
B2 Network data: frequently asked questions
What is B2 Network?
B2 Network is a Bitcoin layer that runs an EVM and prices everything in BTC. Gas is paid in bridged bitcoin, metered at eighteen decimals rather than in satoshis, and the network answers to chain ID 223. Execution is account-based with twenty-byte addresses and the usual token standards, so Solidity contracts deploy unchanged, while the chain those contracts ultimately lean on keeps no accounts at all. Zero-knowledge proofs of the network’s state are produced and committed into Bitcoin transactions, which is what anchors it, and the data those proofs cover is held by the network’s own availability arrangement rather than in an Ethereum blob. The result is a chain whose execution reads like an EVM rollup and whose settlement trail has to be read on a proof-of-work ledger.
B2 Network data on SonarX
SonarX indexes B2 Network blocks and headers, transactions and receipts, decoded event logs, execution traces including internal value transfers, and token transfers and balances, with BTC amounts carried at the chain’s own scale.
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 B2 Network on request. Kafka streaming can be enabled for B2 Network on request.
How SonarX indexes B2 Network
The two halves of this network keep different books, and reconciling them is the work. Balances here are account balances at eighteen decimals; the bitcoin behind them sits on Bitcoin as unspent outputs counted in satoshis, so a cross-chain figure is rescaled as well as re-modeled. Anchoring is the second half: proof commitments are written into Bitcoin transactions rather than verified by a contract, so tying execution to its anchor means reading a second chain, and the cadence of those commitments decides when a record is anchored.
What teams build with B2 Network data
Bridged-bitcoin accounting comes first: stating how much BTC the chain holds, and matching it against what was locked on Bitcoin, is a question no single balance answers. Anchoring verification is the second workload and is specific to this design, because the proof commitments that back the chain are Bitcoin transactions, so an auditor checking that the history was anchored is querying two chains at once. Position-level DeFi analytics is the third, denominated in BTC throughout, where a return series has to be measured in the same asset the position is held in. Teams comparing Bitcoin layers usually pull Bitlayer alongside this one, since the two solve the same problem with different machinery.
Getting B2 Network 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 when the anchoring side matters. 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 B2 Network data API?
Real-time and batch APIs over indexed B2 Network 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 B2 Network 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 B2 Network coverage go?
The full recorded history of the chain is available today as a data-share or a file delivery, with depth confirmed when the share is scoped. The Bitcoin transactions carrying its proof commitments are a separate history on a separate chain, so tell us whether an anchoring audit is part of the work and Bitcoin coverage is provisioned alongside.
How are B2 Network balances denominated?
In BTC, at eighteen decimals, which is the EVM convention rather than Bitcoin's. The same coin on Bitcoin is counted in satoshis at eight decimals, so every figure crossing between the two has to be rescaled as well as re-modeled, and a number copied across without that step is wrong by a factor of ten billion.
