Quai Data: Index EVM Contracts Across Quai Chains

Index Quai Network's contract events, token transfers, and decoded transactions in one pipeline, delivered to your own database. Real-time and complete historical data, no node to run.

Quai Network is a scalable Proof-of-Work protocol built as a hierarchical set of interoperable, EVM-compatible chains rather than a single ledger. A Prime chain sits at the top as the knot that braids everything together, Region chains sit beneath it, and Zone chains do the high-throughput work of processing transactions independently and asynchronously. Those chains are merged-mined together, so hash power is shared across the braid and settlement rolls up through the hierarchy. The network has two native tokens: QUAI, and Qi, which the docs describe as a decentralized dollar tied to the cost of energy. You can read how the team frames the design at qu.ai.

That sharded structure is exactly what makes Quai data awkward. The execution surface is standard EVM, so contract events, token transfers, and decoded calls look familiar, and today all of it runs on a single active Zone chain, Cyprus-1, with more zones designed to come online as demand grows. Indexing Co covers Quai in a single pipeline, decodes the raw chain into the shape you want, and delivers it to your own PostgreSQL, warehouse, or webhook. Real-time and full history, with no node to operate.

Source Quai Zone blocks

Ingest blocks, logs, traces

Decode ABIs to events

Transform your JavaScript

Deliver your database

Why Quai data is hard

A Braid, Not One Chain Quai is designed as a hierarchy of Prime, Region, and Zone chains, with application activity landing on Zone chains. Today only the Cyprus-1 zone is live, but as more zones activate, a dataset that reflects the whole network has to follow each shard rather than tail a single block feed.

Merged Mining and Shared Security Blocks are merged-mined and settlement braids upward through the hierarchy, with the Prime chain linking the subnetworks together. Reconstructing when data is confirmed across the braid adds structure that a naive per-chain scraper misses.

Standard EVM Decoding The good news is that once you are on a Quai chain, the data is ordinary EVM: logs, receipts, and traces decoded against contract ABIs. The catch is that each protocol needs the right ABI, and proxy upgrades make that a moving target across every deployment you track.

Your Own DB, Not a Hosted API Generic RPC endpoints and hosted query APIs leave you rate-limited and renting someone else's schema. Powering an app or analytics workload on Quai means owning the data in your own store, shaped the way your product queries it.

What Indexing Co delivers for Quai

The DIY Path

Stand up and maintain the whole stack yourself.

Run a Quai node or wire up a third-party RPC for the Cyprus-1 zone.
Fetch and decode logs, traces, and receipts against the right ABIs.
Track proxy upgrades and per-protocol event schemas by hand.
Build backfill, reorg handling, and real-time delivery from scratch.

Indexing Co

One pipeline sources, decodes, and delivers Quai to your store.

Quai contract events, token transfers, and decoded txs in a single pipeline.
Decoded data, shaped by your JavaScript transform.
Lands in your PostgreSQL, BigQuery, warehouse, or webhook.
Real-time delivery plus complete backfilled history. No node, no RPC babysitting.

What you can index

EVM data type	On Quai, for example
Contract events and logs	DEX swaps, bridge transfers, launchpad events
Token transfers (ERC-20, ERC-721)	QUAI-denominated payments, NFT mints
Decoded transactions and traces	Smart-contract calls on the Cyprus-1 zone
Protocol and account state	Pool reserves, vault balances, account positions

A transform, not a subgraph

You write the transform in JavaScript, not AssemblyScript, and change it without re-indexing from block zero. Indexing Co runs your function over each block server-side: decode the logs you care about and return rows for your destination.

// Indexing Co transform: reshape each block into rows for your database
function transform(block) {
  const results = [];
  const signatures = [
    'event Transfer(address indexed from, address indexed to, uint256 value)'
  ];

  for (const tx of block.transactions || []) {
    for (const log of tx.receipt?.logs || []) {
      const event = utils.evmDecodeLogWithMetadata(log, signatures);
      if (!event) continue;
      results.push({
        chain: block._network,
        block: Number(block.number),
        tx_hash: tx.hash,
        contract_address: log.address?.toLowerCase(),
        from: event.decoded.from,
        to: event.decoded.to,
        value: event.decoded.value,
      });
    }
  }
  return results;
}

Quai with Indexing Co

Run it yourself if

You want full control of node infrastructure and have the team to operate a Quai node for the Cyprus-1 zone, decode every protocol's ABIs, and build backfill and reorg handling in-house.

Use Indexing Co if

You want Quai contract events, token transfers, and decoded transactions delivered to your own database, with real-time plus complete history and no infrastructure to run.

Get a Demo Open the Console

FAQ

Do I need to run a Quai node?

No. Indexing Co sources Quai blocks, logs, and traces for you, including full historical data, so you never operate a node or babysit an RPC endpoint.

Which Quai zones can I index?

Cyprus-1, which is the only active zone on Quai mainnet today. Point a pipeline at the contracts you care about there, and we decode the events against the right ABI.

Is indexing Quai different from any other EVM chain?

At the data layer, no. Quai's execution is EVM-standard, so logs, receipts, and traces decode the same way. The hierarchy shows up in where blocks are produced, and the pipeline handles that for you.

Where does the Quai data go?

Into your own destination: PostgreSQL, BigQuery, a warehouse, or a webhook. You define the output schema and own the storage.

Can I get complete historical Quai data?

Yes. We backfill from your chosen start block and merge it with real-time data, so your Quai dataset is gap-free from the chain's genesis forward if you want it.

Get Started

Index Quai in minutes. Set up your first Quai contract or token pipeline without running a node.