Indexed VeChainBlockchain Data
VeChain, an enterprise proof-of-authority Layer 1 with 101 identified validators, splits its economics in two: VET holds value while VTHO pays for computation.
How to query VeChain data with SonarX
Instant Data Share
Available todaySnowflake, and file dumps to your object storage
Query VeChain 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 VeChain 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 VeChain 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
Balances
Enabled on requestTables and REST
Read what a VeChain 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 VeChain 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 VeChain balances on page load
- Compliance checks that read one VeChain 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 VeChain 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 VeChain data behind their own API layer
VeChain data: frequently asked questions
What is VeChain?
VeChainThor mined its genesis block in June 2018 and has been run as an enterprise ledger since: blocks arrive about every ten seconds, produced by an authority set of 101 validators whose operators are identified rather than anonymous. The economics are split across two assets. VET is the value token, VTHO pays for computation, and holding VET generates VTHO over time, so the cost of using the chain is separated from the price of holding it. Execution is EVM-compatible: Solidity written for Ethereum deploys unchanged, and VIP-180, the fungible token standard here, matches ERC-20 field for field. The transaction envelope is local. One transaction carries a list of clauses, each with a recipient, a value and calldata, and it can declare a dependency on another transaction along with a block reference and an expiry. Fee delegation under VIP-191 lets one party pay another’s gas.
VeChain data on SonarX
SonarX indexes VeChain blocks and headers, transactions and their clauses, receipts, decoded event logs, execution traces including internal value transfers, and VET, VTHO and VIP-180 balances. Those records land in the normalized model SonarX uses on every network it covers.
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 VeChain on request.
How SonarX indexes VeChain
Three properties break an Ethereum-shaped model. VTHO accrues to VET holders as protocol state rather than as transfers, so a VTHO balance rebuilt from transfer events is short by everything the protocol generated. A transaction is a list of clauses, so one hash can move value to several recipients and a one-row-per-transaction table drops the remainder without complaining. And under fee delegation the account that paid is often not the account that signed, so cost attribution reads the delegation rather than the sender. Block production rotates through a fixed authority set, which keeps the tip stable and takes reorganization handling out of ingestion.
What teams build with VeChain data
Two-token accounting is the recurring workload, because VTHO generated by holding VET has to be derived rather than counted, and a treasury report that misses it understates what the account earned. Cost reporting is the second, tying VTHO burned to the clauses and contracts that consumed it, which is how an enterprise sees what a process actually costs to run. Provenance-record research is the third, following the contracts that write product and document records over years rather than weeks. Token analytics covers the issuance side across chains, and teams looking at enterprise ledgers side by side usually pull XDC Network into the same warehouse.
Getting VeChain 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. VeChain history is available now, so a first delivery is provisioning rather than engineering. 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 VeChain data API?
Real-time and batch APIs over indexed VeChain 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 VeChain 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 VeChain coverage go?
The historical data-share and file delivery cover VeChainThor from its June 2018 genesis block forward, and are available today. The token's earlier life as an ERC-20 sits on Ethereum instead, so a study of holdings from before the swap reads that chain rather than this one. Real-time delivery keeps the same dataset current to chain tip and is enabled on request.
Is VeChain EVM-compatible?
Yes. VeChainThor executes Solidity bytecode, and VIP-180, its fungible token standard, matches ERC-20 field for field. Coverage tables that file VeChain under a non-EVM heading are describing how SonarX models the dataset, not the chain: the transaction envelope, the two-token fee model and fee delegation all differ from an Ethereum chain, while the contracts inside it do not.
How are multi-clause VeChain transactions indexed?
Clause by clause. One transaction here can carry a list of clauses, each with its own recipient, value and calldata, so a single hash may move value several times over. SonarX keeps each clause as its own record under the transaction that carried it, which is what stops a transfer view from reporting only the first movement and losing the rest of an enterprise batch.
