Filecoin Data: Index FEVM Contracts and the Storage Economy

Index Filecoin's FEVM 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.

Filecoin calls itself the world's largest decentralized storage network, a peer-to-peer system that turns idle disk into a global, cryptographically verified storage market and acts as the incentive layer on top of IPFS. Storage providers seal client data, prove they still hold it over time, and earn FIL for doing so, while clients pay to keep petabytes of cultural archives and scientific datasets live. On top of that base sits the Filecoin Virtual Machine and its EVM runtime, the FEVM, which brought programmable smart contracts to the network. You can read how the team frames it at filecoin.io.

For an indexer, the FEVM is the entry point. It executes EVM bytecode, so Solidity contracts, 0x and f410f addresses, ABIs, logs, and traces all behave the way you expect, which means FEVM data is fully claimable through a standard EVM pipeline. FIL is the gas token, and what makes Filecoin distinct is what those contracts touch: built-in actors for the storage market, storage-provider deals, and the verified-data program behind DataCap. Indexing Co covers Filecoin 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 Filecoin FEVM blocks

Ingest blocks, logs, traces

Decode ABIs to events

Transform your JavaScript

Deliver your database

Why Filecoin data is hard

Two Layers in One Chain Filecoin is a storage network and a smart-contract platform at the same time. The interesting datasets live at the seam: an FEVM contract that pays a storage provider, a DataCap allocation that unlocks verified deals, a liquid-staking vault built on top of sealing rewards. Capturing that means decoding EVM events and the storage economy they reference, not one or the other.

FEVM and Built-In Actors The FEVM runs EVM bytecode but sits over Filecoin's native actors, the storage market, miner, and verified-registry actors that govern deals and DataCap. Contracts reach them through precompiles, and addresses come in f0, f410f, and 0x forms that a naive EVM scraper will not reconcile. You want history that maps every form back to one identity.

Decoding Across Many Contracts A real Filecoin dataset spans the FEVM ecosystem at once: liquid-staking protocols, storage-provider marketplaces, perpetual-storage payment rails, and DeFi built on FIL. Each needs its own ABI and event handling, and proxy patterns 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 an app or analytics workload on Filecoin means owning the data in your own store, shaped the way your product queries deals, providers, and contract events.

What Indexing Co delivers for Filecoin

The DIY Path

Stand up and maintain the whole stack yourself.

Run a Filecoin (Lotus) node or wire up a third-party FEVM RPC.
Fetch and decode logs, traces, and receipts against the right ABIs.
Reconcile f0, f410f, and 0x addresses and track proxy upgrades by hand.
Build backfill, reorg handling, and real-time delivery from scratch.

Indexing Co

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

Filecoin FEVM 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 Filecoin, for example
Contract events and logs	Liquid-staking mints, storage-provider marketplace deals
Token transfers (ERC-20, ERC-721)	FIL-denominated payments, wrapped FIL and stablecoin flows
Decoded transactions and traces	FEVM calls into the storage market and miner actors
Protocol and account state	Staking vault balances, DataCap allocations, deal payment 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;
}

Filecoin with Indexing Co

Run it yourself if

You want full control of node infrastructure and have the team to operate a Filecoin node, decode every FEVM protocol's ABIs, reconcile address types, and build backfill and reorg handling in-house.

Use Indexing Co if

You want Filecoin FEVM 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 Filecoin node?

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

Can I index any FEVM contract on Filecoin?

Yes. Point a pipeline at any Filecoin FEVM contract or set of contracts, from liquid-staking and storage-provider marketplaces to your own deployments, and we decode the events against the right ABI.

Does Indexing Co handle Filecoin's address types?

Yes. The pipeline works with FEVM's 0x-style addresses and can reconcile them with the f0 and f410f forms, so decoded data maps back to a single contract identity as it appears across the chain.

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

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

Get Started

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