Juice finance lets a borrower trace how WETH collateral, USDB debt and strategy positions change after each confirmed action on Blast

The Starting Record for One Borrow

The trace begins with four account values: deposited WETH, outstanding USDB debt, displayed remaining capacity and health factor. Record them before opening a wallet prompt. Together they show the collateral already posted, the amount owed, the room under the current limit and the account's liquidation buffer.

Wallet holdings are a separate record. Assets held by a JuiceAccount do not need to appear in the connected wallet's token list.

A transaction hash identifies an attempted state change, while its receipt shows whether the network executed it successfully. The updated account then supplies the economic evidence. A deposit should affect collateral, a borrow should affect debt and account USDB and a vault deposit should create or enlarge the corresponding strategy position.

This baseline keeps unrelated movements out of the comparison. Changes in the wallet, the JuiceAccount and a strategy position belong to different records even when one action connects them. Using the same account and the same action boundary makes a mismatch easier to locate.

What Must Match Before You Continue?

A reader should continue only when the network, wallet, JuiceAccount, asset and proposed amount all describe the same action. A correct token symbol alone is insufficient because balances and permissions belong to specific contracts and accounts on a particular network. The live account view must also show enough remaining USDB capacity for the intended borrow.

• The wallet is connected to Blast and shows the intended address.
• The selected JuiceAccount belongs to that wallet.
• The WETH balance exists on Blast rather than another network.
• The wallet has ETH available for transaction fees.
• The proposed USDB amount remains below the displayed borrowing capacity.

Remaining capacity can change before submission because collateral value, debt and protocol risk parameters affect the limit. Re-read it after any deposit or repayment. If the displayed figure no longer supports the proposed amount, changing the amount before signing is safer than treating an earlier screenshot as a standing authorization.

Separate Approval and Deposit Evidence

Approval and deposit are separate transactions with different results. An ERC-20 approval changes a spending allowance; it does not transfer WETH into collateral. A successful approval receipt therefore proves permission was set, but the starting collateral record should remain unchanged until a deposit transaction executes.

After the deposit confirms, compare the JuiceAccount's collateral with the baseline and the submitted WETH amount. A successful receipt paired with no expected collateral change calls for checking the selected account and transaction details. Do not borrow merely because the interface now exposes a button or an earlier approval succeeded.

The Borrowed USDB Record

Borrowing creates USDB debt and places the borrowed balance inside the protocol-managed JuiceAccount. It does not need to raise the connected wallet's USDB balance. Compare the requested amount with the debt change, account USDB and remaining capacity after confirmation. Small timing differences in accrued debt require the account's current accounting record, not a subtraction based only on the wallet request. The borrow is ready for a later action only when those records describe the same confirmed loan.

Debt Evidence Beyond the Token Balance

Debt evidence needs the same account and observation point as the collateral record. The Manager compares account equity, built from collateral, investment and credit values, with the loan value to determine whether an account is liquidatable. A wallet token balance cannot reproduce that cross-margin calculation because strategy assets and account credit may also affect equity.

The health factor gives the account-level consequence of a change, but it does not identify the transaction responsible for that change. Use the receipt and individual balances to locate the action, then use health and remaining capacity to decide whether another commitment is permitted. An unexpected health movement may reflect asset valuation, debt accrual or a strategy position rather than a missing token transfer.

View image file

Vault Placement as a Separate State

Vault placement follows a confirmed borrow and requires another transaction. Its evidence belongs in the strategy position, not in the original collateral record. The JuiceAccount's available USDB should change as funds enter the selected registered strategy, while the loan remains outstanding. A vault receipt does not repay debt or release WETH collateral.

The selected strategy may have a displayed deposit fee, asset exposure and external-protocol risk. Read the fee shown at the time of the action rather than carrying forward an old value. The transaction record, resulting position and account health should all refer to the same placement before any further change is made.

What Does a Complete Match Look Like?

A complete match has two aligned layers: a successful transaction receipt and the expected account delta. For a deposit, collateral rises without creating debt. For a borrow, debt and account USDB reflect the loan. For a vault placement, the strategy position appears while the debt remains visible.

An interface can refresh later than the transaction receipt, so a brief display mismatch does not establish a failed transaction. Compare the receipt with the relevant contract and account state, then refresh the account view. If the state is correct but the display remains stale, submitting the next action risks relying on an incomplete view.

The recorded state, not an enabled button, determines whether the trace is complete.

A Bounded Mismatch Before Retry

In this hypothetical example, the changing inputs are the intended 0.42 WETH deposit, a USDB borrow below the displayed capacity, the capacity reading and each wallet gas estimate. The reader records zero new collateral and zero new debt before beginning, then submits only the WETH approval.

The expected state after approval is a successful receipt and enough allowance for 0.42 WETH, with collateral and debt unchanged. The next expected state would require a separate deposit receipt followed by a 0.42 WETH increase in the account's collateral record.

The observed state shows a successful approval and updated allowance, but no deposit hash and no collateral increase. This is a bounded failure between permission and transfer. No borrow has been submitted, so the proposed loan can still be changed or abandoned. The approval transaction fee has already been spent, and a later gas estimate may differ.

The retry starts at the deposit rather than repeating the successful approval automatically. After confirming the network, JuiceAccount and amount, the reader submits the deposit and waits for its receipt. The retry reaches a concrete result when collateral rises by 0.42 WETH while debt remains unchanged. Remaining capacity and transaction costs are then read again before any borrow decision.

View image file

Cost Inputs Along the Trace

Cost along the trace comes from separate inputs rather than one fixed number. Each approval, deposit, borrow and vault action can require a Blast transaction fee. An open loan accrues borrowing interest, while a selected strategy may have a displayed deposit fee. Liquidation costs belong to a different failure state and should not be mixed into a normal completion record.

View image file

The lending pool recomputes its borrow and liquidity indices before each action to account for accrued debt and yield. A later debt reading can therefore differ from the initial USDB amount without another borrow transaction. Record the observation time or block context when comparing debt, then separate that accrual from wallet gas and strategy-specific charges.

Repayment and Exit Records

A full exit follows the account's dependencies in reverse: leave open vault positions, make enough USDB available for repayment, clear the debt and withdraw collateral. Each action needs its own receipt and resulting state. A single successful withdrawal cannot prove the entire sequence completed.

A vault withdrawal confirms only the strategy leg. The returned assets must appear in the JuiceAccount before they can support repayment. If the available USDB does not cover the recorded debt, the account remains open and its collateral cannot be treated as fully released.

After debt reaches zero, excess USDB in the JuiceAccount and WETH collateral in the Manager are separate balances with separate exit actions. Claiming excess USDB changes the wallet and account records, while collateral withdrawal changes the Manager's collateral record. Both outcomes should be compared with their own starting values.

Final evidence consists of zero debt, no intended vault position and confirmed transfers of the assets meant to leave the account. Compared with leaving a leveraged strategy open, a verified full exit requires more than a vault withdrawal: it ends only when repayment and collateral withdrawal have both reached their expected states.