How Does BEND Work?
BEND is Berachain's native lending protocol, forked from the battle-tested Morpho codebase. It enables permissionless lending and borrowing of ETH, BTC, BERA derivatives, and stablecoins through isolated markets. With ~$17M TVL, it benefits from Berachain's Proof-of-Liquidity rewards but is still very early in its operating history.
TVL
$11M
Sector
Lending
Risk Grade
B-
Value Grade
D
Core Mechanisms
6.1.4
Morpho-style isolated lending markets where each market has independent risk parameters
Inherited from Morpho v1 — permissionless market creation with per-market isolation
6.2.2
Kinked utilization curve inherited from Morpho for interest rate setting
Standard rate model with kink point driving borrowing costs
6.4.1
External oracle feeds for collateral pricing (ETH, BTC, BERA derivatives, stablecoins)
Oracle pricing critical for liquidation triggers across all markets
6.3.2
Fixed-spread liquidation mechanism from Morpho for underwater positions
Liquidators receive a bonus for closing undercollateralized positions
2.2.4
Revenue split between vault depositors and the protocol via curator-managed vaults
Re7 Labs serves as first curator managing vault allocations and fees
3.1.1
NovelProof-of-Liquidity (PoL) BGT reward distribution to depositors who supply liquidity
Novel integration of Berachain PoL consensus rewards with lending — depositors earn BGT alongside interest
How the Pieces Interact
Each isolated market depends on its own oracle feed — a single feed failure can trigger bad debt in that market without protocol-wide safeguards
BGT reward emissions may attract mercenary capital that deposits only for rewards, distorting utilization rates and interest rate accuracy
During rapid price declines, oracle latency could delay liquidation triggers, allowing bad debt to accumulate before liquidators act
Curator allocation decisions concentrate depositor funds in specific markets — poor curation could expose vault depositors to higher-risk markets
BGT reward rate changes could cause sudden capital flows between vaults, creating utilization spikes and withdrawal liquidity issues
What Could Go Wrong
- Oracle dependency for collateral pricing across multiple asset types with no public fallback details
- Relatively new deployment on Berachain mainnet (launched Feb 2025) despite being based on well-audited Morpho codebase
- Proof-of-Liquidity integration introduces novel staking-lending coupling not battle-tested at scale
Oracle Failure Cascading Through Isolated Markets
ModerateTrigger: A primary oracle feed for a major collateral type (e.g., BERA derivatives) goes stale or reports incorrect prices during high volatility
- 1.Oracle feed for BERA-derivative collateral returns stale or incorrect price — Liquidation engine cannot correctly assess position health in affected markets
- 2.Undercollateralized positions accumulate as liquidators wait for accurate pricing — Bad debt accrues in the isolated market beyond what the liquidation spread can cover
- 3.Lenders in the affected vault realize losses from socialized bad debt — Depositors begin withdrawing from all vaults as confidence drops
- 4.Utilization rates spike across remaining markets as deposits flee — Interest rates jump, borrowers face margin calls, creating cross-market stress
- 5.BGT reward attractiveness drops as depositors exit the protocol — Reduced TVL weakens Berachain PoL security contribution
Risk Profile at a Glance
Overall: B- (33/100)
Lower score = safer