Berachain proof-of-liquidity mechanism and tri-token structure

The mechanics of Proof-of-Liquidity

I observe Berachain’s Proof-of-Liquidity (PoL) mechanism creating a tight economic loop that forces capital to stay productive. In this system, liquidity providers deposit assets like $USDC into protocols such as BEX, BEND, or BERPS to earn $BGT governance tokens. These users receive liquidity certificate tokens, such as $HONEY-WBERA, which they stake in reward vaults to claim $BGT. Validators earn $BGT through block rewards and delegations from these providers. Validators then choose which reward vaults to direct their $BGT emissions toward to attract more delegators. This competition for $BGT delegations forces validators to prioritize the success of the liquidity pools they serve. I find the non-transferable nature of $BGT, which users can only exchange for $BERA at a 1:1 ratio, a significant limitation for those seeking quick asset movement. In the BEX protocol, users manage liquidity via the WarmPath contract and the CrocSwapDex contract. Users who provide liquidity on BEX obtain LP tokens and stake them in the PoL reward vault to receive $BGT. The BeraCrocMultiSwap contract handles multi-path token exchanges, while the HotPath handles common exchange logic and the KnockoutPath handles price boundary adjustments. In the BEND lending protocol, liquidity providers deposit $HONEY to receive AHONEY at a 1:1 ratio. Borrowers pledge crypto assets to borrow $HONEY tokens, and liquidators monitor the health coefficient of these borrowers to ensure the protocol remains solvent.

The tri-token model and modular architecture

The tri-token model separates network gas, governance, and stability. $BERA handles transaction fees and validator staking. $BGT manages governance and incentive distribution. $HONEY provides stability as a stablecoin pegged to the US dollar. Berachain builds its modular architecture on the Cosmos SDK to allow for cross-chain interoperability through the Inter-Blockchain Communication protocol. Because the BeaconKit consensus layer handles the consensus mechanism while the execution layer maintains EVM compatibility, developers can deploy Ethereum-based dApps directly onto Berachain without making any modifications to their existing code. You likely already understand how EVM compatibility reduces friction for developers. Validators who optimize their emission strategy to attract more $BGT delegations can increase their block rewards, which incentivizes them to keep the ecosystem liquid and secure for all participating users. The execution layer supports six mainstream EVM execution clients including Geth, Erigon, Nethermind, Besu, Reth, and Ethereumjs. The top N validators, ranked by their $BERA stake, form the Active Set and propose blocks. The BeaconKit framework encapsulates CometBFT to ensure it can interact with any execution environment compatible with the Ethereum Virtual Machine.

Vault yield and market scale

Early participants used pre-deposit vaults to capture yield. The Bitcoin Bera Vault accepted LBTC or wBTC on the Ethereum mainnet with a lock-up period ending April 14, 2025. The StakeStone Berachain Vault accepted ETH, STONE, WETH, or BTC-related assets to provide multi-layered yield. I note Berachain’s $BERA maintains a market cap of $32.67M, while Ethereum holds a market cap of $221.05B. Berachain’s 24-hour trading volume reaches $8.28M, while Ethereum’s volume is $1.64B. In a direct price comparison, Berachain’s $BERA is $0.0932, while Ethereum is $1,809.60. The circulating supply of Berachain is 350,451,821 BERA, whereas Ethereum has 122,151,332 ETH.

Will the current market cap of $32.67M expand as more liquidity providers enter the ecosystem?