Custody Factory: Segregated Asset Control on a Shared Network
Category:
Factory
Date:
Creator
Benz Martheen
Asset managers have a structural tension to manage: they need to participate in shared market infrastructure, but they also need cryptographic certainty that their clients' assets are segregated and under their exclusive control.
Segregation by construction, not by policy
Custody Factory contracts instantiate a new, isolated contract for each custody relationship, even though every instance is built from the same underlying template. Segregation isn't a policy an asset manager promises to follow — it's a property of the contract structure itself.
Shared infrastructure, independent control
The efficiency gain comes from the fact that the custody logic itself only needs to be built and audited once. Every new client relationship reuses that validated logic while still getting a fully independent instance.
Operational implications
For a custodian scaling client relationships, onboarding becomes an act of instantiating a new contract from an already-audited template — a process that can happen in a fraction of the time traditional custody onboarding takes.
Regulatory reporting made simpler
Because every custody instance shares the same underlying data structure, generating regulator-facing reports across a large book of clients becomes a matter of aggregation rather than reconciling formats from disparate legacy systems.
