Fraxtal Data: Index Stablecoins, LSTs, and DeFi State

Index Fraxtal's contract events, frxUSD stablecoin flows, FRAX gas-token transfers, frxETH and sfrxETH LST activity, and decoded transactions in one pipeline, delivered to your own database. Real-time and full history, no node to run.

Fraxtal is the Frax ecosystem's home chain, a modular OP Stack chain that settles to Ethereum (Frax now markets it as an EVM Layer 1), positioned as digital-dollar infrastructure rather than a general-purpose chain. It is where the frxUSD stablecoin and the Legacy Frax Dollar circulate and where frxETH and sfrxETH liquid staking accrues. Since the North Star hardfork in April 2025, FRAX (formerly FXS) is the native gas token, and the chain leans hard into stablecoins, real-world-asset yield, and DeFi. The team frames the full picture at frax.com.

That tight integration is exactly what makes the data dense. Stablecoin mints and redemptions, savings-vault deposits, LST staking, AMO controller moves, and protocol-level state all land on the same EVM chain, and the modular data availability design means the raw bytes do not always sit where a naive scraper expects them. Indexing Co covers Fraxtal 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 Fraxtal L2 blocks

Ingest blocks, logs, traces

Decode ABIs to events

Transform your JavaScript

Deliver your database

Why Fraxtal data is hard

Stablecoin and LST Flows frxUSD mints and redemptions, FraxNet savings-vault deposits, and frxETH to sfrxETH staking all emit their own events, and yield routed through AMO controllers ties them together. Reconstructing who holds what, when yield accrued, and how supply moved means decoding every leg of that flow, not just transfers.

DeFi Protocol State Fraxtal is a DeFi-dense chain where lending markets, AMM pools, and savings vaults change state block by block. Capturing positions, rates, and balances over time means tracking storage and per-protocol events, not just the latest snapshot a node can return.

OP Stack and Modular DA Fraxtal is an OP Stack chain with a custom modular data availability module, so deposit and withdrawal lifecycles, sequencer ordering, and the L2 settlement path all add structure. With attestations not always posted on chain, you want history that reflects how the chain actually settles, not a best-effort guess.

EVM Decoding at the Source A real Fraxtal dataset spans many contracts at once: stablecoin issuers, LST minters, AMO controllers, and the DeFi protocols built on them. Each needs its own ABI, and proxy upgrades make the right ABI a moving target. Generic RPC and hosted APIs leave you rate-limited and renting someone else's schema.

What Indexing Co delivers for Fraxtal

The DIY Path

Stand up and maintain the whole stack yourself.

Run a Fraxtal archive node or wire up a third-party RPC.
Fetch and decode logs, traces, and receipts against the right ABIs.
Track stablecoin, LST, and proxy event schemas by hand.
Build backfill, reorg handling, and real-time delivery from scratch.

Indexing Co

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

Fraxtal contract events, stablecoin and LST flows, 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 Fraxtal, for example
Contract events and logs	frxUSD mints and redemptions, savings-vault deposits
Token transfers (ERC-20, ERC-721)	FRAX gas-token transfers, frxETH and sfrxETH staking
Decoded transactions and traces	AMO controller calls, DeFi protocol interactions
Protocol and account state	Lending positions, vault balances, LST exchange rates

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

Fraxtal with Indexing Co

Run it yourself if

You want full control of node infrastructure and have the team to operate a Fraxtal archive node, decode every stablecoin, LST, and DeFi protocol ABI, and build backfill and reorg handling in-house.

Use Indexing Co if

You want Fraxtal contract events, stablecoin and LST flows, 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 Fraxtal node?

No. Indexing Co sources Fraxtal 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 frxUSD, FRAX, and LST flows?

Yes. Point a pipeline at the stablecoin issuers, savings vaults, and frxETH or sfrxETH contracts you care about, and we decode mints, redemptions, staking, and yield events against the right ABI.

Does Indexing Co handle Fraxtal's OP Stack and modular DA?

Yes. The pipeline accounts for the OP Stack chain lifecycle and Fraxtal's modular data availability so your decoded history reflects how the chain actually settles, plus reorgs and proxy upgrades.

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

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

Get Started

Index Fraxtal in minutes. Set up your first stablecoin, LST, or DeFi contract pipeline without running a node.