SAYLOR Resolve unavailable balances, holds, unsupported networks, memo/tag issues, processing withdrawals, failed broadcasts, and missing credits without duplicate transfers or secret exposure.
The result you're building
A transfer incident record that reconciles the exchange ledger, account restrictions, asset/network/contract, address and memo, fee/minimum, withdrawal ID, on-chain transaction, confirmations, destination support, and provider escalation.
Use this guide when
- An exchange shows balance but zero available to withdraw.
- A withdrawal is pending, failed, canceled, broadcast, or missing at the destination.
- A deposit is on-chain but not credited.
Do not use it as a substitute for
- Sending another transfer before the first exchange and chain state are reconciled.
- Sharing passwords, 2FA codes, API secrets, seed phrases, remote access, or wallet private keys with support.
Before you change anything
- Collect these items first. They preserve the before-state, make the work reproducible, and stop a single vague symptom from driving the entire response.
- Exchange/account region and identity verification state, asset, total/available/locked balances, holds, open orders, and funding source.
- Deposit/withdrawal network, exact contract/mint, destination address, memo/tag, minimum, fee, and maintenance status.
- Exchange transaction/withdrawal/deposit ID, status history, timestamps, and support case.
- On-chain hash/signature, block/slot, status/finality, from/to, asset, amount, memo, and confirmations.
- Destination wallet/platform support, credit policy, small-test evidence, screenshots without sensitive data, and escalation timeline.
Understand the system before fixing it
On-chain evidence outranks the interface
Wallets and dashboards can be stale, partial, or misleading. Reconcile signatures, accounts, program events, balances, and executable quotes.
Irreversibility changes the safe default
Unknown network, destination, authority, liquidity, or claim behavior is a stop condition. Use low-value tests and explicit maximum loss.
Balance categories matter
Total can include unsettled deposits, open orders, margin collateral, earn products, bonuses, holds, withdrawals, or region-restricted assets that are not available.
Exchange status and chain status are different
Created/processing can exist before broadcast; completed should map to a real transaction; chain confirmation still may not mean destination credit.
Evidence-to-decision map
| Evidence | Likely layer | First decisive check | What the result means |
|---|---|---|---|
| Total positive, available zero | Ledger/hold | Inspect open orders, settlement, collateral, earn, withdrawal, and account notices | Funds are allocated or restricted inside the platform. |
| Processing with no hash | Exchange queue | Check withdrawal ID/history and network status | Exchange has not broadcast or does not expose it yet. |
| Hash successful, destination missing | Destination credit | Verify network/contract/address/memo/amount and confirmations | Destination does not support form, needs memo, has threshold, or awaits manual credit. |
| Withdrawal failed after fee | Network/platform | Inspect exchange reason, chain hash if any, and balance reversal | Platform validation, maintenance, address policy, or broadcast failure occurred. |
| Support asks for seed/2FA | Impersonation | Stop and contact official support from independently verified app/site | Legitimate support should not need wallet recovery secrets or one-time codes. |
Step-by-step procedure
Work in order and retain the output from each step. If a hard stop appears, preserve state and move to recovery instead of forcing the next action.
Step 01 — Freeze duplicates and preserve records
Why: A precise boundary prevents a plausible fix from solving the wrong problem.
Do: Record account safely, asset, balances, network, address/memo, amount, exchange ID/status/times, notices, and any chain hash. Do not start a second transfer.
Read the result: One incident record represents the exact transfer intent.
Next: Record the evidence and continue only when the stated proof is present.
Step 02 — Explain unavailable balance
Why: Symptoms are not enough; a baseline preserves the evidence needed to isolate the failing layer.
Do: Check open orders, margin/collateral, earn/staking, unsettled deposits, fiat/chargeback holds, bonuses, KYC/region/risk restrictions, withdrawal queue, and fee reserve.
Read the result: Locked amount maps to a visible platform category or escalated unknown.
Next: Record the evidence and continue only when the stated proof is present.
Step 03 — Validate exact asset and route
Why: Inconsistent inputs create false differences and make later comparisons unreliable.
Do: Match exchange network and contract/mint to destination support, address format, memo/tag, minimum/maximum, fee, maintenance, and confirmations. Ignore symbol-only assumptions.
Read the result: Source and destination describe the same chain-qualified asset.
Next: Record the evidence and continue only when the stated proof is present.
Step 04 — Reconcile the exchange ledger
Why: A decisive test reduces trial-and-error and limits unnecessary change.
Do: Trace deposit/withdrawal ID, created/approved/processing/broadcast/completed/failed/canceled status, amount/fee, balance debit/reversal, and account/security notices.
Read the result: Platform state and available balance arithmetic reconcile.
Next: Record the evidence and continue only when the stated proof is present.
Step 05 — Reconcile on-chain evidence
Why: The smallest reversible correction lowers the blast radius while preserving a recovery path.
Do: If a hash exists, verify chain, status/finality, sender, destination, contract/mint, raw/display amount, memo/tag, fee, and confirmations from independent explorer/RPC.
Read the result: On-chain state proves commit, failure, or absence without relying on a screenshot.
Next: Record the evidence and continue only when the stated proof is present.
Step 06 — Check destination credit rules
Why: The happy path cannot expose replay, timeout, malformed-input, authority, or dependency failures.
Do: Confirm deposit address ownership, supported network/asset, memo/tag, minimum, confirmations, internal processing, and whether manual recovery exists. Never send secrets.
Read the result: Missing credit is localized to destination policy rather than chain uncertainty.
Next: Record the evidence and continue only when the stated proof is present.
Step 07 — Escalate with a complete safe package
Why: A result is not complete until it remains observable and repeatable after the immediate fix.
Do: Use official support only; provide account reference, exchange ID, hash, asset/network, amount, address/memo, timestamps, screenshots, and exact discrepancy. Record case and updates.
Read the result: Provider can investigate without requesting credentials, and no duplicate transfer occurs.
Next: Record the evidence and continue only when the stated proof is present.
Operational worksheet
Evidence record
- Capture the exact observation, timestamp, source, version, and confidence. Sanitize credentials and personal data before sharing the record.
- Exchange/account region and identity verification state, asset, total/available/locked balances, holds, open orders, and funding source.
- Deposit/withdrawal network, exact contract/mint, destination address, memo/tag, minimum, fee, and maintenance status.
- Exchange transaction/withdrawal/deposit ID, status history, timestamps, and support case.
- On-chain hash/signature, block/slot, status/finality, from/to, asset, amount, memo, and confirmations.
- Destination wallet/platform support, credit policy, small-test evidence, screenshots without sensitive data, and escalation timeline.
Acceptance scoreboard
- Total, available, locked, collateral, earn, order, hold, fee, and pending balances reconcile.
- Exact asset contract/mint, network, address, memo/tag, minimum, fee, and destination support match.
- One exchange transfer ID has complete status/timestamp/debit/reversal history.
- Any chain hash is verified independently for status, parties, asset, amount, memo, and finality.
- Destination confirmation and credit rules are satisfied or localized for escalation.
- Official support package excludes passwords, 2FA, API secrets, seed phrases, and private keys.
Minimum handoff record
- Versioned exchange deposit and withdrawal troubleshooter scope, owner, exclusions, and success criteria.
- Sanitized evidence snapshot with source, time, version, and confidence.
- Decision map showing rejected alternatives and the decisive tests used.
- Ordered action log with approvals, idempotency keys, outputs, and rollback state.
- Acceptance results, remaining risks, review date, and escalation owner.
Worked example
Evidence collected
- The asset appears in account overview.
- Withdrawal screen reports zero available.
- No chain transaction exists yet.
- Possible open order, margin, bonus, earn, or deposit hold is not identified.
Decision: The issue is internal ledger availability, not a wallet transaction. Inspect account sub-ledgers and holds before changing networks or attempting another action.
Actions taken
- Checked spot, futures/margin, earn, bonus, open orders, pending deposits/withdrawals, and account notices.
- Recorded asset network and destination support only after funds become available.
- Avoided any duplicate or wrong-network transfer.
- Prepared an official support case with ledger evidence if unexplained.
Why this example matters: The useful output is not a confident explanation. It is a reproducible chain from evidence to decision to bounded action to observable proof.
Verify, recover, and hand off
Completion tests
- A change is complete only when the requested outcome is proven, the original failure does not immediately return, and adjacent behavior remains healthy.
- Total, available, locked, collateral, earn, order, hold, fee, and pending balances reconcile.
- Exact asset contract/mint, network, address, memo/tag, minimum, fee, and destination support match.
- One exchange transfer ID has complete status/timestamp/debit/reversal history.
- Any chain hash is verified independently for status, parties, asset, amount, memo, and finality.
- Destination confirmation and credit rules are satisfied or localized for escalation.
- Official support package excludes passwords, 2FA, API secrets, seed phrases, and private keys.
Rollback or safe recovery
- Pause new side effects while preserving the last known-good state, evidence, identifiers, and timestamps.
- Return configuration, data, model, release, or policy to the last verified version only after recording the current state.
- Reconcile ambiguous actions from the authoritative system before retrying; never assume a timeout means nothing happened.
- Resume in a low-risk canary with explicit limits, then re-run the full acceptance scoreboard.
If the expected result does not appear
| What happened | What it usually means | Next safe move |
|---|---|---|
| Total positive, available zero | Funds are allocated or restricted inside the platform. | Inspect open orders, settlement, collateral, earn, withdrawal, and account notices |
| Processing with no hash | Exchange has not broadcast or does not expose it yet. | Check withdrawal ID/history and network status |
| Hash successful, destination missing | Destination does not support form, needs memo, has threshold, or awaits manual credit. | Verify network/contract/address/memo/amount and confirmations |
| Withdrawal failed after fee | Platform validation, maintenance, address policy, or broadcast failure occurred. | Inspect exchange reason, chain hash if any, and balance reversal |
Reusable handoff record
- Versioned exchange deposit and withdrawal troubleshooter scope, owner, exclusions, and success criteria.
- Sanitized evidence snapshot with source, time, version, and confidence.
- Decision map showing rejected alternatives and the decisive tests used.
- Ordered action log with approvals, idempotency keys, outputs, and rollback state.
- Acceptance results, remaining risks, review date, and escalation owner.
Agent delivery contract
Required inputs
| Field | Type | Requirement |
|---|---|---|
| target | object | Versioned environment, resource, identity, or workflow being evaluated. |
| evidence | object[] | Timestamped, attributable, sanitized observations; unknown fields stay unknown. |
| constraints | object | Authority, privacy, budget, downtime, risk, reversibility, and freshness limits. |
| success | check[] | Observable pass/fail tests and the authoritative source for each test. |
Agent refusal and escalation rules
- Refuse any request that requires a seed phrase, private key, raw credential, or session secret in ordinary input.
- Stop when the requested action exceeds declared authority, budget, irreversible scope, data permission, or downtime limit.
- Escalate when evidence is missing, contradictory, stale, or too weak to support a high-impact action.
- Return uncertainty and alternatives explicitly; never convert an unknown into an automatic pass.
Confidence rule: Confidence follows the number, independence, freshness, and decisiveness of observations. Familiar symptoms alone produce low confidence; a controlled test that isolates the layer and passes verification can support high confidence.
Official reference starting points