Proof of Liquidity on Berachain originally tied validator rewards to DeFi liquidity: validators directed BGT emissions to reward vaults, and users earned BGT by staking eligible positions. The Berachain bridge brought assets from other chains onto Berachain, where they could enter those positions. This design separated BERA, the gas and validator staking token, from BGT, a non-transferable governance and reward token; HONEY was Berachain’s stablecoin. Berachain’s current documentation now describes WBERA emissions instead, making this the original BGT model.
How Did Proof of Liquidity Turn Liquidity Into Rewards?
Proof of Liquidity routed block rewards through validators into approved reward vaults. A validator staked BERA to secure the chain. When it produced a block, it received BGT emissions and chose which eligible vaults would receive the distributable share. A vault divided incoming BGT among users staking its accepted receipt token. Each user’s share depended on their stake relative to the vault’s total and on how much BGT validators sent there.
Take an illustrative USDC holder. They move USDC through the Berachain bridge, convert part of it into HONEY, and supply both assets to an eligible USDC/HONEY pool. The pool issues an LP token representing their share. They stake that token in the matching reward vault. Only then does their position participate in that vault’s BGT stream. The bridge moves capital; the pool creates liquidity; the vault connects that liquidity to emissions.
The user can delegate earned BGT to a validator. More delegated BGT increased that validator’s boost and its BGT emissions when producing blocks. The validator could send more BGT toward the vault supporting the user’s pool. That is the loop: liquidity earns BGT, BGT delegation strengthens a validator’s reward capacity, and validator allocation attracts liquidity. A user could instead burn BGT 1:1 for BERA, giving up its governance and delegation role.
Protocols had a reason to enter this loop. One seeking deeper USDC/HONEY liquidity could offer incentive tokens to validators that allocated BGT to its vault. Validators received those incentives for directing emissions and could share them with BGT delegators. A generous offer could attract capital quickly, but could also pull emissions toward the highest bidder rather than the pool with the most useful trading liquidity.
In the BGT design, simply moving BERA onto Berachain earned no vault rewards. Ordinary users could not buy or bridge BGT: they had to stake an eligible asset in a reward vault to earn it. Holding an LP token outside its vault also missed that vault’s emissions. The useful question was which token a vault accepted and whether validators were sending emissions to it.
Related Questions
How Is BGT Different From BERA?
BGT was non-transferable governance and reward power, earned by users through the original reward vaults and delegable to validators. BERA paid gas and backed validator staking; BGT could be burned 1:1 for BERA, but the reverse route was unavailable. In the current PoL system, BGT no longer controls allocation or pays vault stakers; WBERA emissions do.
What Are Berachain Reward Vaults?
Berachain reward vaults are contracts that accept a specified eligible token, such as an LP receipt token, and pay stakers their share of routed emissions. In the original BGT model, validators decided which approved vaults received BGT. Today the vault still links a staked position to network rewards, but the payout is WBERA. Before using one, identify its accepted token and current emission stream.
Top comments (0)