SonarX

Indexed CyberBlockchain Data

Cyber is an OP Stack rollup built for social applications by the CyberConnect team, settling to Ethereum, paying gas in ETH, and carrying profiles, follow records and CyberID names.

Cyber logo

How to query Cyber data with SonarX

Instant Data Share

Available today

Snowflake, and file dumps to your object storage

Query Cyber 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 Cyber 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 Cyber 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 Cyber 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 Cyber activity within seconds
  • Fraud and anomaly detection that has to fire before settlement
  • Live dashboards and alerting on Cyber 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 Cyber 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 Cyber 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 Cyber balances on page load
  • Compliance checks that read one Cyber 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 Cyber 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 Cyber data behind their own API layer

Cyber data: frequently asked questions

What is Cyber?

Cyber is an EVM chain built from the OP Stack, live since 2024, and it settles to Ethereum rather than running a consensus of its own: blocks are sequenced here and posted there. Gas is paid in ETH, so the network has no native coin, and it answers to chain ID 7560. Execution is EVM-equivalent, so Solidity contracts deploy unchanged and their receipts, logs and traces read the way an Ethereum team expects. The chain comes from the team behind CyberConnect, a social graph protocol running since 2021, and its intended workload is social: profiles, follow records, and the CyberID names that attach a readable label to an address. CYBER, the ecosystem token, is a contract deployed at one address across several EVM networks, this one included, rather than the fee asset here.

Cyber data on SonarX

SonarX indexes Cyber blocks and headers, transactions and receipts, decoded event logs, execution traces including internal value transfers, and token transfers and balances, which here means profile updates, follow records and name registrations as much as payments. 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 Cyber on request. Kafka streaming can be enabled for Cyber on request.

How SonarX indexes Cyber

Because gas is ETH rather than a local coin, there is no native supply to track and fee accounting reads against the same asset a team already follows on Ethereum and on other rollups. The traffic matters more. Meaning here sits in calls whose value fields are zero: a follow, a profile update or a name registration is a log and an internal call, not a transfer, so a pipeline keyed on value movement records almost nothing that happened. CYBER’s contract shares an address with its copies on other networks, so any join keyed on the address alone collides across chains.

What teams build with Cyber data

Consumer cohort analysis is the first workload: which accounts arrived, what they did in their first week, and how much of that activity was contract calls rather than transfers. Name-record research is the second, tracing CyberID registrations and the addresses behind them over time. Token accounting is the third, and it depends on separating CYBER’s copies by network, because one address across five chains will otherwise read as one balance. Settlement reconciliation is a fourth, matching batches here against the Ethereum blocks that carry them. Wallet analytics covers holder-level work across chains, and teams studying consumer networks usually pull Zora alongside this one.

Getting Cyber 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. Cyber 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 Cyber data API?

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

The historical data-share and file delivery cover the chain from its first blocks forward, and are available today. This is a young network, so the whole record is small beside an established Layer 1 and a full backfill is quick to hand over. Real-time delivery keeps the same dataset current to chain tip and is enabled on request.

Does Cyber have its own gas token?

No. Fees are paid in ETH, so there is no separate native coin to account for and gas is denominated the way it is on Ethereum. CYBER exists as a token contract, deployed at the same address on Ethereum, Optimism, BNB Smart Chain, Base and Cyber itself, with a separate address on Solana. A holder study therefore has to say which network's copy it means.

Cyber logo

Get Cyber data from SonarX