SonarX

Indexed TenetBlockchain Data

Tenet, an EVM Layer 1 on the Cosmos SDK, accepts more than its own token as stake: whitelisted derivatives such as wstETH and cbETH bond alongside TENET.

Tenet logo

How to query Tenet data with SonarX

Instant Data Share

Available today

Snowflake, and file dumps to your object storage

Query Tenet 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 Tenet 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 Tenet 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 request

Event stream

Consume Tenet 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 Tenet activity within seconds
  • Fraud and anomaly detection that has to fire before settlement
  • Live dashboards and alerting on Tenet 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 request

Tables and REST

Read what a Tenet 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 Tenet 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 Tenet balances on page load
  • Compliance checks that read one Tenet 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 request

REST over the indexed dataset

Query indexed Tenet 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 Tenet data behind their own API layer

Tenet data: frequently asked questions

What is Tenet?

Tenet is an EVM-compatible Layer 1 whose staking accepts more than its own token. Consensus is Diversified Proof of Stake, committed by a Tendermint validator set over a Cosmos SDK application, and the design is a module that wraps the chain’s native staking so whitelisted assets can be bonded alongside TENET. In practice that means liquid staking derivatives minted elsewhere, wstETH and cbETH among them, can be staked to a validator here while they keep earning the Ethereum staking yield they represent. TENET is the native asset, divisible to eighteen decimals, and it pays gas and carries governance: locking it produces vote-escrowed veTENET, and a longer lock produces more. The chain answers to chain ID 1559, and its mainnet beta opened in the fourth quarter of 2023.

Tenet data on SonarX

SonarX indexes Tenet blocks and headers, transactions and receipts, decoded event logs, execution traces including internal value transfers, and token transfers and balances, in the normalized model used on every chain SonarX 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 Tenet on request. Kafka streaming can be enabled for Tenet on request.

How SonarX indexes Tenet

Collateral is the awkward part. What secures a block can be a derivative token minted on another network, so a validator’s backing is an ERC-20 position whose meaning depends on what that token stands for where it was issued, and reading it takes both the transfers on this chain and the rate the derivative carried at the time. The second seam is that delegation, rewards and governance are recorded as Cosmos application state while contract calls are recorded as EVM transactions. One economic event can leave two differently shaped records, so a delegation series is assembled from the consensus side rather than from decoded logs.

What teams build with Tenet data

Validator and delegation accounting is the first workload, and it is unusual here: explaining a reward means knowing which derivative was bonded and what it was worth against its underlying at the time. SonarX’s staking solutions cover that class of work across the networks it indexes. Collateral analysis is the second job, since the chain’s stablecoin is issued against yield-bearing assets and its backing is only as legible as the token positions behind it. Cross-chain exposure mapping is the third: a wstETH balance recorded here is a claim on stake held on another network, so the position has two sides. Teams reading chains that import security from elsewhere put Core beside it.

Getting Tenet 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. Say if you need the consensus-side delegation records separated from EVM activity, since that split is easier to set at scoping time. 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 Tenet data API?

Real-time and batch APIs over indexed Tenet 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 Tenet 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 Tenet coverage go?

The historical data-share and file delivery cover Tenet's recorded history and are available today, back through the mainnet beta that opened in late 2023, with exact depth confirmed when the share is scoped. Real-time delivery keeps the same dataset current to chain tip and is enabled on request.

What can be staked to a Tenet validator?

Whitelisted assets as well as TENET itself, which is the point of the design. Liquid staking derivatives minted on other networks, wstETH and cbETH among them, can be bonded to a validator or delegated, so the backing behind a block can consist of tokens that are claims on stake held elsewhere. A stake figure here therefore only means something next to what the derivative represented at that time.

Tenet logo

Get Tenet data from SonarX