Reading your position
Your position joins three records: the BTC still locked on Bitcoin, the debt recorded on Ethereum, and the transactions authorized to connect the two. A balance alone cannot tell you whether an action has finished.
Start with the current collateral
Track the current vault outpoint, written as txid:vout, its amount and whether it remains unspent. After a partial withdrawal or liquidation, the old output has been spent and a new remainder holds the collateral.
The remainder has its own address and event commitments. Follow the position’s parent/child history rather than assuming the original deposit address always represents the loan.
Read debt and coverage together
Ethereum records the debt, collateral credit, health and pending claims. Coverage describes the price/debt states and event horizon for which your signed transactions remain usable.
A loan can have sufficient collateral yet be unable to borrow more because coverage is stale or collateral is reserved for a pending settlement. Conversely, a stored pre-signature alone does not establish coverage once its event horizon has ended. An authorization already published remains usable under its Bitcoin spending conditions; expiry does not revoke it.
| What you see | What it means for the position |
|---|---|
| Funding broadcast | The deposit is not yet a sufficiently confirmed collateral output. |
| Bitcoin funding confirmed | Ethereum credit and coverage verification may still be pending. |
| Active collateral | The recognized position can support actions allowed by its health and coverage. |
| Ethereum transaction included | It is mined; dependent authorizations still wait for finality. |
| Withdrawal or liquidation pending | The source may be reserved or already spent while settlement and accounting finish. |
| Settlement payout awaiting sweep | The allocation exists, but the beneficiary has not yet received a completed payout. |
| Guardian reversal | The contested output followed the prescribed re-vault path; it is not a successful withdrawal. |
| New remainder active | Bitcoin, Ethereum and replacement coverage identify the same new collateral. |
Completion crosses both chains
Zest Protocol requires finalized Ethereum observations and at least six confirmations for Bitcoin-derived actions. Bitcoin locks can impose additional delays before a child transaction or settlement sweep becomes usable.
A receipt, a broadcast notification or an elapsed timer is only one part of that sequence. Check the confirmed transaction and resulting debt/collateral record. If two proposed actions spend the same output, only the canonical spend can define what happened.
When the display and the chain disagree
Record the network, position, transaction IDs and the block heights behind the view. Refreshing an indexer may resolve a stale display; signing another transaction does not resolve an unexplained accounting mismatch.
Verify your position gives the detailed checks. For a pending change, follow partial withdrawals, partial liquidations or closing your position. For unavailable services, see Recovery.