Indexed BitTorrentBlockchain Data
BitTorrent Chain is the delegated proof-of-stake EVM network that moves assets between TRON, Ethereum and BNB Smart Chain, minting a mapped token on arrival rather than moving the original.
How to query BitTorrent Chain data with SonarX
Instant Data Share
Available todaySnowflake, and file dumps to your object storage
Query BitTorrent Chain 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 BitTorrent Chain 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 BitTorrent Chain 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 BitTorrent Chain 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 BitTorrent Chain activity within seconds
- Fraud and anomaly detection that has to fire before settlement
- Live dashboards and alerting on BitTorrent Chain 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
Available todayTables and REST
Read what a BitTorrent Chain 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 — on request
- Real-time balances API for latest and historical balances
- Batch API for wallets, tokens and balances in bulk
Used for:
- Reconstructing BitTorrent Chain 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 BitTorrent Chain balances on page load
- Compliance checks that read one BitTorrent Chain 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 BitTorrent Chain 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 BitTorrent Chain data behind their own API layer
BitTorrent Chain data: frequently asked questions
What is BitTorrent Chain?
BitTorrent Chain, usually written BTTC, is an EVM network that has been producing blocks since 2021, and it exists to move assets between TRON, Ethereum and BNB Smart Chain. Blocks are produced under proof of stake by a validator set that token holders delegate to, and the network answers to chain ID 199. Gas is paid in BTT, the token the BitTorrent brand is named for, which also circulates on TRON and Ethereum, so the fee asset here is not unique to this chain. Execution is the EVM, with twenty-byte addresses and the usual token standards, which is why contracts written for Ethereum deploy unchanged. Assets crossing its bridges arrive as mapped tokens: a deposit on a connected chain mints a matching token here rather than moving the original.
BitTorrent Chain data on SonarX
SonarX indexes BTTC blocks and headers, transactions and receipts, decoded event logs, execution traces including internal value transfers, and token transfers and balances. Mapped tokens keep their own contract identity, never merged by symbol.
Full historical coverage is available today as a data-share or a file delivery. Real-time delivery is enabled on request. The real-time balances API and the batch wallets, tokens and balances API are available for BitTorrent Chain, and the rest can be enabled on request. Kafka streaming can be enabled for BitTorrent Chain on request.
How SonarX indexes BitTorrent Chain
One asset with several identities is the problem this chain sets. A token bridged from Ethereum and the same token bridged from TRON are separate contracts here, so holder and supply analysis has to treat the origin chain as part of a token’s identity instead of matching on a symbol. Bridge records are the other half: a mint here corresponds to a lock on the source chain, and only one of those legs is in this dataset, so a flow model needs the connected networks indexed beside it.
What teams build with BitTorrent Chain data
Cross-chain token accounting is the first workload and the one this network exists to create: BTT and the assets mapped in from three chains have to be stated as one position, which means matching mints here against locks elsewhere. Bridge monitoring is the second, watching deposits and withdrawals for mismatched legs, which is a reconciliation job rather than a dashboard. Transfer analysis is the third, using decoded events to follow where mapped assets go once they arrive. Supply and distribution work of this kind runs through tokens and payments, and teams looking at the wider family usually pull TRON alongside it.
Getting BitTorrent Chain 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 streaming is provisioned on request. 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 BitTorrent Chain data API?
Yes. Real-time and batch APIs over indexed BitTorrent Chain data are available today, covering historical and latest balances and wallet, token and balance lookups in bulk. They read from the same indexed dataset as the Snowflake share and the file delivery, so an API answer and a warehouse query agree.
How do I get BitTorrent Chain 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 BitTorrent Chain coverage go?
The historical data-share and file delivery cover the chain from its 2021 launch forward, and are available today. The BTT token is older than the chain and has circulated on other networks since 2019, so a token history that starts before these blocks is a history of the token rather than of this network.
Is BitTorrent Chain the same thing as the file-sharing network?
No. BitTorrent is a file-transfer protocol with no blockchain in it. BitTorrent Chain, usually shortened to BTTC, is a separate proof-of-stake EVM network that shares the brand and uses BTT as its gas token. Nothing in this dataset describes file transfers: the records are blocks, transactions, logs and token transfers, the same object types as any other EVM chain.
Why does the same token appear more than once on BTTC?
Because assets arrive over three separate bridges. A token deposited from TRON and the same token deposited from Ethereum are minted as two different contracts here, each tracking its own source. Supply and holder analysis therefore has to carry the origin chain as part of a token's identity, because matching on the symbol alone merges balances that are not interchangeable.
