Indexers

Why Use an Indexer?

RPC endpoints are optimized for real-time queries. For historical data, complex queries (token transfers, DEX trades, balances over time), or event aggregation, use a dedicated indexer.

Provider status

Option	Status	Best use
Bounded JSON-RPC log scans	Available now	Recent event reads and small backfills within provider caps
Self-hosted archive node plus custom indexer	Available now	Full historical data, replayable ETL, and integration-specific schemas
SubQuery project pattern	Available now as generic tooling	Build a multichain EVM/Cosmos indexer using c8ntinuum RPC surfaces
Official hosted SubQuery provider	TBA	Use once a provider, endpoint, and SLA are published
Official hosted indexer schemas	TBA	Use once managed schemas and freshness guarantees are published
The Graph hosted c8ntinuum provider	Not announced	Adapt generic EVM subgraph patterns only where infrastructure supports the target network

Types of Data

Data Type	Best Source
Real-time balances	RPC (`eth_getBalance`, `eth_call`)
Event logs	RPC (`eth_getLogs`) or indexer
Historical state	Indexer
Token transfers	Indexer
DEX trades	Indexer
NFT ownership	Indexer

Using Event Logs

c8ntinuum supports standard Ethereum event logs. Query recent ranges via RPC:

const logs = await provider.getLogs({
  address: contractAddress,
  topics: [ethers.id("Transfer(address,address,uint256)")],
  fromBlock: 1234000n,
  toBlock: "latest",
});

The documented EVM JSON-RPC profile caps each eth_getLogs request at 10000 blocks and 10000 returned logs. Paginate historical jobs and persist cursors; for large backfills, use an archive node or dedicated indexer. See Historical Data for archive and scan guidance.

SubQuery

c8ntinuum’s EVM and Cosmos surfaces fit SubQuery’s multichain indexing pattern. A c8ntinuum SubQuery project can use an Ethereum runtime data source for EVM logs and a Cosmos runtime data source for Cosmos SDK events, following the same project shape used in SubQuery’s EVM + Cosmos multichain quickstart. Official hosted SubQuery providers for c8ntinuum are TBA in this repository.

The Graph

c8ntinuum exposes Ethereum-compatible logs and JSON-RPC, so generic EVM subgraph patterns can be adapted for contracts deployed on c8ntinuum when the target indexing infrastructure supports the network. No official c8ntinuum-specific The Graph provider is announced in these docs.

Required fields for future provider docs

When a hosted indexer is published, document provider URL, supported networks, schema names, freshness targets, backfill depth, rate limits, authentication, pricing/SLA link, and failure behavior.

Introduction

Developer Essentials

Tooling and Infrastructure

Reference

Guides

Resources

Why Use an Indexer?

Provider status

Types of Data

Using Event Logs

SubQuery

The Graph

Required fields for future provider docs

​Why Use an Indexer?

​Provider status

​Types of Data

​Using Event Logs

​SubQuery

​The Graph

​Required fields for future provider docs

Why Use an Indexer?

Provider status

Types of Data

Using Event Logs

SubQuery

The Graph

Required fields for future provider docs