All chains
Berachain

Berachain

EVM Layer 1 / Chain ID 80094

Berachain is an EVM-compatible Layer 1 built on Proof of Liquidity consensus, aligning network security with DeFi activity.

Quick Facts
Networks 2
Runtime EVM
Chain ID 80094
Real-time Yes
Data tables 5
Category Layer 1
Networks
2
Data tables
5
Chain ID
80094
Runtime
EVM
Coverage
Real-time + archive
Start block
0 (genesis)
License
Open-source SDK

Networks

berachain-mainnet
Real-time EVM mainnet 5 tables
berachain-bartio
EVM testnet 5 tables

Berachain on SQD

Validated at ingestion

Berachain data is validated by SQD Network workers before it reaches the Portal. Validation is performed across the network rather than by a single ingestion node, so a faulty upstream source can't poison the dataset.

Decoded, schema-typed

5 Berachain tables (blocks, transactions, logs & traces), decoded and schema-typed, ready to query. Your indexer queries the data directly without writing RLP parsers.

Archive plus real-time

Single Portal endpoint serves Berachain from genesis through the current head, with sub-second hot-path latency. No separate streaming pipeline to wire up.

Open-source SDK

Both the Squid SDK and the Pipes SDK are open-source. Connectors for Postgres, ClickHouse, MongoDB, SQLite and Parquet, plus a custom-target hook. Run your Berachain indexer on your own infrastructure or on SQD Cloud.

Build with Berachain data

Common production patterns teams build with SQD on Berachain.

Available Data

blocks

Block headers with timestamps, gas usage, miner info, and consensus data.

transactions

All onchain transactions with sender, receiver, value, gas, and input data.

logs

Event logs emitted by smart contracts, the primary source for tracking DeFi, NFT, and token activity.

traces

Internal transactions and call traces showing the full execution path of each transaction.

state_diffs

State changes per transaction, storage slot modifications, balance changes, and nonce updates.

Stream Berachain data in two lines

Example below uses the public Berachain endpoint, no API key required for development. For full SDK reference, see the documentation.

1curl --compressed -X POST \
2 'https://portal.sqd.dev/datasets/berachain-mainnet/stream' \
3 -H 'Content-Type: application/json' \
4 -d '{
5 "type": "evm",
6 "fromBlock": 0,
7 "toBlock": 100,
8 "fields": {
9 "block": {"number":true,"timestamp":true},
10 "transaction": {
11 "hash": true,
12 "from": true,
13 "to": true,
14 "value": true
15 }
16 },
17 "transactions": [{}]
18 }'
berachain-mainnet/stream
EVM · blocks 0100

Frequently asked questions

How does SQD compare to running a Berachain RPC node?
A Berachain RPC node serves raw bytes for recent state and rate-limits per request. SQD's Portal pre-indexes the full Berachain archive into decoded, schema-typed tables (blocks, transactions, logs & traces) and serves them as a single streaming endpoint. You skip the multi-day node sync, archive storage, monitoring, and scale-out work, and pay only for the data you stream.
What does SQD cost for Berachain data?
The public Portal endpoint at portal.sqd.dev/datasets/berachain-mainnet is free for development with no API key. Production workloads run on the SQD Portal with tiered pricing based on the network and request volume. See the pricing page for current tiers, or contact us for an enterprise quote.
How is SQD's Berachain data different from a block explorer like Etherscan?
Block explorers are read-optimized for human browsing of single blocks or addresses. SQD is built for programmatic indexing: stream millions of Berachain blocks into your own database, run analytical queries across the full history, and back production applications with decoded data. Output is structured tables, not HTML pages, and there are no per-call rate limits geared toward UI traffic. If you wanted to build your own Berachain explorer, the SQD Portal is what you would back it with.
Can I self-host SQD's Berachain indexer?
Yes. Both the Squid SDK and the Pipes SDK are open-source. You can run a Berachain indexer on your own infrastructure pointing at the SQD Network or the Portal. SQD Cloud also offers managed hosting if you'd rather not operate it yourself.
Can I export Berachain data to a data warehouse or pipeline?
Yes. The Pipes SDK streams Berachain data from the Portal into Postgres, ClickHouse, MongoDB, SQLite, Parquet, or a custom target you implement. See the SDK docs for the connector reference.
Does SQD validate Berachain data?
Every Berachain block ingested into SQD is validated by the SQD Network workers (hash chain, parent reference, and where applicable finality) before it reaches the Portal. Validation is performed across the network, not by a single ingestion process, so a faulty upstream node can't poison the dataset.
Does SQD support real-time Berachain data?
Yes. Berachain is served with both real-time and historical data from the same Portal endpoint, with sub-second latency on the hot path. No separate streaming pipeline to wire up.

See other chains supported by SQD

Start building with Berachain

Access Berachain data through the SQD Portal, free tier available.