Bonzo is hedera's paused single-asset lending market
Bonzo is a non-custodial market - users retained wallet control - whose single-asset pools each held one token for lending and collateral-backed borrowing on Hedera. Bonzo Lend used Aave V2-derived smart contracts, utilization-based rates, and oracle prices to account for supplies and debt. The lending market remains paused after a July 2026 oracle verification failure, so new deposits, borrowing, and ordinary withdrawals are not the live entry path. The pause did not affect Bonzo Vaults, Bonzo Bridge, or BONZO/XBONZO staking.
It is a non-custodial lending protocol on Hedera where users supply assets to single-asset pools and borrow against collateral as utilization sets variable rates.
Bonzo Lend's pause changes the entry decision
The Bonzo Lend market remains paused, so prospective suppliers and borrowers have no ordinary entry while the recovery process is prepared.
On July 11, 2026, a third-party oracle verifier accepted an abnormal SAUCE price update. Bonzo Lend read that value when calculating collateral, allowing debt far beyond the asset's economic value. The pool then carried a shortfall, and the protocol paused lending, borrowing, Bonzo Points, and ordinary withdrawals. Price data was therefore part of the credit mechanism, not a dashboard decoration. Wallet keys stayed with users, but supplied assets remained inside smart contracts and depended on their accounting and integrations.
The recovery plan assigns funding to restore affected positions at their values immediately before the event. Bonzo Finance Labs also began building a separate redemption mechanism, with Halborn reviewing the new contracts before deployment.
Other Bonzo components followed separate contracts and accounting. Vaults continued running automated strategies, the Bridge remained available, and single-sided BONZO/XBONZO staking continued operating. A product name alone therefore does not establish whether the pause applies.
Bonzo beside Hedera staking and lending alternatives
Among Bonzo alternatives, the first differences are the activity performed, the network used, and who controls deposited assets after signing.
The follow-on topic is treated in Bonzo tutorial. Hedera native staking keeps HBAR in its account and delegates stake to a consensus node; it provides no borrowing. SaucerSwap V2 places two assets into an automated-market-maker position, adding price-range management and paired-asset exposure. Aave V3, Compound III, and Venus Protocol provide non-custodial lending on other networks, so choosing one also means choosing its supported chains, collateral lists, and wallet infrastructure. Each protocol sets its own liquidation and reserve rules, while none duplicates Bonzo's combination of HTS reserves and Hedera settlement.
| Route | Custody or control model |
|---|---|
| Hedera native staking | HBAR remains in the Hedera account under its account key. |
| SaucerSwap V2 | Two assets enter AMM contracts; the wallet controls the liquidity position. |
| Aave V3 | Protocol contracts hold supplied liquidity; the wallet controls its account position. |
| Compound III | A Comet market holds assets and collateral under wallet-authorized account logic. |
| Venus Protocol | Market contracts hold pooled assets; the connected wallet controls transactions. |
HBAR holders seeking yield without debt start from native staking. Users seeking pooled credit compare Aave V3, Compound III, and Venus Protocol alongside the network transfer involved. SaucerSwap V2 serves a liquidity-provision decision rather than a like-for-like loan.
What did Bonzo's single-asset pools change?
Single-asset reserves gave Bonzo one underlying token per pool, removing the paired-token requirement of an automated market maker.
Supply accounting
Each reserve accepted 1 underlying asset, so an HBAR supplier did not also need USDC or another token. Bonzo recorded the supplier's share and increased its claim as borrower interest accrued. Because the contract did not rebalance a two-token pair, the position avoided impermanent loss. It still carried the market exposure of the supplied asset, smart-contract risk, and dependence on unborrowed pool liquidity for routine withdrawals.
Incentive accounting
The interface separated 2 reward streams. Native supply interest auto-compounded and followed borrower demand, while liquidity incentives added separately funded rewards in assets such as HBAR, USDC, DOVU, or KARATE. Users had to claim incentive rewards manually. Their duration followed the funded emission allocation rather than the reserve's interest formula, so an incentive display represented a distinct economic input.
How did Bonzo turn collateral into borrowing power?
Collateral values gave Bonzo Lend limited borrowing power, while a health factor determined when liquidation became available.
Loan-to-value limits
Loan-to-value, or LTV, multiplied oracle-valued collateral by a reserve-specific percentage to set the opening debt ceiling. Bonzo configured LTV separately for each eligible asset and applied borrow caps to the debt reserve. A wallet balance outside the protocol added no borrowing power, while collateral disabled inside the dashboard stopped contributing to the calculation.
Health-factor movement
The health factor compared weighted collateral at its liquidation thresholds with the account's total debt. Price changes and accrued interest moved this ratio without another wallet transaction. A Bonzo Lend position became eligible for liquidation below a health factor of 1, and a liquidator could repay up to 50% of its debt.
Collateral transferred during liquidation
Liquidation reduced the outstanding debt and transferred corresponding collateral plus the reserve's configured bonus to the liquidator. Each asset carried its own threshold and bonus, reflecting liquidity and price characteristics. Borrowing farther below the displayed maximum left a larger buffer before relative price movement or interest accumulation reached the trigger.
Where did Bonzo's supply yield come from?
Quoted supply yield in Bonzo came from borrower interest plus optional token incentives, with each component following different accounting.
Borrowed liquidity divided by supplied liquidity produced utilization. The Aave V2-derived model used 2 rate segments around a configured optimal-utilization point: the first slope increased borrowing cost gradually, and the second raised it faster as unused liquidity became scarce. At 100% utilization, no unborrowed balance remained for an ordinary withdrawal. Supplier interest followed the borrower rate and utilization after subtracting the reserve factor. Incentives sat on top of that amount. Flash loans also began and ended within 1 transaction, carrying a fixed 0.09% fee whose distribution contributed to reserve economics.
Wallet, token, and network prerequisites
Opening a Bonzo Lend position required a Hedera-compatible wallet, HBAR for fees, an associated token, and an open market.
Hedera-compatible wallets such as HashPack, Blade, and Kabila manage account signatures and HTS token associations. Mainnet uses EVM chain ID 295, while a contract address occupies 20 bytes and appears as 40 hexadecimal digits after the optional prefix. HBAR uses 8 decimal places: 1 HBAR equals 100,000,000 tinybars, and one tinybar equals 0.00000001 HBAR. A standard Hedera transaction's valid duration cannot exceed 180 seconds, so an expired wallet request must be rebuilt before reaching consensus. These are network properties, not Bonzo market settings.
Under normal operation, the entry path ran from wallet connection to asset supply, followed by an optional collateral setting and borrowing transaction. The dashboard then showed the supply balance, debt, available borrowing power, and health factor. While Lend remains paused, those historical steps describe the mechanism rather than an available onboarding route.
The controls beneath each reserve
Reserve-level limits, external prices, and fee routing kept each Bonzo Lend pool inside its configured credit boundaries.
Supply and borrow caps
Supply caps blocked deposits after a reserve reached its configured token amount, while borrow caps limited outstanding debt in the same asset. The two controls operated independently. Because administrators expressed caps in token units rather than a shared currency value, every reserve required its own calibration.
Oracle-priced collateral
Oracle feeds converted HBAR, USDC, SAUCE, and other collateral into comparable account values. The architecture integrated 2 named oracle systems, Supra and Chainlink, with feeds assigned by asset. Bonzo contracts then combined those prices with LTV settings, liquidation thresholds, and debt balances. The July 2026 event demonstrated the consequence of this dependency: a correct token quantity paired with an abnormal accepted price produced incorrect borrowing capacity.
Reserve factor and token supply
The reserve factor routed a configured portion of borrower interest to protocol revenue before suppliers received their share. BONZO had a fixed maximum supply of 400,000,000 tokens, but that token limit did not set a reserve's interest curve. Borrow demand, utilization, caps, collateral parameters, and fee routing remained separate contract-level inputs.
The next decision while lending remains paused
The next step for Bonzo depends on whether the reader held a paused position or was only evaluating the market. A sibling page deals with Bonzo walkthrough.
Existing Lend positions fall within the recovery and redemption process rather than the ordinary withdrawal flow. The recovery valuation used the position snapshot immediately before 00:51:39 UTC on July 11, 2026, and the redemption mechanism required separate Hedera contracts. Distinguishing Lend from Vaults, Bridge, and BONZO/XBONZO staking prevents unrelated balances from being treated as one product state.
A prospective user first chooses the desired mechanism: native HBAR staking, paired liquidity on SaucerSwap V2, or collateralized borrowing through a lending protocol. Borrowing adds health-factor management and liquidation exposure; supply-only strategies do not create debt. Bonzo becomes an actionable lending choice again only after its Lend markets reopen.
Still wondering about Bonzo?
Is the BONZO token required for a lending position?
BONZO was not required merely to supply an asset or borrow against collateral. The lending contracts accepted supported reserve assets, while BONZO served separate incentive, staking, and governance-related roles. Its fixed maximum supply is 400,000,000 tokens, but owning any portion did not create borrowing capacity. Collateral value, the reserve's loan-to-value setting, and the account's existing debt determined borrowing power before the market pause.
Does a supply-only Bonzo position face liquidation?
A supply-only Bonzo position did not qualify for liquidation because it carried no borrowed balance. Supplied assets were enabled as collateral by default, yet liquidation required debt and a health factor below 1. A user could also disable a supplied asset as collateral while continuing to receive native supply interest and eligible incentives. The market pause now controls access and withdrawals separately from this normal liquidation rule.
What network fees applied to Bonzo transactions?
Each Bonzo transaction paid a Hedera network fee in HBAR rather than a flat subscription or deposit charge. Hedera's fee model contains 3 components: node, network, and service fees. Smart-contract actions also consume gas, so the wallet estimate reflected the call's work and the network's HBAR conversion rate. The protocol separately routed borrower interest, reserve-factor revenue, liquidation bonuses, and the fixed 0.09% flash-loan fee.
Are Bonzo Vaults the same product as Bonzo Lend?
Bonzo Vaults and Bonzo Lend are separate products with different position accounting. Bonzo Lend pooled assets for collateral-backed borrowing, while Vaults placed a deposited primary asset into an automated strategy and issued vault shares. The July 2026 pause applied to Lend and Bonzo Points; Vaults, Bonzo Bridge, and BONZO/XBONZO staking remained unaffected. A vault balance therefore should not be interpreted as a lending-market supply balance.
What happens after a Bonzo market reaches its supply cap?
A Bonzo market at its configured supply cap rejected additional deposits until total supplied tokens fell below that cap. Existing suppliers did not lose their recorded positions simply because administrators lowered a cap beneath the outstanding amount. Withdrawing first could therefore prevent an immediate re-supply. Caps used token units per reserve, so a cap for HBAR was not numerically comparable with one for USDC or SAUCE.
Why might an HTS token association be required before using Bonzo?
HTS token association connected a Hedera account to a specific token before the account received or held it. HashPack, Blade, or Kabila could surface the association as a separate wallet approval when no automatic association covered the asset. Association did not itself supply funds to Bonzo or authorize borrowing; the later contract transaction performed that action. Keeping those two signatures conceptually separate made the resulting position record easier to interpret.
Last updated