Ethereum Classic Data: Index ETC Contracts and Transactions

Index Ethereum Classic'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.

Ethereum Classic is the original Ethereum chain, the fork that kept running proof-of-work and an unaltered ledger after the 2016 DAO split, when most of the community moved to the chain that reversed the hack. Its guiding principle is "code is law": transactions stand as recorded, immutability is a feature, and the network still settles under an Ethash-based proof-of-work consensus with ETC as its gas token. Because it never abandoned the EVM, the same contracts, ABIs, and opcodes you know from Ethereum run here, on a chain with one of the longest continuous histories in the space. You can read how the community frames it at ethereumclassic.org.

That long, immutable history is the data problem. Ethereum Classic has years of blocks, contract events, and token transfers on a proof-of-work chain that keeps producing new state, and pulling clean data across that span means running an archive node and decoding the same EVM structures Ethereum uses. Indexing Co covers Ethereum Classic 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 Ethereum Classic blocks

Ingest blocks, logs, traces

Decode ABIs to events

Transform your JavaScript

Deliver your database

Why Ethereum Classic data is hard

Proof-of-Work History Depth Ethereum Classic has one of the longest unbroken histories in crypto, a proof-of-work chain that has been minting blocks continuously since 2015 and never migrated to proof-of-stake. Walking that full span from genesis forward, block by block, is a heavy archive-node job that most teams would rather not run.

Immutability Means No Rewrites The "code is law" ethos means the ledger is not rewound, so your dataset has to reflect exactly what happened, including the contracts and events that lived through the 2016 DAO-fork split. Getting that history right is the whole point on a chain that treats its record as final.

EVM Decoding Without Ethereum's Tooling Ethereum Classic runs the same EVM, ABIs, and opcodes as Ethereum, but it does not get the same depth of hosted indexers and query APIs. You end up decoding standard Solidity events and proxy patterns yourself against far thinner off-the-shelf support.

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

What Indexing Co delivers for Ethereum Classic

The DIY Path

Stand up and maintain the whole stack yourself.

Run an Ethereum Classic archive node or wire up a third-party RPC.
Fetch and decode logs, traces, and receipts against the right ABIs.
Track proxy upgrades and per-contract event schemas by hand.
Build backfill, reorg handling, and real-time delivery from scratch.

Indexing Co

One pipeline sources, decodes, and delivers Ethereum Classic to your store.

Ethereum Classic 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 Ethereum Classic, for example
Contract events and logs	DEX swaps and pool mints, liquidity adds and removes
Token transfers (ERC-20, ERC-721)	Stablecoin and wrapped-asset transfers, NFT mints
Decoded transactions and traces	Router calls, multisig and treasury actions
Protocol and account state	ETC balances, pool reserves, contract 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;
}

Ethereum Classic with Indexing Co

Run it yourself if

You want full control of node infrastructure and have the team to operate an Ethereum Classic archive node, decode every contract's ABIs, and build backfill and reorg handling in-house.

Use Indexing Co if

You want Ethereum Classic 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 an Ethereum Classic node?

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

Can I index any contract on Ethereum Classic?

Yes. Point a pipeline at any Ethereum Classic contract or set of contracts, from DEXes to token deployments or your own contracts, and we decode the events against the right ABI.

Is Ethereum Classic really EVM-compatible?

Yes. Ethereum Classic runs the same EVM as Ethereum, so the same Solidity contracts, ABIs, and event signatures decode exactly as they do on Ethereum, on a proof-of-work chain with ETC as the gas token.

Where does the Ethereum Classic 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 Ethereum Classic data?

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

Get Started

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