Oasys Data: Index Game Assets, Verses, and Players

Index Oasys Hub Layer and Verse Layer contract events, NFT and token transfers, and decoded player actions in one pipeline, delivered to your own database. Real-time and full history, no node to run.

Oasys started as a blockchain for games and now calls itself the blockchain for Asia and beyond. It is an EVM-compatible network built so studios can ship Web3 titles without making players think about gas. Its defining trait is a two-layer design: a Hub Layer that acts as a scalable Layer 1 backbone for tokens, NFTs, and bridging, and Verse Layers, game-specific Layer 2 rollups where the actual play happens. Game developers run their own Verse and cover transaction costs, so players get a gasless, fast-play experience. OAS pays for gas, deposits, and staking rewards and carries governance, while the validator set is drawn from major game studios. You can read how the team frames it at oasys.games.

That multi-layer, game-first design is the data problem. Oasys spreads activity across the Hub Layer and a fan-out of Verse Layers, all of them EVM, where mints, trades, transfers, and player actions stream out across many chains at once. Indexing Co covers the Hub and any Verse in a single pipeline, decodes the raw chains 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 Hub + Verse blocks

Ingest blocks, logs, traces

Decode ABIs to events

Transform your JavaScript

Deliver your database

Why Oasys data is hard

Hub Layer and Verse Layers Oasys is not one chain but a Hub Layer plus a fan-out of Verse Layers, each a game-specific L2. A real dataset means following activity across several of these at once, correlating Hub-side tokens, NFTs, and bridge contracts with the per-game Verse where the play actually happens.

Game Economy Activity Each game on a Verse runs its own economy: token sinks and faucets, reward payouts, crafting and breeding, staking, and seasonal events. With gas covered by the studio, players transact freely, so reconstructing balances and flows across those loops in real time is its own engineering job.

NFT and Asset Data Game assets on Oasys mint, trade, and burn constantly, and some are designed to move across titles. Tracking ERC-721 and ERC-1155 ownership, marketplace listings and sales, and per-collection royalties means following transfer chains that span both the Hub Layer and individual Verses.

Decoding Across Many Contracts A real Oasys dataset spans the Hub Layer bridge and token contracts, OAS staking, and multiple game contracts on different Verses at once. Each needs its own ABI and event handling, and proxy upgrades make the right ABI a moving target as studios ship new seasons.

What Indexing Co delivers for Oasys

The DIY Path

Stand up and maintain the whole stack yourself.

Run a Hub Layer node and a node per Verse, or wire up third-party RPCs for each.
Fetch and decode logs, traces, and receipts against the right ABIs.
Track game contract upgrades and per-Verse event schemas by hand.
Build backfill, reorg handling, and real-time delivery from scratch.

Indexing Co

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

Hub Layer and Verse contract events, NFT and 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 Oasys, for example
Contract events and logs	OAS staking and delegation, Verse game contracts
Token transfers (ERC-20, ERC-721, ERC-1155)	Game asset mints, in-game item trades
Decoded transactions and traces	Player actions across Hub and Verse layers
Protocol and account state	Marketplace listings, validator stakes, game balances

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

Oasys with Indexing Co

Run it yourself if

You want full control of node infrastructure and have the team to operate a Hub Layer node and a node per Verse, decode every game and protocol ABI, and build backfill and reorg handling in-house.

Use Indexing Co if

You want Hub Layer and Verse contract events, NFT and token transfers, and decoded player actions 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 Oasys node?

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

Can I index both the Hub Layer and a Verse?

Yes. Both the Hub Layer and the Verse Layers are EVM, so we index them the same way. Point a pipeline at Hub-side token, NFT, and bridge contracts, at a specific game Verse, or at both, and we decode the events against the right ABI.

Can I track NFT and in-game asset activity on Oasys?

Yes. We follow ERC-721 and ERC-1155 transfers, marketplace listings and sales, and mints and burns, so you can reconstruct ownership and asset flows across an entire game economy and across Verses.

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

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

Get Started

Index Oasys in minutes. Set up your first Hub Layer, Verse, NFT, or token pipeline without running a node.