Custody vs. Custodianship

Notes

A party may have custody without custodianship — a software process holds keys but owes no duties. A party may have custodianship without sole custody — a qualified custodian may rely on sub-custodians, infrastructure providers, or technology vendors who hold portions of the operational stack. The keys are where the asset can be moved; the duties are where the asset belongs. The distinction is foundational in trust and banking law, where the qualified custodian framework under the Investment Advisers Act and the segregation requirements under the Customer Protection Rule attach to the office, not merely to the holding.^{1 2} The OCC's interpretive guidance on cryptocurrency custody by national banks turns on the same point: a bank may hold cryptographic keys for a customer because that activity is the modern form of safekeeping — the office of custodianship — not because possession of keys is itself the regulated activity.³

Tokenized settlement infrastructure complicates the distinction because operational custody is distributed across systems that were not designed to be custodians. A multi-signature scheme, a smart contract escrow, a validator set, a bridge — each holds a portion of the operational ability to transfer. The assessment question is not whether the keys are secure; it is whether custodianship has been clearly assigned, the duties are owed by an identifiable party, and the operational architecture supports the discharge of those duties under stress. Custody can be engineered. Custodianship must be owed.