Custody Coverage

Overview

Coverage answers what the custodian can actually safeguard and administer. Support may differ for native coins, token contracts, NFTs, staking, governance, forks, airdrops, smart-contract interactions, and recovery from unsupported transfers. An asset name without its network is often incomplete.

The term should not be confused with insurance coverage. A custodian may technically support an asset while excluding certain losses, regions, client types, or transaction functions from its insurance or contract. Sub-custodians and technology providers can also limit the practical scope.

Clients should maintain a coverage matrix with asset identifiers, networks, deposit and withdrawal capability, storage tier, confirmation rules, limits, service location, and exceptions. Changes need controlled communication because sending an otherwise familiar token over an unsupported route can delay or prevent crediting. Coverage should match both current holdings and planned operations.

Custody Coverage should be distinguished from investment ownership and from a software interface. For example, a provider may display an asset balance while holding pooled assets through another custodian; operations must verify contractual rights, segregation, withdrawal capability, and external evidence rather than rely on the screen alone.

Custody Coverage works through controlled onboarding, asset receipt, internal attribution, storage-tier assignment, authorization, signing or provider instruction, monitoring, withdrawal, reconciliation, reporting, and return or migration. For Custody Coverage, each handoff needs stable identifiers and an authoritative record of who approved and executed it.

For Custody Coverage, risks include key compromise, insider abuse, commingling, inaccurate books, unsupported tokens, provider insolvency, sub-custodian failure, blocked withdrawals, lost recovery material, and ambiguous liability. For Custody Coverage, controls should combine least privilege, separation of duties, verified destinations, asset segregation, limits, monitoring, and continuity tests.