Berachain RPC Endpoint

Fast, flat-rate Berachain RPC node provider — free tier, no KYC, HTTP & WebSocket.

Berachain is an EVM-identical Layer 1 built on a Proof-of-Liquidity consensus model. Instead of rewarding raw staking, Proof-of-Liquidity ties validator rewards to liquidity provided to the ecosystem, aiming to align chain security with on-chain economic activity.

About Berachain

Berachain launched its mainnet in February 2025. It is built with the BeaconKit framework on CometBFT consensus while remaining fully EVM-identical, so Solidity contracts and standard Ethereum tooling deploy unchanged. The chain uses a tri-token model: BERA for gas, BGT (a non-transferable governance token earned by providing liquidity) for emissions and voting, and HONEY, a native stablecoin.

Proof-of-Liquidity routes block rewards through BGT to liquidity providers and the protocols they support, creating a flywheel intended to keep liquidity and security on-chain. The model drew a large pre-launch ecosystem of DeFi protocols building specifically around BGT incentives.

Common Use Cases on Berachain

• Liquidity-incentivized DeFi (BGT emissions)
• Deploying existing Ethereum contracts unchanged
• Native stablecoin (HONEY) applications
• Validator participation tied to liquidity provision
• Yield and liquidity-routing strategies

Berachain Ecosystem

Berachain's ecosystem centers on its native DeFi — BEX (DEX), Berps (perps), Bend (lending) — plus a wide set of third-party protocols competing for BGT-directed emissions. Being EVM-identical, mainstream Ethereum protocols port over directly.

HTTP Endpoint

WebSocket Endpoint

Quick Start: Connect to Berachain

cURL

curl -X POST https://rpc.swiftnodes.io/rpc/berachain?key=YOUR_API_KEY \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'

ethers.js

import { JsonRpcProvider } from "ethers";

const provider = new JsonRpcProvider(
  "https://rpc.swiftnodes.io/rpc/berachain?key=YOUR_API_KEY"
);

const blockNumber = await provider.getBlockNumber();
console.log("Berachain block:", blockNumber);

viem

import { createPublicClient, http } from "viem";

const client = createPublicClient({
  transport: http("https://rpc.swiftnodes.io/rpc/berachain?key=YOUR_API_KEY"),
});

const blockNumber = await client.getBlockNumber();

web3.py

from web3 import Web3

w3 = Web3(Web3.HTTPProvider("https://rpc.swiftnodes.io/rpc/berachain?key=YOUR_API_KEY"))
print("Berachain block:", w3.eth.block_number)

Add Berachain to MetaMask

Bridging to Berachain

Canonical and third-party bridges (including LayerZero-based routes) connect Berachain to Ethereum and other chains for moving assets in and out.

Features of SwiftNodes for Berachain

• Multiple load-balanced upstream nodes for high availability
• Health-checked every 60 seconds with automatic failover
• Free tier available — no credit card or KYC required
• Flat-rate monthly pricing with no per-request fees
• HTTP and WebSocket support
• One API key works across all 75+ supported chains, including Berachain

Rate Limits

Frequently Asked Questions: Berachain

Berachain guides from the blog

• Berachain RPC: Standard EVM, but the Token You Earn Can't Be TransferredBerachain is an EVM-identical L1 (chain ID 80094) on a Proof-of-Liquidity consensus with a tri-token model: BERA for gas, HONEY as a native stablecoin, and BGT — a governance token you earn but cannot transfer. The RPC is standard eth_* (viem/ethers/foundry work), but treating BGT like a normal ERC-20 breaks. Here's the developer map.
• Connecting MetaMask to Sonic, Berachain, and MonadThree of 2025's biggest EVM chain launches, three sets of MetaMask configuration values. The exact fields to paste, why the official public RPCs aren't enough for real use, and the errors to expect when you mistype something.

Related L2 & rollup chains

Explore RPC endpoints for other L2 & rollup networks on SwiftNodes: