Keep the original attempt identifiable
- Save the error and transaction reference
Record the complete message, network, wallet and transaction digest if one was supplied. Do not replace the error with a summary such as insufficient balance unless the wallet actually says that. A total SUI balance does not identify the specific object version selected by the proposed operation.
- Check whether the transaction has an execution result
The Sui lifecycle documentation describes looking up an existing transaction by digest. A finalized transaction can have failed execution, so read the result rather than treating any returned record as a successful transfer. If a lookup is empty, the documentation notes that the queried node might not yet know the transaction.
- Compare the established payment with the instruction
If execution evidence exists, check the intended SUI movement, amount and destination. Only then connect that transfer to the exchange record. An object reservation error on a later attempt does not by itself establish the outcome of an earlier payment or the state of its ETH payout.
Different observations need different explanations
| Observation | What to investigate | Conclusion to avoid |
|---|---|---|
| Stale object version reported | The current object reference and prior activity | All visible SUI has disappeared |
| Object reserved for another transaction | The referenced existing attempt | The ETH recipient caused the error |
| Equivocation reported | Conflicting owned-object use and wallet guidance | Every reservation error has the same recovery time |
| A finalized failed transaction found | Its actual execution status | A returned record proves exchange funding |
The balance and the selected object version answer different questions
Suiโs object-versioning reference explains that an object has an ID and version, and a change produces a new version. A transaction referring to an outdated version can be rejected. A walletโs headline balance does not tell you whether an application constructed its payment using the current reference. This is a transaction-preparation question, not automatically a shortage of coins.
The epochs reference also distinguishes reservations and conflicting owned-object transactions. Depending on the circumstances, a version may be reserved or objects may become equivocated until an epoch transition. Do not apply an old forum answer about one error to every similar-looking message. Use the exact observed error and the current walletโs explanation of that attempt.
Checks before allowing another payment attempt
- Has the earlier attempt been resolved?
- Do not repeatedly create different transactions against the same unresolved owned objects merely to see which one works. Ask the responsible wallet to establish the existing state. This article does not prescribe unlocking tools, new signatures or a manual transaction reconstruction.
- Is support investigating the Sui input or Ethereum output?
- Label the unresolved side. Provide the Sui digest, result and payment details for an input question; provide the separate exchange and receiving record for an output question. Keeping the two sides distinct prevents a preparation error from being described as a confirmed payment awaiting ETH.
- Are you assuming the whole wallet is affected?
- An error naming a specific object does not describe every holding without further evidence. Likewise, visible funds do not prove the proposed operation can use its chosen inputs. Obtain a precise explanation before changing an amount or treating additional funding as the remedy.
Sui object and payment questions
- Does a stale object-version error mean the visible SUI balance is gone?
- No. Resolve the selected object reference and existing transaction state; the headline balance alone does not diagnose that error.
- Does finding a finalized transaction prove successful payment?
- No. Sui documents finalized transactions with failed execution as well. Read the actual result.
- Do all object reservation errors require the same wait?
- No. Reservation, stale references and equivocation need their specific observed state checked.
- Should I create several competing payments to test the wallet?
- No. Establish the original attempt before authorizing a different transaction against unresolved objects.
Primary Sui documentation
- Sui object IDs and current versions
- Sui epochs: reservations and equivocation
- Sui lifecycle: lookup by digest and execution result
Reviewed: