Mantle Data: Index mETH, Aave, and Onchain Finance

Index Mantle's contract events, mETH staking flows, and decoded transactions in one pipeline, delivered to your own database. Real-time and full history, no node to run.

Mantle bills itself as institutional onchain finance, an Ethereum Layer 2 rollup backed by a large community treasury. It pairs sub-cent fees with a finance-first roadmap: the mETH liquid staking protocol, FBTC as wrapped Bitcoin and Aave V3 lending live since February 2026. MNT pays for gas and steers governance. You can read how the team frames it at mantle.xyz.

That history is also where the data gets awkward. Mantle moved its data from EigenDA to Ethereum blobs in April 2026, has run ZK validity proofs since its September 2025 move to OP Succinct, and concentrates value in a handful of treasury-backed finance protocols. Indexing Co covers Mantle 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 Mantle L2 blocks

Ingest blocks, logs, traces

Decode ABIs to events

Transform your JavaScript

Deliver your database

Why Mantle data is hard

A Separate Data Availability Layer Mantle posted its data to EigenDA from March 2025 until the Arsia upgrade in April 2026, when it moved data availability to Ethereum blobs. A backfill that reconstructs or verifies batches has to know which data layer was in use at each block.

mETH and Restaking Flows mETH is a core asset here. Stakes, unstakes, the cMETH liquid restaking wrapper, and reward accrual move across the mETH protocol contracts. Tracking who holds what, and how yield accrues, means decoding several interlocking contracts rather than one transfer log.

Decoding Treasury-Backed Finance A real Mantle dataset spans Aave V3 markets, FBTC mints and redemptions, MNT governance and gas, and the protocols the treasury seeds. Each carries its own ABI, and proxies make the right ABI a moving target as contracts upgrade. Generic event parsing flattens distinctions that matter for finance data.

A History That Changed Stacks Mantle launched as an optimistic rollup, moved to ZK validity proofs with OP Succinct in September 2025, and moved its data to Ethereum blobs in April 2026. A complete dataset has to span both eras and stay correct across the migration. You want backfilled history that reflects how the chain actually settled at each block, not a snapshot of today's configuration.

What Indexing Co delivers for Mantle

The DIY Path

Stand up and maintain the whole stack yourself.

Run a Mantle archive node or wire up a third-party RPC.
Decode mETH, Aave, FBTC, and MNT events against the right ABIs.
Account for the EigenDA-to-Ethereum data move and the optimistic-to-ZK migration.
Build backfill, reorg handling, and real-time delivery from scratch.

Indexing Co

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

Mantle 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 Mantle, for example
Contract events and logs	Aave V3 borrows, mETH stake and unstake events
Token transfers (ERC-20, ERC-721)	MNT gas payments, FBTC mints and redemptions
Decoded transactions and traces	cMETH restaking calls, smart-account user operations
Protocol and account state	mETH balances, Aave positions, treasury holdings

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

Mantle with Indexing Co

Run it yourself if

You want full control of node infrastructure and have the team to operate a Mantle archive node, decode the mETH and Aave contracts yourself, and build backfill and reorg handling in-house.

Use Indexing Co if

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

No. Indexing Co sources Mantle 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 the mETH protocol on Mantle?

Yes. Point a pipeline at the mETH and cMETH contracts and we decode stake, unstake, and restaking events against the right ABIs, so you can track balances and yield accrual in your own store.

Does Indexing Co handle Mantle's stack migrations?

Yes. We index Mantle's execution layer directly and backfill history that spans both the optimistic and ZK eras, so your dataset stays correct across the chain's upgrades.

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

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

Get Started

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