The custody-wallet watch and journal model described by older deposit integrations has been retired. Current deposits use a client’s custody gateway: coins enter the gateway and custody receipts represent them. This reference explains what changed for addresses, token acceptance, records, notifications and positions.
The custody watch and journal are retired. Current gateways use records and custody receipts. Cases and registrar reconciliation are separate operator controls.
Where the deposit address comes from
Older integrations selected a custody-account address and started a deposit watch. That model is retired. Current deposits go to the acting client’s gateway address on the selected network. A provider account address is not a gateway deposit address. Read Wallet deposits and withdrawals before sending coins.
Why the address appears only after its watch exists
The deposit-watch prerequisite and its start route are retired. Current deposit instructions depend on the client’s gateway being available in indexed records. Starting an old watch does not make an address valid for gateway deposits, and the former pre-watch credit rule no longer applies.
Which tokens are accepted
The former watch and external-token acceptance settings are retired. Current acceptance comes from the gateway’s enabled coin and receipt configuration. A direct deposit of an unsupported coin fails. A plain transfer of an unsupported coin is handled through the gateway’s unsupported-transfer records and their permitted decisions. Check the gateway’s supported coins before transferring.
How a transfer is credited exactly once
The durable watch and journal-credit mechanism is retired. Current gateway processing uses its deposit records and available coins to protect receipt minting from repeated processing. Use the gateway record and its history to follow the result. The old journal identifier and notification-once contract do not describe that result.
Wait for the indexed block
The former indexed-watch step is retired. Current reads show indexed gateway deposit records and their stage history. Wait for the actual record to appear rather than assuming the old watch cursor, polling interval or journal compensation rule still applies.
Confirm the wallet still belongs to the investor
The former watch’s custody-reset credit rule is retired. Current gateways belong to a client identity on a network and follow the current wallet-recovery model. Use the gateway of the client you are acting as. Reset-bound withdrawal-destination proofs remain a separate control. They do not establish a deposit watch.
Screen the transfer
The former universal spendable-or-held screening rule is retired. Current gateway screening checks the transfer’s source and permits only the decisions available at its stage. Custody acceptance is a separate step. The provider alone does not determine that every incoming deposit must wait for an operator.
Credit the spendable or the held balance
The former spendable and held journal credits are retired. A current deposit mints custody receipts. Quarantine, mint refusal and awaiting custody describe different stages, with different permitted actions. Receipts held while custody acceptance is pending become usable through that acceptance flow. These stages are not renamed journal balances.
Reversal after a chain reorganisation or a return
The former journal compensation and webhook-revision promises are retired. A gateway return is handled through its actual deposit record and permitted transitions. A chain reorganisation does not, by itself, promise an automatic receipt rollback, journal compensation or replacement retraction notification.
Funds that leave a deposit wallet
The old operator-movement attribution rule is retired. An unexplained debit must be investigated using actual transactions, gateway records and escrow or reserve evidence. There is no replacement movement book that guarantees an investor’s former journal position remains unchanged.
Deposit lifecycle webhook events
The former custody deposit lifecycle events are retired. Their old payload and revision rules are not current subscription instructions. Read current gateway records and history for deposit stages, and consult the webhook catalogue for events that remain available. There is no automatic one-to-one replacement for each retired event.
Positions: spendable and held
The custody-journal spendable and held position reads are retired. Current receipt holdings and gateway records answer holdings and stage questions. They do not reproduce the old position schema, pagination or attribution of funds to custodial locations.
Operator movements
The old operator-movements read and its custody movement event are retired. Current transaction and gateway record evidence can help an investigation, but it is not a replacement report of custodial sweeps or reallocations.
The custody journal is the source
The custody-operations journal and its daily reconciliation are retired. Current custody evidence consists of receipts, gateway records and escrow or reserve readings. The registrar break register and reserve check remain separate controls. Retained platform ledger data does not recreate the former custody journal.