Orderly Data: Index Orderbook, Perps, and Settlement

Index Orderly's omnichain orderbook, perp fills, and onchain settlement in one pipeline, decoded and delivered to your own database. Real-time and complete historical data, no node to run.

Orderly is omnichain orderbook and liquidity infrastructure: one shared orderbook that any builder can plug into for CEX-grade perpetual futures depth, live across Ethereum, Arbitrum, Base, Solana, and a growing list of chains. Matching runs off-chain, and settlement lands on Orderly Chain, an OP Stack chain that records the trades, fills, and ledger movements behind every connected venue. You can read how the team frames it at orderly.network.

That shared-liquidity design is the data problem. A single Orderly integration powers many front-ends at once, so the settlement layer carries perp fills, funding, liquidations, deposits, and withdrawals from every builder in one place. Indexing Co covers Orderly's EVM settlement data in a single pipeline, decodes it 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 Orderly settlement

Ingest blocks, logs, traces

Decode ABIs to events

Transform your JavaScript

Deliver your database

Why Orderly data is hard

One Orderbook, Many Builders Orderly's shared orderbook powers perp venues across Ethereum, Arbitrum, Base, Solana, and more from a single liquidity layer. The settlement data mixes fills from every connected builder, so attributing activity back to a specific venue or broker means decoding the right fields, not just scraping raw logs.

Off-Chain Match, Onchain Settle Matching happens on Orderly's engine while trades, ledger balances, and account movements settle on Orderly Chain. Reconstructing a true picture of positions and PnL means following the onchain settlement events as the source of record, not just the orderbook stream.

OP Stack L2 Specifics Orderly Chain is an OP Stack Optimium: it batches transactions, posts its data to Celestia, and commits state to Ethereum L1. Sequencer ordering, deposit and withdrawal lifecycles, and L1-to-L2 messaging all add structure that a naive EVM scraper misses. You want history that reflects how settlement actually finalizes.

Your Own DB, Not a Hosted API Building a trading dashboard, broker analytics, or risk engine on Orderly means owning fills, funding, and liquidations in your own store, shaped the way your product queries. Generic RPC endpoints and hosted query APIs leave you rate-limited and renting someone else's schema.

What Indexing Co delivers for Orderly

The DIY Path

Stand up and maintain the whole stack yourself.

Run an Orderly Chain archive node or wire up a third-party RPC.
Fetch and decode settlement logs, traces, and receipts against the right ABIs.
Map fills, funding, and liquidations back to brokers and accounts by hand.
Build backfill, reorg handling, and real-time delivery from scratch.

Indexing Co

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

Orderly settlement 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 Orderly, for example
Contract events and logs	Perp fills, funding payments, liquidations
Token transfers (ERC-20, ERC-721)	USDC deposits and withdrawals, collateral movements
Decoded transactions and traces	Broker settlement and account ledger movements
Protocol and account state	Open positions, collateral balances, staking

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

Orderly with Indexing Co

Run it yourself if

You want full control of node infrastructure and have the team to operate an Orderly Chain archive node, decode the settlement ABIs, and build backfill and reorg handling in-house.

Use Indexing Co if

You want Orderly fills, funding, liquidations, and settlement movements 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 Orderly node?

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

Can Indexing Co index perp fills and liquidations from Orderly?

Yes. The settlement events behind perp trading, funding, and liquidations are decoded against the right ABI and delivered to your destination, ready to reconstruct positions and PnL.

Does Indexing Co handle Orderly Chain reorgs and proxy upgrades?

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

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

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

Get Started

Index Orderly in minutes. Set up your first Orderly settlement or token pipeline without running a node.