What is crypto custody? A guide to digital asset custody

Crypto custody is the safekeeping of the private keys that authorize transactions. So, it is not storage of the assets themselves. Instead, a digital asset custodian holds and manages those keys for a client, then layers signing controls, asset segregation and reporting on top. Custody models differ by who holds the keys and how those keys are stored. A lost key is usually unrecoverable, which is what makes the choice of model consequential.

A Bitcoin never leaves the blockchain. It sits in a public ledger entry that anyone can read, and nothing physical moves when the coin changes hands. What changes is who can sign for it. Crypto custody is the practice of protecting that signing authority.

In crypto, custody means control over the private keys that authorize transactions on a blockchain. The asset never moves off the network. What is being safeguarded is the cryptographic ability to sign a transfer, plus the records that establish whose authority that is.

Ownership on a public blockchain is not a name on a register. It is the capacity to produce a valid signature for a given address. Anyone who can produce that signature can move the balance, and anyone who cannot is locked out regardless of what they paid or what a contract says.

European rules define the service in exactly these terms. Under the MiCA rulebook, custody covers the safekeeping of crypto-assets or of the means of access to them, where applicable in the form of private cryptographic keys. The phrase "means of access" is the whole point.

Traditional custody protects a registered instrument and the ownership record behind it. Crypto custody protects the ability to sign. A traditional custodian can usually reissue a lost certificate or correct a mistaken entry, while a completed blockchain transfer is final. So, an unrecoverable key has no comparable remedy.

US bank regulators treat the two as related rather than identical. In OCC Interpretive Letter 1170, holding cryptographic keys for customers is described as a modern form of the safekeeping banks have always performed. Investment adviser rules take a similar line, with the SEC Custody Rule guidance defining custody as holding client assets or having the authority to obtain them.

The differences show up in risk rather than definition. Settlement finality removes the reversal and recourse mechanisms that traditional custody quietly relies on, which pushes the security burden onto key management.

In practice, digital asset custody is the same as crypto custody. Both terms describe safeguarding the keys that control blockchain-based holdings, and providers use them interchangeably. Digital asset custody can be evaluated as the broader label.

Three mechanics sit underneath every custody model, and every later comparison depends on them.

• Public key: Derived from the private key and used to generate a receiving address. It can be shared freely, and it reveals nothing that allows spending.
• Private key: The secret value that produces valid signatures for that address. Holding it is what holding the asset means in operational terms.
• Signature: A cryptographic proof, generated with the private key, that a specific transaction was authorized by the key holder.

The signature is doing more work than it appears to. Under the NIST digital signature standard, a digital signature authenticates the identity of the signatory and detects any unauthorized modification of the signed data. Once broadcast, that signed instruction is what the network executes.

This is also why later distinctions become meaningful. Cold storage is about where the private key lives, while multisig and multi-party computation are about how signing authority is divided.

A digital asset custodian is a service that stores and manages private keys on a client's behalf. Storage is only the starting point. The role also covers executing and authorizing transactions, controlling who may approve them, keeping client holdings separate from the provider's own assets, and reporting positions back to the client.

For digital asset custodians, MiCA Article 75 requires a documented custody policy, a register of positions opened in each client's name, prompt recording of every movement, periodic statements, and clear segregation of client assets. ESMA guidance adds that a provider must be able to return the same type of asset it holds, on request.

None of this makes a custodian a vault. It makes a custodian an operator of controlled signing, with an audit trail attached.

There is no password reset for a private key. If the key and its backup are gone, the balance stays visible on the chain and permanently out of reach, which is the single largest behavioral difference between crypto and a bank account.

The scale is measurable in two directions. Industry analysts estimate that somewhere between 2.3 million and 4 million Bitcoin are permanently inaccessible, largely through lost keys, discarded hardware and forgotten backups.

The conclusion is not that one model is safe and another is not. It is that custody is an architectural question, covering who can sign, how approval is split, and where keys are physically held.

Custody models sort along two axes. The first is who controls the keys. The second is how the keys are stored or how signing authority is divided.

• Self-custody (non-custodial): The user alone holds the keys and the recovery phrase, with full control.
• Third-party (custodial) custody: A provider holds and manages the keys, offering recovery and support in exchange for counterparty exposure.
• Qualified custody: A regulatory category with specific safeguards around segregation and eligibility, relevant mostly to institutions and regulated funds.
• Cold and hot storage: Whether keys are kept offline or on internet-connected systems, which changes the risk profile accordingly.
• MPC and multisig: Two ways to remove reliance on a single key, one splitting a key into shares and one requiring several independent keys.
• Institutional custody: Segregated accounts, multi-approver workflows and reporting built for organizations rather than individuals.

A third-party custodian can hold keys in cold storage and split signing across a multisig quorum, while a self-custody user can do the same thing with a hardware wallet and a personal multisig setup. Naming a model therefore describes who holds authority, not how strong the security is alone. Any real comparison has to state both axes at once.