Bonzo troubleshooting is a wallet reconnection workflow for failed transactions

Last updated: 2026-07-23

Bonzo troubleshooting is a wallet-session reset for failed Hedera transactions: disconnect Bonzo Finance, remove its WalletConnect session in HashPack or Kabila, close other Hedera dApp tabs, restart the browser or wallet and reconnect the intended mainnet account. Then check HBAR for fees, device time and the on-chain receipt before retrying once. Reconnection repairs stale interface state; it does not reverse a settled transaction or bypass a paused Bonzo Lend market.

Reset the wallet session from end to end

A complete Bonzo Finance reset removes the dApp-side connection and wallet-side session before the browser or mobile wallet starts again.

1. Open Bonzo Finance and disconnect the current wallet.
2. In HashPack or Kabila, remove Bonzo from active dApp connections.
3. Close Bonzo, SaucerSwap and other Hedera dApp tabs.
4. Clear Bonzo site data on desktop, then quit the browser; on mobile, force-close the wallet.
5. Reopen the wallet, select the intended Hedera mainnet account and unlock it.
6. Return to Bonzo, approve a new WalletConnect session and inspect the account shown before initiating a transaction.

WalletConnect keeps pairing and session state outside the visible Bonzo page, so a page refresh alone leaves the old account mapping alive. An inactive pairing expires after 5 minutes, while an active pairing has a 30-day expiry. Deleting the connection from both sides forces a new session proposal, account choice and permission set. Desktop users can approve a HashPack or Kabila extension prompt; a mobile wallet can scan a fresh QR code or enter the pairing string. The account visible in Bonzo after reconnection must match the account prepared in the wallet. That final comparison catches stale account events before a transaction is built and sent for signature.

Start from Bonzo’s dated protocol status

Bonzo Lend availability sets the boundary: wallet reconnection repairs a session fault, while a protocol pause prevents lending transactions from executing.

The latest published Bonzo Finance update, dated July 16, 2026, said that Bonzo Lend markets remained paused. The pause followed an oracle verification failure on July 11, 2026 and the update described a separate redemption mechanism under development. Bonzo Points was also paused, while an earlier report said Bonzo Vaults, Bonzo Bridge and single-sided $BONZO/$XBONZO staking continued operating. Treat those products as separate paths. A successful wallet handshake therefore does not prove that a Bonzo Lend supply, borrow, repay or withdrawal action is available.

The dated pause matters more than a clean connection icon. Before any retry, confirm that the relevant Bonzo product reports available service; a green wallet badge describes session state, not Bonzo Lend market execution.

Separate connection failures from ledger failures

From a timing perspective, Bonzo troubleshooting works fastest when the missing wallet prompt, Hedera precheck response and final smart-contract receipt stay three separate diagnostic stages.

A missing prompt points to WalletConnect, a locked wallet or an outdated session. A Hedera precheck stops a transaction before consensus: OK is response code 0, INVALID_SIGNATURE is 7 and INSUFFICIENT_PAYER_BALANCE is 10. A consensus receipt means the network accepted the submission and then returned its final status. CONTRACT_REVERT_EXECUTED, code 33, means the Ethereum Virtual Machine reached a contract rule that rejected the requested state change. Reconnecting helps the first category. It does not change a precheck requirement or the contract condition recorded in the receipt (see also Using Bonzo ).

Record the exact status name before changing anything. The label decides whether to reset WalletConnect, fund HBAR or stop retrying Bonzo Lend.

A user-rejected wallet prompt creates no signed submission, so HashScan has no transaction to display. By contrast, a signed request can leave the browser before its success callback returns. That distinction explains why checking HashScan precedes every retry.

Match the account, network and signing key

On those terms, Bonzo Finance must build the request for the same Hedera mainnet account that HashPack or Kabila presents to WalletConnect for signing.

Hedera mainnet uses EVM chain ID 295; testnet uses 296 and previewnet uses 297. Those identifiers prevent a mainnet Bonzo action from being signed as a test transaction. A numeric Hedera account ID contains 3 components in shard.realm.number form, while an EVM address is 20 bytes and displays as 42 characters including its prefix. Compare the account in Bonzo with the selected wallet account, not merely the shortened address. Hedera supports Ed25519 and ECDSA over secp256k1 account keys, but the wallet handles that signing detail. If you switched accounts after loading the page, disconnect and create a new session so WalletConnect receives the account change.

Correct clock drift before another signature

Device time matters because every Hedera transaction carries a valid-start timestamp and a limited validity duration before the network rejects it.

A Hedera transaction validity duration cannot exceed 180 seconds. TRANSACTION_EXPIRED is response code 4, INVALID_TRANSACTION_START is 5 and INVALID_TRANSACTION_DURATION is 6. A clock set ahead creates a start time that consensus has not reached; a clock set behind consumes the validity window before submission. Enable automatic time and time-zone sync, close the stale approval and rebuild the transaction after synchronisation. Discard the old wallet prompt after fixing the clock, because its timestamp belongs to the earlier request. A fresh Bonzo request should present a new wallet approval, not revive the previous one.

After synchronising the clock, reopen Bonzo Finance and generate a new approval. The 180-second ceiling concerns transaction validity, not a promised interface response time or WalletConnect display timeout.

Reserve HBAR for fees and smart-contract gas

Every Bonzo contract action needs spendable HBAR in the fee-paying Hedera account, even when the supplied or withdrawn asset is another token.

One HBAR equals 100 000 000 tinybars and the native unit has 8 decimal places. Hedera smart-contract cost combines a base transaction fee, calldata gas and execution gas, so the wallet quote changes with the function and computation. INSUFFICIENT_TX_FEE is response code 9, while INSUFFICIENT_PAYER_BALANCE is 10. Leave a fee buffer instead of entering the wallet’s entire HBAR balance into a Bonzo action. Check that the fee-payer account in the approval matches the reconnected account. A reconnection cannot fund the payer account, and switching accounts moves the fee check to a different HBAR balance.

Read contract reverts as protocol responses

A Bonzo contract revert confirms that signing and submission worked, but the requested function failed a rule inside the executing contract.

Hedera labels that outcome CONTRACT_REVERT_EXECUTED, response code 33; INSUFFICIENT_GAS is code 30. A Bonzo Lend pause, insufficient market liquidity, an amount beyond the available balance or a position constraint all belong in this layer. A reward claim can also fail for a contract-side condition rather than a broken wallet session. Check the receipt and interface state before interpreting the message. If the same code 33 returns after one clean reconnection, another reconnect repeats the same request against the same rule.

For a confirmed revert, preserve the transaction ID and charged fee shown by HashScan; both identify the code 33 execution. Then check Bonzo Lend availability and the requested amount before another approval. The same receipt is more useful than another browser reset.

Verify the transaction in HashScan before retrying

HashScan separates a missing submission from a completed Hedera transaction by showing the transaction ID, consensus timestamp, result and charged fee.

Copy the transaction ID from HashPack, Kabila or Bonzo and search it on the correct Hedera network. HashScan reads Hedera Mirror Node data, giving the ledger result an independent view outside the dApp. A Hedera timestamp uses seconds plus up to 9 fractional digits, while the transaction ID binds the payer account to a valid-start timestamp. If HashScan shows success, refresh the Bonzo dashboard and let interface state catch up. Treat that ledger result as completed and limit the next action to an interface refresh. If HashScan shows a named failure, route that status through the earlier categories. If no transaction appears, return to the wallet-session path and rebuild through WalletConnect.

When should you retry a Bonzo transaction?

A retry is appropriate only after the previous transaction status is known and the original failure belongs to a corrected connection, timing or balance condition.

Use this five-condition decision checklist:

• Session: Bonzo shows the newly approved HashPack or Kabila account.
• Network: the wallet targets Hedera mainnet and chain ID 295.
• Time: automatic clock synchronisation is active and the old prompt is closed.
• Funds: the payer retains HBAR beyond the amount being transacted.
• Status: HashScan shows no prior success and Bonzo Lend is available for the requested action.

Retry once after all 5 conditions hold. Repeated approvals create ambiguity when the first request already reached consensus, especially during a delayed interface refresh. Use the single new HashScan transaction ID as the record.

Escalate with a reproducible transaction record

Once that is set, Bonzo Finance support can diagnose a failed transaction faster when the report preserves network facts and the exact wallet path without repeated submissions.

Capture 6 items: Hedera account ID, transaction ID, wallet name, desktop or mobile path, timestamp and full status text. Note whether the prompt never appeared, the wallet rejected signing, precheck failed or the contract returned a receipt. Include the Bonzo product and action, such as a Bonzo Lend withdrawal through HashPack. If no transaction ID exists, state that clearly and identify the button, deep link or QR handoff that stopped. The official Bonzo Finance support channel can compare that record with service status. The 6-item record gives support a reproducible HashPack-to-Bonzo Finance path.

Quick answers