Berachain(BERA)

Berachain is a Layer 1 blockchain built for EVM-compatible applications. That means wallets and applications designed for Ethereum-style networks can connect to Berachain by adding its custom RPC settings. The Berachain mainnet uses chain ID 80094, the RPC URL https://rpc.berachain.com/, BERA as the native currency symbol, and Berascan as its block explorer.

BERA is the network token used to pay for transactions on Berachain. The official docs describe several ways to get BERA, including bridging through the Berachain Bridge, powered by LayerZero, or buying it on supported centralized exchanges. The docs also describe a testnet named Berachain Bepolia, which uses a separate RPC endpoint and explorer for testing.

Berachain’s application layer includes native protocols such as BEX and Bend. BEX is Berachain’s native decentralized exchange, with swaps, liquidity provision, pool creation, weighted pools, stable pools, fees, and Proof of Liquidity reward flows. Bend is a lending and borrowing protocol on Berachain, based on Morpho-style markets and vaults. Bend users can supply assets, borrow HONEY, monitor loan-to-value metrics, repay debt, and withdraw collateral.

A key theme in the documentation is Proof of Liquidity, often shortened to PoL. In Berachain’s own application examples, PoL connects liquidity provision or lending positions with reward vaults and staking. This makes liquidity supply part of the network’s incentive design rather than a separate add-on.

Key facts

• Project: Berachain
• Token: BERA
• Network type: EVM-compatible Layer 1 blockchain
• Mainnet chain ID: 80094
• Mainnet RPC: https://rpc.berachain.com/
• Explorer: https://berascan.com/
• Native token role: BERA is used for transaction fees and staking according to the official docs.
• Core apps in the docs: BEX for swaps and liquidity, Bend for lending and borrowing, Honey for stablecoin-related flows.
• Source reference: https://docs.berachain.com/

Berachain is best understood as a chain plus a native DeFi stack. The chain provides the EVM-compatible execution environment, while applications such as BEX and Bend show how liquidity, lending, borrowing, vaults, and rewards are intended to function inside the ecosystem.

Berachain Introduction#

Berachain is an EVM-compatible Layer 1 blockchain with a native token called BERA. The project documentation presents Berachain as a blockchain network that users can add to common EVM wallets, including MetaMask, Rabby, Coinbase Wallet, and Brave Wallet. Its mainnet uses chain ID 80094, the RPC endpoint https://rpc.berachain.com/, BERA as the native currency symbol, and Berascan as the main block explorer. Berachain — Berachain (BERA) is a cryptocurrency launched in 2025and ope…

The project’s public documentation is organized around both network access and application use. At the network level, users need BERA to pay transaction fees and interact with applications. The docs describe getting BERA through the Berachain Bridge, powered by LayerZero, or through exchanges where BERA is listed. At the application level, the docs cover native Berachain protocols such as BEX, a decentralized exchange, and Bend, a lending and borrowing protocol.

Berachain’s design is closely associated with Proof of Liquidity, or PoL. The available documentation does not present PoL as a simple marketing slogan; it appears across product flows such as BEX liquidity provision and Bend lender rewards. For example, the BEX documentation explains that users can provide liquidity and stake LP tokens in reward vaults. Bend documentation also refers to PoL reward yield from staking vault shares. In plain language, Berachain’s ecosystem aims to connect liquidity-providing activity with network-level incentives.

This explanation separates the chain, the token, and the applications. Berachain is the blockchain network. BERA is the native token used for fees and staking. BEX and Bend are applications that run within the Berachain ecosystem. HONEY appears in the Bend documentation as an asset users can borrow, but it is not the same thing as BERA. Keeping those roles separate matters because a blockchain, a gas token, a stablecoin asset, a DEX, and a lending market all serve different purposes.

Part 1: Whitepaper Review#

The source reference for this explanation is the official Berachain documentation at https://docs.berachain.com/. The provided source material includes pages for connecting to Berachain, getting BERA, using BEX, and using Bend. It also includes an index of documentation pages that describe pool mechanics, lending markets, vaults, oracles, flash loans, liquidation, interest rates, and Proof of Liquidity reward paths.

The connection guide gives direct technical settings for the network. For mainnet, the network name is Berachain, the RPC URL is https://rpc.berachain.com/, the chain ID is 80094, the currency symbol is BERA, and the block explorer is https://berascan.com/. The guide also lists Bepolia, a testnet, with chain ID 80069, RPC URL https://bepolia.rpc.berachain.com/, currency symbol BERA, and explorer https://testnet.berascan.com/. The docs state that any EVM-based wallet supporting custom RPCs can work with Berachain.

The “How to Get BERA” page explains the practical role of BERA. It states that BERA is the network token used to pay for transactions on Berachain. It also describes BERA as needed for gas and staking. The page lists two broad access routes: bridging and exchanges. Bridging is supported through the Berachain Bridge, which is powered by LayerZero. The docs also list several centralized exchanges where BERA trades. This does not imply any future value, return, or safety; it simply explains how users can obtain the token to use the network.

The BEX documentation describes Berachain’s native decentralized exchange. BEX supports swaps, liquidity provision, pool creation, token metadata submissions, fees, stable pools, weighted pools, and Proof of Liquidity flows. The docs describe BEX as using a Balancer V2-style architecture, with pool types suited for different token relationships. Stable pools are intended for stablecoins and correlated assets, while weighted pools support configurable token weights. The provided index also notes that BEX flash loans are currently disabled through protocol fees.

The Bend documentation describes decentralized lending on Berachain. Bend is described as Morpho-based lending and borrowing with native Proof of Liquidity on Berachain. Its docs explain markets, vaults, curators, allocators, public allocators, interest rates, liquidation, collateral ratios, LTV, health factors, flash loans, and oracles. A market is a lending pool primitive built around a collateral and loan pairing. Vaults are yield-generating structures with curator and allocator roles. Curators handle vault strategy, risk parameterization, market selection, caps, and timelock settings. Allocators and public allocation mechanisms help adjust liquidity between markets.

In Bend, users can supply collateral, borrow HONEY, monitor LTV and LLTV, repay debt, and withdraw collateral. Lenders can supply HONEY to vaults, stake vault shares for PoL rewards, unstake, and withdraw. Interest rates are described through an AdaptiveCurveIRM that reacts to utilization and target utilization. Liquidation is tied to health factor and liquidation loan-to-value thresholds. Oracles provide price data for Bend markets, and the docs describe an oracle-agnostic design compatible with different oracle types.

The source material gives a meaningful view of how Berachain’s application layer is structured, but it does not provide every economic detail. Circulating supply and total supply values are available from the job metadata, but the provided documentation excerpt does not disclose a full token allocation schedule, vesting table, emissions curve, or validator reward formula. For a neutral explanation, those missing details should not be invented.

Part 2: Analysis#

Berachain’s main differentiator is its focus on liquidity as part of network coordination. Many Layer 1 blockchains use the same broad pattern: a native token pays gas, validators or other operators secure the network, and applications compete for users and liquidity. Berachain’s documentation shows a different emphasis by placing Proof of Liquidity inside application-level flows. BEX and Bend are not isolated examples; both connect user-supplied liquidity or vault shares with reward-related mechanics.

For a user, the first experience is familiar to anyone who has used EVM networks. They add a custom RPC to an EVM wallet, acquire BERA for gas, and interact with applications through wallet signatures. This lowers the learning curve for users already familiar with Ethereum-style wallets and block explorers. It also means developers and analysts can reason about Berachain using common EVM concepts such as accounts, contract interactions, transaction fees, and RPC endpoints.

BEX gives the ecosystem a native venue for token swaps and liquidity pools. Its Balancer V2-style model is important because it supports more than simple two-token constant-product pools. Weighted pools can define different asset weights, while stable pools are designed for stablecoins and correlated assets. Fee documentation explains that trading fees are split between liquidity providers and the protocol, and can be compounded in pools. Pool creation documentation covers initial ratios, fee tiers, and token burn requirements.

Bend adds a lending layer. Its market design pairs collateral and loan assets, while vaults can route supplied assets into multiple markets according to curator decisions and allocator activity. The docs emphasize risk controls such as LTV, liquidation loan-to-value, health factor, market caps, queues, timelocks, and oracle selection. These are essential concepts in lending systems because lenders and borrowers are exposed to price movements, liquidity shifts, interest-rate changes, and oracle behavior.

The relationship between Bend and Proof of Liquidity is especially relevant. Lenders can earn native lending yield from borrower interest, and the docs also refer to PoL reward yield from staking vault shares. This creates a layered return structure for lenders, but it also adds complexity. A user must distinguish between base lending yield, reward yield, vault risk, market risk, collateral risk, oracle risk, liquidation risk, and smart contract risk. ChainClarity’s neutral framing is that these mechanics are design features, not guarantees of outcome.

Berachain’s token, BERA, has a clear source-backed role as the native network token used for transaction fees and staking. The provided job metadata states a current supply of 545,560,428.6693658 BERA and a circulating supply of 293,203,484.2249213 BERA. The available docs do not provide enough detail to describe distribution, vesting, emissions, insider allocation, validator economics, or long-term supply rules. That missing information limits the depth of tokenomics analysis from the provided source set.

The most important risk areas are also familiar across DeFi networks. First, application risk: BEX pools and Bend vaults depend on smart contracts, pool configuration, oracle inputs, and liquidity conditions. Second, liquidation risk: borrowers on Bend must monitor LTV, LLTV, and health factors. Third, oracle risk: lending systems rely on accurate price data. Fourth, governance and parameter risk: curators, market parameters, caps, timelocks, and allocation decisions affect vault behavior. Fifth, bridge risk: users obtaining BERA through bridging interact with cross-chain infrastructure.

Berachain is therefore best explained as a Layer 1 network with a native DeFi stack built around liquidity incentives. Its documentation is more detailed on how to use the network and applications than on long-form economic disclosure. The result is a project with clear operational materials for users and developers, but with token distribution and long-term economics requiring separate source confirmation before making strong claims.

Internal Linking Section#

Readers comparing Berachain with other chains can start with Ethereum, since Berachain is EVM-compatible and uses familiar wallet and contract interaction patterns. For a different high-throughput Layer 1 model, see Solana. For another EVM-focused chain with its own ecosystem and validator structure, see Avalanche. For a base asset comparison, Bitcoin offers a simpler monetary network model without Berachain’s DeFi application stack.

FAQ

Q: What is Berachain? A: Berachain is an EVM-compatible Layer 1 blockchain. Its docs describe wallet connection settings, the BERA token, and ecosystem applications such as BEX and Bend.

Q: What is BERA used for? A: The official docs state that BERA is the network token used to pay for transactions on Berachain and is also used for staking.

Q: What is BEX? A: BEX is Berachain’s native decentralized exchange. It supports swaps, liquidity provision, pool creation, weighted pools, stable pools, fee mechanics, and Proof of Liquidity reward paths.

Q: What is Bend? A: Bend is a lending and borrowing protocol on Berachain. It includes markets, vaults, curators, allocators, interest-rate models, liquidation rules, and oracle support.

Q: What is Proof of Liquidity? A: In the provided documentation, Proof of Liquidity is connected to reward flows for liquidity-related activity, such as staking LP tokens in BEX reward vaults or staking Bend vault shares.

Q: Is HONEY the same as BERA? A: No. BERA is the native token used for network fees and staking. HONEY appears in the Bend documentation as an asset users can borrow in lending flows.

Q: Does the documentation disclose full BERA token allocation details? A: The provided source material does not disclose a full allocation, vesting, emissions, or distribution schedule. Those numeric facts should not be assumed from the available excerpts.