Berachain Data: Index Proof-of-Liquidity Flows and DeFi Onchain

Index Berachain's reward-vault emissions, sWBERA staking, and native DeFi events in one pipeline, delivered to your own database. Real-time and complete history, no node to run.

Berachain frames itself as a high-performance, EVM-identical Layer 1 built around Proof-of-Liquidity, a consensus design that ties network security directly to the liquidity flowing through its DeFi ecosystem. BERA pays gas and secures validators, HONEY is the native over-collateralized stablecoin, and since the July 2026 PoL Next upgrade retired BGT, emissions flow to reward-vault stakers as WBERA and sWBERA. The team lays out the mechanics at berachain.com.

That design is also what makes its data unusual. Because rewards do not flow straight to validators but get routed through governance-whitelisted reward vaults, the most valuable signals on Berachain are spread across emission events, vault stakes, and delegation moves, on top of the usual swaps and transfers. Indexing Co covers Berachain 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 Berachain blocks

Ingest blocks, logs, traces

Decode vault and pool ABIs

Transform your JavaScript

Deliver your database

Why Berachain data is hard

Proof-of-Liquidity Reward Flows On most chains, block rewards land on validators and you are done. On Berachain, validators emit WBERA and route it to whitelisted reward vaults, where stakers claim it as WBERA or sWBERA. Reconstructing who actually earned what means stitching together validator emissions, vault distributions, and per-staker accounting block by block.

Two Token Eras Berachain's token model changed in July 2026, when PoL Next retired the non-transferable BGT in favour of WBERA and sWBERA emissions. A complete dataset has to span both eras: BGT earning, delegation, and redemption before the upgrade, and sWBERA accrual after it.

A Fast-Moving DeFi Surface Native primitives BEX and Bend sit alongside ecosystem protocols like Infrared, plus a long tail of vaults added through governance. New reward vaults and pools appear continuously, and each one needs its own ABI and event handling to index correctly.

Your Own DB, Not a Hosted API Public RPC endpoints and hosted query layers leave you rate-limited and renting someone else's schema, which is a poor fit for the join-heavy queries PoL data demands. Powering an app or analytics workload on Berachain means owning the data in your own store, shaped the way your product reads it.

What Indexing Co delivers for Berachain

The DIY Path

Stand up and maintain the whole stack yourself.

Run a Berachain node or wire up a third-party RPC.
Decode logs, traces, and receipts against reward-vault, BEX, and Bend ABIs.
Track newly whitelisted vaults and proxy upgrades by hand.
Build backfill, reorg handling, and real-time delivery from scratch.

Indexing Co

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

Reward-vault emissions, sWBERA staking, swaps, and transfers 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 Berachain, for example
Contract events and logs	BEX swaps, Bend borrows, reward-vault claims
PoL and vault activity	Reward-vault stakes, WBERA emissions, validator distributions
Token transfers and staking	HONEY mints and burns, sWBERA deposits and claims
Protocol and account state	sWBERA balances, HONEY collateral, BEX pool weights

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

Berachain with Indexing Co

Run it yourself if

You want full control of node infrastructure and have the team to operate a Berachain node, decode every reward vault and protocol ABI, and build backfill and reorg handling in-house.

Use Indexing Co if

You want Berachain reward-vault flows, staking, and DeFi events 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 Berachain node?

No. Indexing Co sources Berachain blocks, logs, and traces for you, including full historical data back to mainnet launch, so you never operate a node or babysit an RPC endpoint.

Can I index Proof-of-Liquidity reward flows?

Yes. Point a pipeline at the reward vaults and validator contracts, and we decode the emission, stake, and distribution events so you can reconstruct who earned rewards, including the BGT era before July 2026, not just raw transfers.

Which Berachain protocols can I index?

Any of them. Native primitives like BEX and Bend, ecosystem protocols like Infrared, or your own deployments. Because Berachain is EVM-identical, every contract decodes against a standard Solidity ABI.

Does Indexing Co handle the BGT era and the move to sWBERA?

Yes. We index BGT history where it actually moved, in vault accruals, delegation, and redemption, and the WBERA and sWBERA flows that replaced it in July 2026, so your dataset spans both models.

Where does the Berachain data go?

Into your own destination: PostgreSQL, BigQuery, a warehouse, or a webhook. You define the output schema and own the storage.

Get Started

Index Berachain in minutes. Set up your first reward-vault, pool, or token pipeline without running a node.