SonarX

Indexed BaseBlockchain Data

Base, the OP Stack rollup Coinbase runs on Ethereum, produces two-second blocks under a single sequencer and charges for both L2 execution and the L1 data each batch consumes.

Base logo

How to query Base data with SonarX

Instant Data Share

Available today

Snowflake, and file dumps to your object storage

Query Base 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

Used for:

  • Analytics teams already on Snowflake that want Base 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 Base 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

Available today

Event stream

Consume Base 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 Base activity within seconds
  • Fraud and anomaly detection that has to fire before settlement
  • Live dashboards and alerting on Base 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

Curated Datasets

Available today

Purpose-built tables

Protocol-level Base datasets modelled for one job, so the decoding and the joins are done before the data reaches you.

  • DeFi
  • Tokens and payments

Used for:

  • Position-level Base lending, swap and liquidity analysis
  • Reward, delegation and validator reporting without rebuilding the model
  • Token distribution, holder and payment-flow reporting
  • Risk and exposure work that needs protocol state, not raw logs
  • Skipping the decoding layer an in-house team would have to maintain
  • Extending an existing Base share with a modelled slice

Balances

Available today

Tables and REST

Read what a Base 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 Base 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 Base balances on page load
  • Compliance checks that read one Base 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

Available today

REST over the indexed dataset

Query indexed Base 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 Base data behind their own API layer

Base data: frequently asked questions

What is Base?

Base is an optimistic rollup that settles on Ethereum, built by Coinbase on the OP Stack and opened to the public on 9 August 2023. It has no token of its own, and gas is paid in ETH. Blocks are produced every two seconds by a single sequencer, and the canonical chain is derived from the batches that sequencer posts to Ethereum, so finality here is Ethereum’s finality arriving late rather than a property of Base’s own consensus. Execution is EVM-equivalent: the same bytecode, the same ABIs and the same twenty-byte addresses, plus two record types that only exist on a rollup. Deposit transactions are created by messages from Ethereum and carry no ordinary signature, and a system transaction at the head of every block writes the L1 attributes the chain needs. Fees are charged in two parts, one for execution and one for the Ethereum data a batch consumes. Since the Dencun upgrade of March 2024 that data has traveled as blobs rather than calldata.

Base data on SonarX

SonarX indexes Base end to end: blocks and headers, transactions and receipts, event logs decoded against contract ABIs, execution traces including internal value transfers, and token transfers and balances. Rollup-specific records are kept rather than flattened away, so deposits, withdrawal initiations and the two halves of a transaction’s cost are all present. The normalized model is the one SonarX uses across every network it covers, so Base joins to its settlement layer in a single query instead of across two pipelines.

Full historical coverage is available today as a data-share or a file delivery. Real-time delivery keeps the same dataset current to chain tip. Point-in-time balance tables, the real-time balances API and the batch wallets, tokens and balances API are all available for Base. Kafka streaming carries the same records as a live topic today.

How SonarX indexes Base

A rollup’s history is not self-contained, which is the whole difficulty. Base’s canonical chain is derived from data posted to Ethereum, so an L1 reorg can invalidate an unconfirmed head that already looked settled, and the indexer has to follow the derivation rather than trust the sequencer’s output. Deposits and withdrawals are half-recorded on each chain: a withdrawal proved and finalized on Ethereum weeks after it was initiated on Base is one economic event with two timestamps. Fee accounting needs both components or it reports the wrong number, and after Dencun the L1 half is priced against a blob market that moves independently of Base’s own activity.

What teams build with Base data

Base carries a large share of consumer-scale onchain activity, and the work reflects it. Wallet and retention analysis is the common one: cohorts of addresses followed across apps, which needs decoded logs and traces together rather than transfer counts. Payment and stablecoin flow analysis is second, tracing ERC-20 movement between exchanges, apps and bridges where a rollup’s low fees change user behavior rather than the accounting. Third is rollup economics, comparing what a chain charges users against what it pays Ethereum for data, a calculation only possible with both fee components in one place. All three need the deposit and withdrawal records intact, because a user’s first appearance on Base is usually a bridge transaction rather than a wallet creation, and a cohort that starts at the first swap misses where the money came from. DeFi analytics work spans Base and Optimism together, since the two share a codebase and a record structure.

Getting Base 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. Base history and the balance APIs are available now, so a first delivery is provisioning rather than engineering. 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 Base data API?

Yes. Real-time and batch APIs over indexed Base data are available today, covering historical and latest balances and wallet, token and balance lookups in bulk. They read from the same indexed dataset as the Snowflake share and the file delivery, so an API answer and a warehouse query agree.

How do I get Base 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 Base coverage go?

The historical data-share and file delivery cover Base from its first blocks in 2023 forward, and are available today. The chain is young but dense, because it produces a block every two seconds, so the backfill is larger than the launch date suggests. Real-time delivery keeps the same dataset current to chain tip.

Are Base deposits and withdrawals visible in the indexed data?

Yes, and both are two-sided. A deposit begins with a transaction on Ethereum and arrives on Base as a system-created transaction with no ordinary signature. A withdrawal is initiated on Base and finalizes on Ethereum only after the challenge period, so following the money means joining records on two chains rather than reading one transfer.

How are Base transaction fees represented?

As two components, because that is how they are charged. A Base transaction pays for its own execution and separately for the Ethereum data its batch consumes, and since the Dencun upgrade of March 2024 that second component is priced against blobs. Cost analysis that only reads the execution fee understates what a transaction actually cost.

Does Base have its own token?

No. Gas on Base is paid in ETH, and there is no native gas asset to account for separately. Token activity on the chain is ERC-20 and ERC-721 activity, which is why balance work here looks like contract-level accounting rather than native-asset accounting.

How do I start with Base data?

Tell SonarX the delivery target, the history depth and the refresh cadence you need, and the share is scoped against that. There is no self-serve signup: every engagement is provisioned, so the first conversation is about scope rather than credentials.

Base logo

Get Base data from SonarX