Indexed AbstractBlockchain Data
Abstract is a ZK Stack rollup on Ethereum built by the team behind Pudgy Penguins, where account abstraction is native and a person's assets sit in a contract authorized by a passkey.
How to query Abstract data with SonarX
Instant Data Share
Enabled on requestSnowflake, and file dumps to your object storage
Query Abstract 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
Used for:
- Analytics teams already on Snowflake that want Abstract 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 Abstract 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 Abstract 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 Abstract activity within seconds
- Fraud and anomaly detection that has to fire before settlement
- Live dashboards and alerting on Abstract 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 Abstract 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 Abstract 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 Abstract balances on page load
- Compliance checks that read one Abstract 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 Abstract 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 Abstract data behind their own API layer
Abstract data: frequently asked questions
What is Abstract?
Abstract is a ZK rollup on Ethereum, open to the public since January 2025 and built by Igloo Inc, the company behind the Pudgy Penguins collection. It is assembled from the ZK Stack, the framework that also produced zkSync Era, so batches execute off the L1 and a zero-knowledge proof of each batch is verified on Ethereum, which settles it. Gas is paid in ETH and no separate token pays for transactions. Account abstraction is native rather than bolted on: an account can carry its own validation logic, and the Abstract Global Wallet holds a person’s assets in a deployed contract authorized by a passkey. Solidity compiles to the stack’s own virtual machine, so a contract’s source moves over from Ethereum while its compiled artifact does not. The chain is aimed at consumer applications, and its traffic reflects that.
Abstract 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. Account fields are kept rather than collapsed into a sender column, in the normalized model SonarX uses on every chain it covers.
Full historical coverage is provisioned for Abstract on request. Balance tables and the balance APIs can be enabled for Abstract on request. Kafka streaming can be enabled for Abstract on request.
How SonarX indexes Abstract
Two properties decide how this chain has to be indexed. Most users arrive through a contract account deployed for them, so the signer of a transaction, the account holding the assets and the address that paid the fee can be three different values, and a query that counts senders does not count people. The second is compilation: contracts built for the stack’s virtual machine carry different artifacts from their Ethereum equivalents and derive addresses by a different rule, so a contract map lifted from an L1 pipeline mislabels rows rather than failing.
What teams build with Abstract data
Consumer traffic asks a different question set from a DeFi chain. Account resolution comes first: an application wants to know how many people used it, which here means grouping contract accounts and the keys that operate them rather than counting addresses. Collectible and token accounting is the second workload, restating mints, transfers and marketplace settlements per item. Sponsored-fee reporting is the third, since a team that pays its users’ gas needs the total one contract spent over a campaign rather than any user’s balance. Wallet analytics underpins all three, and teams benchmarking consumer chains usually pull Immutable zkEVM alongside this one.
Getting Abstract 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. Abstract 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 Abstract data API?
Real-time and batch APIs over indexed Abstract 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 Abstract 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 Abstract coverage go?
The historical data-share and file delivery cover the chain's recorded history from its January 2025 public mainnet forward, and are provisioned on request. The testnet that ran before it is a separate network with its own addresses and its own history, so a model that starts earlier than mainnet is reading a different chain rather than an earlier Abstract.
Does the Abstract Global Wallet change how users are counted?
Yes. It is a contract account deployed per person and authorized by a passkey, so assets can sit at an address that never signs a transaction itself. Counting distinct senders therefore counts sessions and relaying accounts alongside people. Indexed data keeps the signer, the acting account and the fee payer as separate fields, so the grouping is a decision you make in SQL rather than one the pipeline makes for you.
