SonarX

Indexed ElectroneumBlockchain Data

Electroneum has issued ETN since 2017, and the ledger carrying it now is the Electroneum Smart Chain, a Geth-based EVM network under Istanbul BFT that replaced the original chain outright.

Electroneum logo

How to query Electroneum data with SonarX

Instant Data Share

Available today

Snowflake, and file dumps to your object storage

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

Electroneum data: frequently asked questions

What is Electroneum?

Electroneum has issued ETN since 2017, when it launched as a mobile-first payments network, and the chain that carries it today is the Electroneum Smart Chain: an EVM network based on the Geth implementation of the Ethereum protocol, answering to chain ID 52014. Consensus is Istanbul BFT, so blocks are proposed and signed by a validator set, with a proposer signature and validator votes attached to each one, rather than being mined. ETN is the native asset and pays for the gas of every transaction and contract call. Execution is account-based over twenty-byte addresses with standard token interfaces. The move onto this chain was a replacement rather than an upgrade: holders’ funds were swept on the old ledger and re-issued here, which is why the two histories do not join.

Electroneum data on SonarX

SonarX indexes Electroneum 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 Electroneum on request. Kafka streaming can be enabled for Electroneum on request.

How SonarX indexes Electroneum

The opening of this chain does not look like organic activity. Balances were established by an oracle crediting addresses after funds were swept to a bridge address on the legacy ledger, so the earliest record for many holders is a protocol credit with no matching sender, and supply analysis that assumes every inbound transfer had a counterparty will misread the start of the series. After that the chain reads like any IBFT network: a signed block is final when it is committed, so nothing has to be withdrawn later, and there is no reorg depth to reason about. What remains chain-specific is that the pre-migration history belongs to a different ledger entirely.

What teams build with Electroneum data

Payment-flow reconstruction is the main workload: following ETN between users, merchants and exchanges at a volume where sampling is useless, which needs every transfer with its block and its fee. Token analytics covers the asset side of that work across networks. Supply and distribution accounting is the second job and is unusual here, because the opening balances were issued by the migration rather than earned or bought. Transaction monitoring is the third, where a business needs every deposit and withdrawal touching its own addresses matched against internal records. Teams looking at comparable consumer payment chains read Celo and TRON beside it.

Getting Electroneum 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. Electroneum coverage is provisioned on request, so tell us the history depth and the delivery target and we will scope it. 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 an Electroneum data API?

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

The indexed history is the Electroneum Smart Chain, from its first block forward, and it is provisioned on request as a data-share or a file delivery. The ledger that ran before the migration was a different chain with a different transaction format, so it is not part of this series. Real-time delivery keeps the same dataset current to chain tip and is enabled on request.

How did ETN balances reach the Electroneum Smart Chain?

By sweep and credit rather than by transfer. Funds on the legacy chain were moved to a bridge address there, and an oracle then dispatched matching transactions to each holder's address on the new chain. The consequence for analysis is that many opening balances have no counterparty a user recognizes: the first record for an address is a protocol credit, not a payment from another wallet.

Is Electroneum EVM-compatible?

Yes. The Electroneum Smart Chain is based on the Geth implementation of the Ethereum protocol, so Solidity contracts, twenty-byte addresses and standard token interfaces all behave as they do on Ethereum, and the chain answers to chain ID 52014. What differs is consensus: blocks are proposed and signed by a validator set under Istanbul BFT instead of being mined.

Electroneum logo

Get Electroneum data from SonarX