DATA Network (formerly Story): Index Data Provenance, Licensing, and Royalty Flows Onchain

Index DATA Network's asset registrations, licensing events, and royalty flows in one pipeline, decoded and delivered to your own database. Real-time and complete history, no node to run.

DATA Network, formerly Story Protocol, is a purpose-built Layer 1 that pairs a 100% EVM-compatible execution layer with a Cosmos SDK and CometBFT base. In June 2026 the Story Foundation became The DATA Foundation, Story Network became DATA Network, and the $IP token became $DATA. The chain now positions itself as a trust layer for AI training data: assets are registered onchain with their provenance and machine-readable licenses, and attribution and royalties flow across derivative graphs. The protocol contracts carried over from Story, so existing integrations keep working. The team frames the vision at datafdn.org.

That graph-shaped design is what makes the data interesting and hard. Every IP registration, license mint, royalty payment, and dispute is an EVM event tied into a web of parent and derivative assets. Indexing Co covers DATA Network in a single pipeline, decodes those events into the shape you want, and delivers them to your own PostgreSQL, warehouse, or webhook. Real-time and full history, with no node to operate.

Source DATA Network L1 blocks

Ingest blocks, logs, traces

Decode ABIs to events

Transform your JavaScript

Deliver your database

Why DATA Network data is hard

IP Asset Registration and Licensing Each work registered through the IP Asset Registry mints an ERC-721 NFT and deploys its own IP Account contract, then licensing modules attach Programmable IP License terms on top. Reconstructing who registered what, under which license, and when means decoding registration, license-mint, and license-token events across a fleet of per-asset contracts.

Royalty and Dispute Flows The Royalty and Dispute modules settle revenue and infringement claims onchain. Following the money means tracking royalty deposits, claims, and distribution events as value moves along the derivative chain, plus dispute raises and resolutions that can change which assets are payable. Naive log scraping loses that economic state.

The Programmable-IP Graph Proof-of-Creativity links parent IP Assets to their derivatives in a recursive graph. The data only makes sense when you can walk those edges: a single remix can inherit licenses and royalties from several ancestors. Capturing the relationships, not just isolated events, is the whole point and the hard part.

EVM Decoding on a Custom L1 DATA Network's execution is a custom Geth fork riding on a Cosmos SDK and CometBFT base. It is 100% EVM-compatible, so standard ABIs decode, but you still want history that reflects this L1's own block production and finality rather than a generic chain assumption. Getting both the EVM events and the chain semantics right takes real work.

What Indexing Co delivers for DATA Network

The DIY Path

Stand up and maintain the whole stack yourself.

Run a DATA Network archive node or wire up a third-party RPC.
Fetch and decode logs, traces, and receipts against the right ABIs.
Track IP Account deployments and per-module event schemas by hand.
Build backfill, reorg handling, and real-time delivery from scratch.

Indexing Co

One pipeline sources, decodes, and delivers DATA Network to your store.

IP Asset events, license mints, and royalty flows 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 DATA Network, for example
Contract events and logs	IP Asset registrations, license mints, dispute raises
Token transfers (ERC-20, ERC-721)	IP Asset NFTs, license tokens, $DATA (formerly $IP) movements
Decoded transactions and traces	IP Account calls, royalty deposits and claims
Protocol and account state	License terms per asset, royalty balances, derivative links

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

DATA Network with Indexing Co

Run it yourself if

You want full control of node infrastructure and have the team to operate a DATA Network archive node, decode every module's ABIs, and build backfill and reorg handling in-house.

Use Indexing Co if

You want DATA Network IP Asset events, licensing, and royalty flows 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 DATA Network node?

No. Indexing Co sources DATA Network 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 protocol on DATA Network?

Yes. Point a pipeline at any DATA Network contract or set of contracts, from the IP Asset Registry and licensing modules to royalty and dispute contracts or your own deployments, and we decode the events against the right ABI.

How does indexing the IP graph work?

The protocol registers each IP Asset as an ERC-721 with its own IP Account contract and links parents to derivatives. We decode the registration, licensing, and royalty events so you can rebuild that graph and walk the relationships in your own store.

Where does the DATA Network data go?

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

Is DATA Network the same chain as Story?

Yes. DATA Network is the former Story Protocol chain under its new name, and $DATA is the former $IP token, converted 1:1. Story-era blocks are part of the same chain history, so one pipeline covers both.

Can I get complete historical DATA Network data?

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

Get Started

Index DATA Network in minutes. Set up your first DATA Network IP Asset or licensing pipeline without running a node.