Plume Data: Index Tokenized RWAs, Compliance Events, and Yield Flows

Index Plume's RWA token events, compliance and onboarding events, and yield distribution flows in one pipeline, delivered to your own database. Real-time and complete historical data, no node to run.

Plume calls itself open finance for institutional assets, a modular EVM network purpose-built for real-world assets that wires tokenization and compliance providers directly into the chain. Built on the Arbitrum Nitro stack with a data availability committee, it stays fully EVM-compatible while adding native onboarding, transfer-agent registration, and issuer-grade controls so funds, private credit, and other tokenized assets can behave like crypto-native primitives. You can read how the team frames it at plume.org.

That mandate is the data problem. A single Plume position can touch a tokenized fund, a Nest yield vault, a compliance gate, and a lending market in one transaction, and every step emits events you need to reconstruct who holds what and why. Indexing Co covers Plume 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 Plume RWA blocks

Ingest blocks, logs, traces

Decode ABIs to events

Transform your JavaScript

Deliver your database

Why Plume data is hard

RWA Tokens and Compliance Events Together A tokenized fund on Plume is more than an ERC-20. Mints, redemptions, and transfers ride alongside KYC and AML gating, allowlist updates, and transfer-agent actions. Reconstructing a clean holder ledger means joining the token events to the compliance events that decide whether each transfer was even allowed.

Yield and Distribution Flows Products like Nest vaults pay yield, accrue interest, and let holders loop RWA tokens into lending markets to borrow against them. Tracking real returns means following deposits, vault share accrual, distribution events, and the downstream collateral positions, not just a single balance snapshot.

Institutional Reporting Needs Issuers and the institutions behind tokenized credit, ETFs, and funds need auditable records: position history, settlement timing, and a complete event trail per asset. That bar is higher than a typical DeFi dashboard, and it has to survive over time as the dataset grows.

EVM Decoding Across Many Contracts A real Plume dataset spans dozens of contracts at once: asset tokens, vaults, the pUSD stablecoin, compliance modules, and partner protocols. Each needs its own ABI and event handling, and proxy upgrades make the right ABI a moving target.

What Indexing Co delivers for Plume

The DIY Path

Stand up and maintain the whole stack yourself.

Run a Plume archive node or wire up a third-party RPC.
Fetch and decode logs, traces, and receipts against the right ABIs.
Stitch token events to compliance and vault events by hand.
Build backfill, reorg handling, and real-time delivery from scratch.

Indexing Co

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

Plume RWA token events, compliance events, and yield 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 Plume, for example
Contract events and logs	Nest vault deposits, RWA token redemptions
Token transfers (ERC-20, ERC-721)	Tokenized fund shares, pUSD movements
Decoded transactions and traces	Compliance gating, onboarding, smart-account calls
Protocol and account state	Vault share balances, holder allowlists, loop positions

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

Plume with Indexing Co

Run it yourself if

You want full control of node infrastructure and have the team to operate a Plume archive node, decode every asset, vault, and compliance ABI, and build backfill and reorg handling in-house.

Use Indexing Co if

You want Plume RWA token events, compliance events, and yield 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 Plume node?

No. Indexing Co sources Plume 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 Plume?

Yes. Point a pipeline at any Plume contract or set of contracts, from Nest vaults and tokenized funds to the pUSD stablecoin or your own deployments, and we decode the events against the right ABI.

Can I capture compliance and onboarding events?

Yes. Because Plume is EVM-compatible, allowlist updates, transfer-agent actions, and KYC and AML gating emit decodable events, and we land them alongside the token transfers they govern so your holder ledger stays accurate.

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

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

Get Started

Index Plume in minutes. Set up your first Plume RWA token, vault, or compliance pipeline without running a node.