Indexed RolluxBlockchain Data
Rollux is an OP Stack rollup that settles to Syscoin instead of Ethereum, paying fees in SYS and publishing its data through PoDA, which puts merge-mined proof of work behind its finality.
How to query Rollux data with SonarX
Instant Data Share
Available todaySnowflake, and file dumps to your object storage
Query Rollux 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 Rollux 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 Rollux 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 Rollux 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 Rollux activity within seconds
- Fraud and anomaly detection that has to fire before settlement
- Live dashboards and alerting on Rollux 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 requestTables and REST
Read what a Rollux 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 Rollux 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 Rollux balances on page load
- Compliance checks that read one Rollux 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 Rollux 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 Rollux data behind their own API layer
Rollux data: frequently asked questions
What is Rollux?
Rollux is an EVM rollup that has produced blocks since June 2023, and the chain it settles to is Syscoin rather than Ethereum. It is built from the OP Stack, is EVM-equivalent, and produces blocks about every two seconds. Fees are paid in SYS, the same coin Syscoin uses, under an EIP-1559 fee market, and the network answers to chain ID 570. Transaction data is published to Syscoin through PoDA, its data availability protocol, so the availability guarantee comes from the L1 beneath it rather than from an Ethereum blob. Syscoin is merge-mined by Bitcoin miners, which puts proof of work at the end of this chain’s settlement path. Syscoin also runs a UTXO ledger beside its EVM layer, so an asset’s full story can span three surfaces rather than two.
Rollux data on SonarX
SonarX indexes 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 Rollux on request. Kafka streaming can be enabled for Rollux on request.
How SonarX indexes Rollux
Everything about the L1 side of this chain is unusual. Batches and availability proofs go to Syscoin, so reconciling an L2 record against its settlement means reading a merge-mined chain rather than a staked one, and it means reading two ledgers there, because Syscoin keeps unspent outputs beside its EVM accounts. SYS crosses all three surfaces, so a balance question about the coin is not answered on Rollux alone. Two-second blocks put more rows per hour into a pipeline than the value moved would suggest, which is a streaming consideration rather than a storage one.
What teams build with Rollux data
Cross-layer asset accounting is the workload this chain creates. SYS pays for gas here, exists as unspent outputs on Syscoin and moves through Syscoin’s EVM layer, so stating what a holder owns means lining up three sets of records rather than reading one balance. Position-level DeFi analytics is the second job, built on decoded events and internal transfers. Bridge reconciliation is the third, matching deposits and withdrawals to the settlement records on the chain below. Fee research is the fourth and is cheap here, because two-second blocks and a coin-based fee market produce a long, dense cost series that says what activity actually cost. Teams looking at rollups whose gas is not ETH usually pull Metis in beside it.
Getting Rollux 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. Rollux history is available now, and the Syscoin records that settle it can be scoped alongside. 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 Rollux data API?
Real-time and batch APIs over indexed Rollux 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 Rollux 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 Rollux coverage go?
The historical data-share and file delivery cover the chain from its 2023 launch forward, and are available today. Depth on the Syscoin side is scoped separately, because the batches and availability proofs that settle this chain are recorded there rather than here, so tell us whether your reconciliation needs both.
Where does Rollux transaction data live?
On Syscoin, through its data availability protocol, rather than in Ethereum blobs. That is the practical difference from an Ethereum rollup: checking a Rollux record against the data that backs it means querying Syscoin, and a pipeline built to read Ethereum for the L1 side finds nothing there at all.
