Chiliz Data: Index Fan Tokens and Sports Apps

Index Chiliz Chain's Fan Token transfers, contract events, and decoded transactions in one pipeline, delivered to your own database. Real-time and full history, no node to run.


Chiliz Chain calls itself the blockchain built for sports and entertainment, an EVM-compatible Layer 1 where clubs, leagues, and their fans meet onchain. It is the home of Fan Tokens, the official club assets distributed through Socios.com that let supporters vote in polls, unlock rewards, and hold a stake in teams like Paris Saint-Germain, Manchester City, FC Barcelona, Juventus, and Arsenal. CHZ pays for gas, a Proof of Staked Authority validator set finalizes blocks, and more than seventy official Fan Tokens now trade across the ecosystem. You can read how the team frames it at chiliz.com.

That fan-first design is the data problem. Chiliz is an EVM chain where Fan Token transfers, poll votes, staking rewards, and marketplace trades stream out every time a club runs a campaign or a match kicks off. Indexing Co covers Chiliz 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 Chiliz L1 blocks
Ingest blocks, logs, traces
Decode ABIs to events
Transform your JavaScript
Deliver your database

Why Chiliz data is hard

Fan Token Lifecycle Every Fan Token is its own ERC-20 with its own supporters, and a single club runs polls, rewards drops, and staking campaigns that mint, distribute, and lock balances in bursts around match days. Reconstructing holder rosters and engagement per club across seventy-plus tokens is a data job in its own right.
Sports and Entertainment Cadence Activity on Chiliz is event-driven: a signing, a final, or a limited campaign can spike transfers and votes for a few hours and then go quiet. Capturing those spikes in real time without falling behind the chain head, then correlating them back to specific clubs and events, is a standing engineering problem.
Decoding Across Many Contracts A real Chiliz dataset spans dozens of contracts at once: individual Fan Tokens, Socios reward and voting logic, KayenFi swaps, staking and validator contracts, and club NFT drops. Each needs its own ABI and event handling, and proxies make the right ABI a moving target.
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 a fan app, club dashboard, or analytics workload on Chiliz means owning the data in your own store, shaped the way your product queries it.

What Indexing Co delivers for Chiliz

The DIY Path

Stand up and maintain the whole stack yourself.

  • Run a Chiliz 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-token event schemas by hand.
  • Build backfill, reorg handling, and real-time delivery from scratch.
Indexing Co

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

  • Chiliz Fan Token transfers, contract events, 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 Chiliz, for example
Contract events and logs Socios poll votes, KayenFi swaps, staking rewards
Token transfers (ERC-20, ERC-721) PSG and Barcelona Fan Token transfers, club NFT drops
Decoded transactions and traces Fan Token purchases, reward claims, validator staking
Protocol and account state Per-club holder rosters, staked CHZ, Fan Token supply

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;
}

Chiliz with Indexing Co

Run it yourself if

You want full control of node infrastructure and have the team to operate a Chiliz archive node, decode every Fan Token and Socios contract's ABIs, and build backfill and reorg handling in-house.

Use Indexing Co if

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

Get a DemoOpen the Console

Related Reading

FAQ

Do I need to run a Chiliz node?

No. Indexing Co sources Chiliz 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 Fan Token or app on Chiliz?

Yes. Point a pipeline at any Chiliz contract or set of contracts, from individual Fan Tokens and Socios voting logic to KayenFi or your own deployments, and we decode the events against the right ABI.

Does Indexing Co handle Chiliz reorgs and proxy upgrades?

Yes. The pipeline accounts for chain reorganizations and tracks proxy implementation changes so your decoded data stays correct as contracts upgrade.

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

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

Get Started

Index Chiliz in minutes. Set up your first Fan Token or sports-app pipeline without running a node.

Get a DemoOpen the Console