Liquid Staking Token (LST) issuers can plug their staked-LST product into the Berachain Proof of Liquidity (PoL) Incentive Auction. Once anDocumentation Index
Fetch the complete documentation index at: https://docs.berachain.com/llms.txt
Use this file to discover all available pages before exploring further.
LSTStakerVault and its adapter are registered on BGTIncentiveFeeCollector, the vault automatically receives a pro-rata share of every WBERA payment auction buyers make against redirected Reward Vault incentive tokens.
This page is the integrator-facing guide. For the auction mechanics from the protocol side, see Incentive Marketplace — Incentive fee settlement.
What registration enables
When a buyer settles redirected incentive tokens throughBGTIncentiveFeeCollector, the WBERA they pay is split pro-rata, by WBERA-denominated total assets, across:
- The shared
WBERAStakerVault(sWBERA stakers). - Every registered
LSTStakerVaultwhose LST has an adapter that converts WBERA into the underlying LST.
How auction yield reaches an LST vault
- Reward Vaults transfer redirected incentive tokens (incentives not paid as validator commission) into
BGTIncentiveFeeCollector. - An auction buyer calls
claimFees(recipient, feeTokens)and pays WBERA into the collector. - The collector splits the paid WBERA pro-rata across the sWBERA Staking Vault and registered
LSTStakerVaults, sized by each vault’s WBERA-denominated total assets. - For each registered LST vault, the collector calls the vault’s registered adapter to convert that WBERA share into the vault’s underlying LST, then credits the LST to the vault through
receiveRewards. - The vault’s per-share value rises; its stakers earn the increment without taking any action.
Currently registered LSTs
The first registered LST is iBERA from Infrared. Its staked version, siBERA, accrues both the underlying iBERA yield and its pro-rata share of PoL incentive-auction WBERA via the registered LST adapter. Additional LSTs can be registered through the steps below.Integration steps for LST issuers
The integration is two contract deployments and one registry write. Coordinate with governance for the registry call.1. Deploy your LST vault system
Deploy theLSTStakerVault system via LSTStakerVaultFactory. The factory produces:
- An
LSTStakerVaultERC-4626-style vault that accepts your LST as the asset. - The supporting contracts for withdrawal accounting and reward receipt.
receiveRewards so that the collector can credit converted LST balances during auction settlement.
2. Deploy an LST adapter
The adapter is the contract that converts WBERA into your underlying LST during auction settlement. It must:- Accept WBERA from
BGTIncentiveFeeCollector. - Convert that WBERA into the LST (through your protocol’s mint, swap, or wrap path).
- Hand the resulting LST to the registered
LSTStakerVaultviareceiveRewards.
3. Register the vault and adapter with governance
Submit a governance proposal to calladdLstStakerVault on BGTIncentiveFeeCollector, supplying:
- The deployed
LSTStakerVaultaddress. - The deployed adapter address.
BGTIncentiveFeeCollector and LSTStakerVaultFactory addresses on each network.
Operational notes
- Vault total assets must be denominated comparably to WBERA. The collector sizes each vault’s share by its WBERA-denominated total assets; an adapter that misreports the underlying value will distort the split for every other registered vault.
- No staking-pool LSTs. Staking pool shares (stBERA) are not LSTs and cannot be registered through this path; they have their own yield mechanics. See Staking Pools Overview.
See also
- Incentive Marketplace — Incentive fee settlement — the auction mechanics from the protocol side.
- $sWBERA Token — the sister product that shares the pro-rata WBERA split.
- Deployed contract addresses — current
BGTIncentiveFeeCollectorandLSTStakerVaultFactoryaddresses. - Proof of Liquidity Overview — the broader PoL picture.