Custody transfers
Read the queue, check history and actual accounting result.
Step by step
- Open Transfers. External and Custody are separate tabs and appear only when permitted. Status filters on the server; Search covers only the current page.
- Select a transfer to see the full sender/recipient address, exact amount, hash, UTC dates and recorded observation. Check history reads stored evidence.
- These are historical records, not a fresh network check or a balance. External provider finality does not establish accepted payment; an unknown custody outcome does not release a reservation.
- Available custody actions follow queue prerequisites and current permissions. Backend checks still apply. Nothing signs, relays or recovers automatically. More tools opens the full permitted operation list.
- On a phone, selecting a row moves focus to its details. Back to list restores focus to the selected row.
Local execution and recovery
Local preparation requires separately admitted custody address, owner, book and verified test funding. The original request and principal/fee hold commit first. Only then can the exact request be exported for the independent signer.
Private keys remain in the isolated signer. The console handles public requests and exact signed results. The signed artifact must be stored before relay.
If the original actor is unavailable, a separately authorized human may review version and hash and continue an already signed transfer. This does not allow a new signature, changed amount or release of an unknown operation’s hold.