Indexed KintoBlockchain Data
Kinto is an Arbitrum Nitro rollup on Ethereum that disables externally owned accounts and reverts any sender without a verified identity, and its operators have published a closing plan.
How to query Kinto data with SonarX
Instant Data Share
Available todaySnowflake, and file dumps to your object storage
Query Kinto 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 Kinto 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 Kinto 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 Kinto 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 Kinto activity within seconds
- Fraud and anomaly detection that has to fire before settlement
- Live dashboards and alerting on Kinto 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 Kinto 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 Kinto 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 Kinto balances on page load
- Compliance checks that read one Kinto 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 Kinto 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 Kinto data behind their own API layer
Kinto data: frequently asked questions
What is Kinto?
Kinto is an optimistic rollup built with the Arbitrum Nitro stack, settling to Ethereum, and two of its rules have no equivalent on a general-purpose EVM chain. Externally owned accounts are disabled: a user transacts through a non-custodial smart contract wallet under EIP-4337, so a wallet contract rather than a key is the account of record. Transacting also requires a soulbound NFT called a Kinto ID, issued after verification, and that rule is enforced in execution rather than by an application, so a transaction from an unverified sender reverts. Gas is paid in ETH, so the chain has no native gas asset of its own, and it answers to chain ID 7887.
Its operators have since published a closing plan, after an exploit of the legacy K token proxy contract on Arbitrum took 577 ETH, with a final withdrawal deadline and a claims process for holders.
Kinto data on SonarX
SonarX indexes Kinto 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 Kinto on request. Kafka streaming can be enabled for Kinto on request.
How SonarX indexes Kinto
Nothing here looks like an ordinary EVM transaction trail. With externally owned accounts disabled, a user action arrives as an operation submitted through the entry point contract, so the sender field names infrastructure rather than whoever authorized the action. Attributing activity means decoding the wrapped call, resolving it to the smart contract wallet that signed for it, and reading the wallet factory’s deployment records to know which addresses are user accounts at all. Permissioning is the second seam: the identity contract can revoke a wallet’s ability to transact, so an address can hold a balance it cannot move, and that status changes over time.
What teams build with Kinto data
Account reconstruction is the first workload, and it is harder here than a transaction count suggests: activity has to be traced through bundled operations to the wallet contract that authorized it before a per-user view exists. SonarX’s wallet solutions cover that class of work across the networks it indexes. Exit and settlement accounting is the second job: withdrawals, bridge exits and final balances form a defined set of records to match against internal ledgers. Account-abstraction research is the third: on most chains wallet-contract traffic is a slice of the total and here it is the total, which makes this history a rare public record of how sponsored transactions behaved. Arbitrum is the usual reference beside it.
Getting Kinto 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 whether wallet-factory deployments should be resolved to account owners, since that 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 Kinto data API?
Real-time and batch APIs over indexed Kinto 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 Kinto 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 Kinto coverage go?
The historical data-share and file delivery cover Kinto's recorded history and are available today, with exact depth confirmed when the share is scoped rather than asserted here. Because the network's status has changed, most deliveries for this chain are a fixed window rather than a running feed, and real-time delivery remains provisioned on request.
Is Kinto still operating as a network?
Its operators published a closing plan after an exploit of the legacy K token proxy contract on Arbitrum took 577 ETH, setting a final withdrawal deadline and a claims process for holders, and stating that the network and user wallets themselves were not breached. Whether the chain is still producing blocks is worth confirming with us rather than reading off this page. Either way, the recorded history is what SonarX indexes and delivers.
Does Kinto have its own gas token?
No. Transactions here are paid for in ETH, which is why no native token is listed for this chain. K is a governance asset rather than the asset that pays for gas, and the contract that was exploited was its legacy proxy on Arbitrum. Fee analysis on this chain is therefore denominated in ETH, the same unit as the cost of settling its batches.
