Custodian

Overview

Custodian is an entity or service responsible for safeguarding assets, private keys, or transaction authority on behalf of another party under an agreed legal and operational arrangement. Custody must be evaluated through technical control, legal responsibility, account structure, operational capability, and customer rights. Possession of keys is important, but it is not the only measure of ownership or asset protection.

A custodian is not defined only by possessing a private key; legal responsibility, account structure, control rights, and service terms also matter. It should be distinguished from Proof of Control, Proof of Reserves, and Qualified Custodian. These concepts may interact in one workflow, but they identify different control points, records, or security assumptions.

Operationally, due diligence covers licensing or status where relevant, key architecture, segregation, governance, insurance, sub-custodians, withdrawals, reporting, recovery, and insolvency treatment. A production implementation should preserve the applicable blockchain network, asset or contract identifier, source and destination ownership, policy version, responsible roles, timestamps, transaction identifiers, and evidence used to authorize or reconcile the action. Exceptions should be visible in an operational queue rather than silently corrected.

The principal risk is that cyberattack, fraud, operational failure, legal seizure, insolvency, or unclear ownership can prevent customers from accessing assets. Teams should test normal and exceptional paths, including delayed confirmations, reorgs, unavailable custodians, signing-device failure, stale permissions, incorrect network selection, fee spikes, duplicate requests, compromised user interfaces, and incomplete recovery data. High-value actions should be independently reviewed before execution.

For governance and audit, document the exact meaning of Custodian in the relevant wallet, custody platform, smart contract, or internal ledger. Confirm who can create, change, approve, pause, reverse, or recover the associated configuration. Monitoring should cover privileged access, policy changes, address and key lifecycle events, balance movements, failed transactions, reconciliation differences, and unresolved customer claims. This converts the term from a product label into a testable operational control.