The former custody-wallet deposit and withdrawal operations have been retired. Current wallet deposits and withdrawals use a client’s custody gateway and its custody receipts. Destination control proofs remain available, but proving an address does not make it an approved gateway payout address.
The custody watch and journal are retired. Current gateways use records and custody receipts. Cases and registrar reconciliation are separate operator controls.
A deposit and a withdrawal are separate records
The former custody-wallet deposit and withdrawal records are retired. Current gateway deposits and withdrawal requests have stable identifiers and stage histories. Use the identifiers returned by the current records API. The old deposit identifier formula and spendable or held postings no longer describe gateway evidence. Custodial deposits and positions maps the retired addresses, watches, journals and positions to their current gateway equivalents.
How a deposit becomes spendable
The old journal deposit state table is retired. Current deposits mint custody receipts, with stage-specific screening and acceptance. Receipts awaiting custody acceptance may remain held until that flow completes. Read the current record rather than applying a provider-wide rule to every deposit.
An operator decides a held deposit
The old held-deposit review and transition routes are retired. An operator now reads the gateway deposit and uses only the decisions allowed by its stage and signer roles. Where the add-on requires checker approval, that approval remains necessary. There is no generic release, return or refusal action that applies to every hold.
A destination is proved, then cleared
Address-control proofs and operator review remain available even though the legacy withdrawal workflow is retired. Propose a destination, sign its issued message, submit the proof, and wait for the required operator review. The operator can clear or refuse it. The participant can revoke it. A cleared destination proves and reviews address control, but is not automatically an approved gateway payout address. See Withdrawal destination review and Wallet deposits and withdrawals.
A clearance belongs to one custody reset
The retained destination proof binds the organisation, participant, network, address, custody reset epoch and expiry. A proof that no longer matches that binding is refused. This protects the current proof list. It does not restart a retired deposit watch or authorise a new gateway payout address.
Requesting a withdrawal holds the amount and the fees
The old journal withdrawal request, limits and retry-key contract are retired. A current gateway request locks custody receipts under its current terms. Review the gateway’s amount and fee quote before submitting. The former held-balance errors and journal policy limits are not gateway request rules.
A withdrawal waits out its cancel window
The former journal cancellation window and transition route are retired. Current cancellation depends on the gateway request’s stage and configured cancellation setting. The current return flow releases the receipts when permitted. Do not assume every request waits before payment or can always be cancelled.
A payout settles only on the exact transfer
The former durable payout lifecycle is retired. In the current gateway, claiming a withdrawal pays coins and burns receipts atomically. Follow the actual request stage and gateway record history to distinguish a pending request, a claimable payment and a settled withdrawal.
A payout the platform cannot prove is parked
The old parked-payout resolver is retired. Current gateway requests use their own stages, evidence and role-gated claim or return decisions. An uncertain old payout does not map automatically to a gateway stage, and there is no replacement generic consume-or-release action.
What a withdrawal costs and how the fees are booked
The former journal fee schedule and postings are retired. Gateway withdrawal fees use the gateway’s current terms: a fee can be deducted or recorded as owed. Client and service gas obligations are separate. Review the current quote. Neither fees nor network charges are universally zero.
How the fees are quoted
The old fee-quote endpoint and fixed gas estimate are retired. The current gateway quote uses its actual terms and network recharge ceiling. If the interface cannot price a fee, resolve that condition before submitting. A gateway quote is not a renamed legacy journal quote.
How the fees are charged
The former journal hold for custody fees is retired. Current requests lock receipts and apply the gateway’s fee mode. A deducted fee reduces the value paid, while an accounting-only fee is recorded as owed. Consult the current network quote rather than relying on the old claim that the investor’s custody balance never pays gas.
How the fees are booked
The old fee-account posting table is retired. Current gateway fee-accrued or fee-owed records and reconciliation provide evidence for gateway fees. They are not aliases for the old journal outcomes or fee-account balances.
Who sees what
The old route and role inventory is retired. Current gateway reads are client or organisation scoped, and transitions require the appropriate role and stage. Withdrawal proofs retain their participant and operator checks. Generic organisation Cases remain available to owners and platform administrators even when custody operations are off.
Related pages
The legacy workflows on this page are migration references. Use Custody gateway for the current deposit and withdrawal model, Wallet deposits and withdrawals for client actions, Custody settings for Providers and Cases, and Custody reconciliation for break and destination review. Custody Provider explains signing responsibilities. Maker-checker explains required approvals.