Does closing the browser cancel an existing Bonzo supplied position?

Closing the browser or disconnecting WalletConnect does not cancel a Bonzo position already recorded by Hedera. The supply claim belongs to the signing account and persists on-chain, independent of the device or session. Reconnect the same HashPack or Kabila account to load it again. A disconnected interface only removes the viewing session; it does not withdraw the asset or stop native supply interest from accruing.

Is HTS token association separate from a Bonzo supply?

An HTS token association is separate from a Bonzo supply because association permits a Hedera account to hold a specific token, while supply moves that held balance into a reserve. An account already holding the token has the needed association. HBAR requires none because it is Hedera's native coin. Any association-related wallet request should reference the same account and token selected for the supply.

Why does the Bonzo supplied amount change after deposit?

Bonzo's supplied amount increases as native supply interest accrues through the reserve, so the displayed claim does not stay fixed at the original deposit. The rate changes with reserve utilization and the market's interest model, but the mechanism updates the asset-denominated position. Separate incentive balances follow their own claim process. Use the supplied token amount, rather than its changing quoted value, when reconciling the position.

Do I need HBAR after supplying a different asset through Bonzo?

Yes, the connected account needs HBAR because Hedera charges network costs in HBAR even when Bonzo supplies USDC or another token. One HBAR contains 100,000,000 tinybars, and the network deducts the charge in tinybars. Keep a working balance outside the supply amount for later state changes. The exact debit belongs to the transaction the wallet presents, so a fixed Bonzo-wide reserve amount does not apply.

Are Bonzo incentive rewards included in the withdrawal?

Liquidity incentives are separate from the asset withdrawn from a Bonzo reserve. Native supply interest appears in the supplied position and travels with the redeemed claim. Incentive tokens, when a market offers them, occupy a different claimable balance and require a claim action through the interface. Closing the supplied position therefore does not replace the reward-claim transaction for any outstanding incentive shown on the dashboard.

Does changing accounts alter the Bonzo position shown?

Changing the selected HashPack or Kabila account changes the account-specific position Bonzo loads. The supplied balance belongs to the Hedera account whose wallet signed the deposit, not to the browser session or device. If the panel appears empty after a switch, reconnect the original signing account and compare its account ID. Repeating the deposit from another account creates a separate position rather than restoring the first one.

What records should I keep after a Bonzo withdrawal?

Keep the Hedera transaction ID, consensus status, consensus timestamp, account ID, asset, and withdrawn amount for a completed Bonzo exit. Those fields distinguish a settled contract call from a wallet prompt or interface message. The updated wallet balance and reduced or closed Supplied row provide the operational cross-check. A transaction ID also lets a mirror-node explorer retrieve the permanent record without access to the wallet's signing key.

Bonzo is a wallet-signed supply, position check, and withdrawal workflow

Bonzo is a wallet-signed path for placing one supported asset into a Hedera lending reserve, confirming the resulting supplied balance, and later withdrawing it. The usable workflow starts with HashPack or Kabila connected to the intended Hedera account, continues through a market row and supply modal, and only finishes when the wallet signature reaches consensus and the Supplied panel updates. A connected interface alone does not move funds. The wallet must authorize the contract call, and the account must retain enough HBAR for network charges. This walkthrough follows that first-position sequence from prerequisites to a clean exit and stays focused on the asset movement the account authorizes.

The short version: Keep enough HBAR outside the supplied amount to authorize the eventual withdrawal from the same account.

A rejected signature leaves no supplied position

A rejected Bonzo supply signature leaves the asset in the wallet and creates no entry in the Supplied panel.

Connecting HashPack or Kabila through WalletConnect only exposes the selected public account to the interface. The actual supply begins when the wallet receives a contract request and displays the asset, amount, account, and network. Rejecting that request, closing the wallet, or letting it expire leaves the starting balance untouched. Bonzo may close its modal before the dashboard has refreshed, so the visible interface state is not the settlement record. Wait for a successful Hedera response, then look for the supplied row before attempting another deposit.

A duplicate attempt before status resolution can create a second deposit if the first action later succeeds. Use the transaction status, wallet debit, and Supplied row as three checks. Agreement across all three turns a wallet prompt into an established position and preserves a clean audit trail for withdrawal.

Set up one account before choosing an asset

Bonzo prerequisites reduce to one funded Hedera account, a compatible wallet session, and an asset the current dashboard lists.

HashPack and Kabila both connect through WalletConnect, including a QR-code path for a phone and account selection for an extension. Choose the account before opening the supply modal. A native Hedera account ID uses three period-separated numeric parts: shard, realm, and account number. Bonzo's contracts and data service also use a 20-byte EVM address. That address renders as 40 hexadecimal digits, or 42 characters when its 0x prefix is included. Hedera mainnet uses EVM chain ID 295, while testnet uses chain ID 296. Those identifiers must describe the same network and account throughout the session.

Keep an HBAR balance outside the intended supply so the account remains ready to authorize its eventual withdrawal.

The wallet session should show one account consistently across Bonzo, WalletConnect, and the signature window. Switching accounts after building the request changes the signer, so reopen the market row and let the interface recalculate the available balance. This reset keeps the public account ID, EVM address, and displayed asset balance aligned before any contract call leaves the wallet.

How should you choose a supply market?

A Bonzo supply market should match the exact asset, network, and account balance you intend to place into one reserve.

The reserve model follows Aave v2's pattern: one market holds one underlying asset, so HBAR enters the HBAR reserve and USDC enters the USDC reserve. Match the ticker with the token identifier shown by your wallet, especially where Hedera Token Service assets and ERC-20 representations coexist. HBAR uses 8 native decimal places, making 1 HBAR equal to 100,000,000 tinybars; an Ethereum transaction value represents the same coin with 18 decimal places in weibars. Enter the amount in display units, then let the wallet translate it. The selected row should name the same token representation the wallet will debit, making the reserve choice observable before signature.

The supply modal and wallet signature

The Bonzo supply modal prepares the action, while the connected wallet authorizes the exact transaction the account will submit to Hedera.

The modal stages the amount; the wallet forms the authorization boundary. Read the connected account, Hedera network, asset symbol, amount, and contract interaction before signing. When the app presents more than one transaction for asset setup, complete each wallet prompt in order and wait for its result. A Hedera transaction valid-duration field cannot exceed 180 seconds, so the wallet must rebuild an expired request for a new signature. Changing the amount or account also requires a fresh request because the signature covers the serialized transaction bytes.

Worked example: every changing input is hypothetical - a HashPack account starts with 1,250 USDC, the supply input is 1,000 USDC, and accrued interest at the confirmation moment is 0 USDC. The wallet signs the 1,000 USDC request for the selected Bonzo market. After consensus, the token balance is 250 USDC and the supplied row begins at 1,000 USDC. The concrete result is 1,000 USDC supplied and 250 USDC left in the wallet, while HBAR pays the separate network charge.

If the wallet shows a different asset or amount, cancel that request and rebuild it from the market row you selected.

How do you confirm the position on-chain?

Hedera confirms a Bonzo position only after recording success and the same account shows the asset under Supplied.

Start with the wallet receipt, then compare it with the dashboard. A Hedera transaction ID binds the payer account to a valid-start timestamp, and the consensus timestamp records seconds plus a nanosecond field with 9-digit precision. HashScan or another Hedera mirror-node explorer can show the status and contract call for that ID. In Bonzo's own account data, the atoken_balance field represents the amount supplied to the reserve. The interface converts that position into the asset's display units. Matching account, asset, amount, and successful status provides four independent facts about the same action.

The supplied balance will diverge from the original deposit as native supply interest accrues. Compare the current position with the original transaction amount without treating a difference as failure. The current token amount and its quoted market value answer different questions, so check the asset-denominated balance when deciding what to withdraw. The Supplied row remains the working record for that later action.

A clean withdrawal from the supplied balance

For a regular user, Bonzo closes a first supply-only position through the Supplied row, a withdrawal amount, a new wallet signature, and a final balance check. The adjacent topic is explained in Bonzo tutorial.

Open the asset from the Supplied section and choose Withdraw. On desktop, the action sits behind the row menu; in HashPack's mobile dApp browser, tapping the asset opens its controls. Enter a partial amount or use the full-balance control, then read the transaction overview before sending the request to the wallet. Available liquidity in that single-asset reserve governs how much the contract can return immediately. After the withdrawal reaches Hedera consensus, the underlying asset returns to the connected account and the supplied balance falls by the redeemed amount.

There are two exit shapes. A partial withdrawal redeems only the selected portion of the supply claim and leaves the remainder accruing. A full withdrawal redeems the displayed claim and reduces that reserve position to 0 after settlement. The current supplied balance determines the redemption amount because native supply interest accrues beyond the original deposit.

Finish by matching the wallet credit, successful Hedera status, and updated Supplied row. If the wallet has settled while the interface still shows the earlier amount, reconnect the same account and refresh its dashboard data. Store the transaction ID with the asset and amount; that record gives the next session a precise endpoint for the completed withdrawal.

Before you start with Bonzo

Does closing the browser cancel an existing Bonzo supplied position?: Closing the browser or disconnecting WalletConnect does not cancel a Bonzo position already recorded by Hedera. The supply claim belongs to the signing account and persists on-chain, independent of the device or session. Reconnect the same HashPack or Kabila account to load it again. A disconnected interface only removes the viewing session; it does not withdraw the asset or stop native supply interest from accruing.
Is HTS token association separate from a Bonzo supply?: An HTS token association is separate from a Bonzo supply because association permits a Hedera account to hold a specific token, while supply moves that held balance into a reserve. An account already holding the token has the needed association. HBAR requires none because it is Hedera's native coin. Any association-related wallet request should reference the same account and token selected for the supply.
Why does the Bonzo supplied amount change after deposit?: Bonzo's supplied amount increases as native supply interest accrues through the reserve, so the displayed claim does not stay fixed at the original deposit. The rate changes with reserve utilization and the market's interest model, but the mechanism updates the asset-denominated position. Separate incentive balances follow their own claim process. Use the supplied token amount, rather than its changing quoted value, when reconciling the position.
Do I need HBAR after supplying a different asset through Bonzo?: Yes, the connected account needs HBAR because Hedera charges network costs in HBAR even when Bonzo supplies USDC or another token. One HBAR contains 100,000,000 tinybars, and the network deducts the charge in tinybars. Keep a working balance outside the supply amount for later state changes. The exact debit belongs to the transaction the wallet presents, so a fixed Bonzo-wide reserve amount does not apply.
Are Bonzo incentive rewards included in the withdrawal?: Liquidity incentives are separate from the asset withdrawn from a Bonzo reserve. Native supply interest appears in the supplied position and travels with the redeemed claim. Incentive tokens, when a market offers them, occupy a different claimable balance and require a claim action through the interface. Closing the supplied position therefore does not replace the reward-claim transaction for any outstanding incentive shown on the dashboard.
Does changing accounts alter the Bonzo position shown?: Changing the selected HashPack or Kabila account changes the account-specific position Bonzo loads. The supplied balance belongs to the Hedera account whose wallet signed the deposit, not to the browser session or device. If the panel appears empty after a switch, reconnect the original signing account and compare its account ID. Repeating the deposit from another account creates a separate position rather than restoring the first one.
What records should I keep after a Bonzo withdrawal?: Keep the Hedera transaction ID, consensus status, consensus timestamp, account ID, asset, and withdrawn amount for a completed Bonzo exit. Those fields distinguish a settled contract call from a wallet prompt or interface message. The updated wallet balance and reduced or closed Supplied row provide the operational cross-check. A transaction ID also lets a mirror-node explorer retrieve the permanent record without access to the wallet's signing key.

Last updated August 2026