Private keys are the official starting point for any serious discussion of digital-asset custody, and they are also the point at which casual language usually fails. Deutsche Bank’s official September 16, 2026, announcement put the mechanics in unusually plain official English: “Digital assets such as Bitcoin are accessed and transferred using unique digital codes known as private keys. Whoever controls the private key controls the asset.” The same announcement said the bank’s planned Digital Asset Custody solution “protects and manages these keys and the digital wallets linked to them on behalf of clients,” so that clients “do not need to build and operate their own systems for holding digital assets securely.” The official text is at db.com. This article is a method for reading that kind of official custody language, not a second news account of the November product-page status, and not a review of any exchange’s retail wallet.
Three official models are now on the public record in the same week, and they should not share a single definition. In the bank-controlled model just quoted, the institution manages the keys. In the official OKXICE launch post, the venue says customers will hold digital securities in self-custodial wallets and that the venue will hold neither assets nor keys. In a typical exchange account, the platform holds assets under its own terms of service and, in some cases, publishes reserve attestations; that relationship is defined by that venue’s official documents, not by a bank announcement and not by a self-custody token-securities notice. The method below keeps those models apart, uses official lists and official warnings as they are written, and refuses to invent fees, assets under custody, or a deposit-insurance result that the official text does not support.
What “control of the key” officially means
A digital asset that exists on a public blockchain is transferred by creating a valid transaction signed with the corresponding private key, or with a set of keys if the wallet is multi-signature or otherwise sharded. The official Deutsche Bank sentence, “whoever controls the private key controls the asset,” is the legal and operational core. It is why a screenshot of a balance is not ownership, why a lost key can be an irretrievable loss in a self-custody setting, and why an institution that offers to “manage the wallets and private keys on clients’ behalf” is offering a very specific service: it is taking on key control, under its own governance, so the client does not have to operate that infrastructure.
Taking on key control is not the same as turning the asset into a bank deposit. The official September announcement is explicit that “crypto-assets are not covered by a deposit-guarantee scheme comparable to the protection applicable to eligible bank deposits.” A methodical reader should keep that sentence next to the key-control sentence at all times. The bank may hold the keys, apply hardware-module protection, and still warn that the asset is not protected like an eligible euro or dollar deposit at the same institution. Any explainer that drops the warning is incomplete.
The official control stack: hardware, people, warm and cold
Institutional custody announcements usually describe a stack of controls rather than a single vault metaphor. The official Deutsche Bank list is a useful template because it is specific: “secure key generation and hardware-based protection, segregation of duties, multi-person approval processes, separate warm and cold storage environments, a redundant technical setup, and controlled backup and recovery arrangements.” The official product page at digitalassets.db.com adds hardware security modules and access through the bank’s Autobahn gateway. Those are official design claims. They are not, by themselves, a published service-level agreement or a completed incident-response history.
| Official control, as commonly described | What it is meant to address | What official text often still leaves open |
|---|---|---|
| Hardware security modules or hardware-based key protection | Reducing the chance that a key can be extracted as ordinary software | Which device family, who can administer it, and how firmware is updated |
| Segregation of duties and multi-person approvals | Preventing a single employee or process from moving assets alone | The exact quorum, the emergency override, and the time to assemble it |
| Cold storage | Keeping keys or signing capacity offline until needed | Withdrawal cut-off times and how a client instruction is released |
| Warm storage | Making routine transfers possible without opening the whole vault | Limits, pre-approved address lists, and monitoring thresholds |
| Redundancy and controlled backup and recovery | Surviving a site, device, or process failure without losing the keys | Where backups live, who can invoke them, and under what legal authority |
| External technology providers for defined components | Using specialist infrastructure rather than building every layer in-house | The named vendors, their access rights, and the allocation of liability |
Warm and cold storage, in this official vocabulary, are operational states, not investment products and not interest-bearing accounts. A coin in official cold storage is still exposed to the asset’s price, to the issuer risk of a stablecoin if that is the asset, and to whatever residual operational and legal risks the official terms assign to the client. A methodical reader does not translate “cold” into “safe in every sense,” and does not translate “warm” into “as easy as a retail app transfer,” unless the official operating procedures actually say so. The September Deutsche Bank announcement does not publish those procedures in full, and this article does not invent them.
Asset lists are official, and they are narrower than “crypto custody”
The official launch set in both the September announcement and the product page is Bitcoin, Ether, USDC, EURC and EURAU. Expansion is officially possible, “subject to client demand and the bank’s product-approval, risk management and regulatory processes.” Tokenized financial instruments are “included in the roadmap,” which is official future-tense language, not a completed product schedule. The correct reading habit is to treat the named five assets as the official current list on the pages retrieved for this article, and to treat every other token as unofficial until the bank’s official list says otherwise.
Stablecoins on an official custody list create a second-issuer problem that the custody stack does not dissolve. USDC, EURC and EURAU remain products of their issuers, with their own reserve, redemption and regulatory facts. Holding them in a bank-managed wallet does not, on the official September wording, convert those tokens into Deutsche Bank deposits or into a Deutsche Bank guarantee of the issuer. U.S. readers who are following the federal stablecoin rulebook should also keep that rulebook on its own official track, including the OCC’s finalized GENIUS Act rule ahead of January 2027. A European bank announcement and a U.S. banking rule can both be official and still not be the same legal perimeter.
Self-custody, bank custody and exchange custody, side by side
Self-custody means the client, or the client’s own hardware or software wallet, controls the key. The official OKXICE post’s statement that the venue will hold neither assets nor keys is a self-custody design claim for that venue’s digital securities, and it comes with a different residual-risk list: user error, phishing, lost seeds, and the need to understand how corporate actions will reach a self-custodial wallet. Bank custody, in the official Deutsche Bank definition, moves key control inside a supervised institution and replaces those user-key risks with institution, process, vendor and legal-term risks, plus the official warning that the asset is not deposit-guaranteed like an eligible bank deposit. Exchange custody, where it exists, is a third contract: the user has a claim on the venue under that venue’s official terms, which may include withdrawals, incidents, bankruptcies and, in some cases, published reserve proofs. Those terms have to be read on the venue’s official pages. They cannot be inferred from a bank announcement.
None of those models, on the documents cited here, is a spot-trading fee schedule. A custody announcement does not tell a reader what it costs to trade bitcoin on a public order book, and it does not authorize a “cheapest venue” claim. Readers who are comparing ordinary spot execution costs should use official venue fee pages, and can start with the already published guide to what a zero-fee spot headline does and does not include. This custody method piece stays on keys, controls, asset lists and residual risk.
A due-diligence list that stays inside official text
- Which legal entity is the custodian, and in which official announcement or agreement is that entity named?
- Which official asset list applies to this client, on this date, not merely to a marketing page last year?
- Who controls the keys, in the official definition: the client, the bank, the exchange, or a split-control arrangement?
- What official controls are listed — hardware, approvals, warm and cold, backup — and which operating details are still only in non-public onboarding papers?
- Are external technology providers named, and if not, does the official text at least admit that they are used for defined components?
- What official residual-risk warnings are attached, especially price volatility, fraud, cyber incidents, vendor failure, and the presence or absence of deposit-guarantee language?
- What official geographic and client-eligibility limits apply? A European institutional service is not a global retail wallet.
- What official statements, if any, cover forks, air-drops, stablecoin issuer events, stalled transfers, or insolvency treatment? If the public announcement is silent, the public explainer should be silent too.
The list is a reading order for official documents, not a recommendation to use or avoid any custodian, and not a substitute for legal advice. It is also a list that can be applied, with different official answers, to a self-custody venue or to an exchange account. The answers will not be the same, and that is the point of asking.
Transfers are official, and they are not a trading venue
The official Deutsche Bank announcement says clients can “safeguard their digital assets and transfer digital assets to third parties.” That sentence is easy to inflate into a picture of a bank-run exchange. The official text does not, in the passages used here, describe an in-house dealing desk, a public order book, or a Deutsche Bank reference price for bitcoin. A transfer to a third party is an official movement of an already held asset to an address or account that the bank’s process will accept. It is subject, in any serious institutional setting, to the bank’s due diligence, to the client’s approved-instruction procedures, and to whatever sanctions, travel-rule and anti-money-laundering processes apply. The September announcement does not publish those process times or those address-book rules, and this method piece leaves them unpublished.
The distinction matters for treasury operations. A corporate client that wants to receive a stablecoin from a counterparty, hold it under bank-controlled keys, and later send it to another official counterparty is looking for a custody-and-transfer rail. A corporate client that wants to buy or sell bitcoin against dollars or euros still needs a trading venue, a dealer, or another official execution channel, unless a later official product extends the service. Official custody language that includes “transfer” should be read as transfer. Official marketing language that blurs transfer into execution should be brought back to the announcement’s actual verbs.
Internal transfers between warm and cold storage, which the official product page lists, are a different official movement again: they are movements inside the custodian’s own control environment, not payments to a third party. A methodical reader asks, of any official “transfer” heading, whether the movement is internal or external, who must approve it, and whether the official public text even answers those questions. If the public text does not, the explainer should not pretend that it does.
A worked reading of the official residual-risk sentence
The September announcement says that digital assets “involve material risks, including price volatility, fraud, cyber incidents and failures of market participants.” Four named categories, plus the later deposit-guarantee warning, are enough for a careful walk-through. Price volatility is a market risk. No official hardware module cancels it. A bitcoin balance can be perfectly controlled and still lose official dollar value between two reporting dates, as any miner’s or treasury company’s official filings will also show when they discuss fair-value movements. Fraud is a conduct risk. It can arise from phishing of the client’s instruction channel, from compromised employees, or from external impersonation, which is one reason official texts emphasize identity, approvals and segregated duties. Cyber incidents are a technology risk, aimed at keys, communication channels, or service providers. Failures of market participants are a counterparty and infrastructure risk: an issuer, an exchange, a wallet vendor, a network, or another intermediary can fail even when the custodian’s own official controls operate as designed.
The official list is not exhaustive, and the announcement does not claim that it is. Legal-jurisdiction risk, fork risk, and stablecoin-issuer risk can all sit under or beside “failures of market participants,” but they are not separately itemized in that sentence. A methodical reader can note the omission without filling it with unofficial legal conclusions. The deposit-guarantee warning then does a different job: it tells the reader that, whatever official controls are applied, the statutory protection that may apply to eligible deposits is not, on this official wording, extended to the crypto-assets in custody. Repeating that official warning is more useful than inventing a numeric “safety score.”
Eligibility language belongs in the same careful pass. The official initial target group is clients of Deutsche Bank’s Corporate Bank and Investment Bank, including corporates, asset managers, hedge funds, custodians, brokers and sovereign institutions, subject to the bank’s criteria, due diligence and risk appetite. That is a defined institutional set, in an official European launch plan. It is not a walk-in retail product, and it is not an official on-ramp for every user of a global crypto app. A method that forgets eligibility will misdescribe the service as widely as a method that forgets the deposit-guarantee warning.
Roadmaps require one last official habit. “Tokenized financial instruments are also included in the roadmap” is a real official sentence, and it is still a roadmap sentence. A later secondary report may describe a memorandum of understanding or a planned tokenized fund. Unless and until an official product document says a named fund or tokenized instrument is live, the method is to keep the item in the future tense. Official custody of bitcoin today, official mention of a tokenized-instrument roadmap, and a completed tokenized-fund launch are three different facts. This article records the first two as they appear in the official September text and the official product page, and leaves the third unclaimed.
If this method appears to spend more words on warnings than on the convenience of not running a wallet, that is because official custody announcements usually do the same once the marketing paragraph is over. The September Deutsche Bank text describes a genuine operational service for a defined client set, and it also describes residual risks, a limited asset list, a regulatory process, and the absence of deposit-guarantee equivalence. A useful explainer follows that proportion. It does not turn a key-control model into a promise that digital assets have become ordinary bank money, and it does not turn a different official model — self-custody, exchange custody, or a still-scheduled tokenized-securities wallet — into a footnote of the first. Each official model keeps its official verbs, its official lists, and its official warnings, which is the only way a week with several custody and tokenization headlines can be read without dissolving them into one another.
Those official verbs, lists and warnings are also the last items a reader should check before accepting any secondary summary of a custody launch, including summaries that appear in the same news cycle as inflation data or auction results and have nothing official to do with either.
Keeping those cycles on their own official pages is part of the same method, not a separate topic.
Frequently asked questions
If a bank holds the keys, is the asset a bank deposit?
Not according to Deutsche Bank’s official September 16 warning, which says crypto-assets are not covered by a deposit-guarantee scheme comparable to the protection applicable to eligible bank deposits. Other institutions may use other official wording; read the document in hand.
What assets are named on the official Deutsche Bank list retrieved here?
Bitcoin, Ether, USDC, EURC and EURAU. Those five official names are the list used here, not an unofficial broader crypto inventory. Expansion is described as possible, subject to official processes. Tokenized instruments are on the official roadmap, not treated here as already launched products.
Is bank custody the same as self-custody?
No. Official self-custody language says the client holds the keys. Official bank-custody language in the Deutsche Bank announcement says the bank manages the keys on the client’s behalf.
Do official control lists eliminate asset-price risk?
No. Hardware modules and multi-person approvals are operational controls. They do not officially cancel market-price volatility, and they do not officially make a stablecoin issuer’s reserves into the custodian’s guarantee.
Does this article recommend a custodian?
No. It is a method for reading official custody documents and official warnings.
Sources and research limits
Primary official sources are Deutsche Bank’s September 16, 2026, announcement and the official Digital Asset Custody product page, used here as a worked example of bank-custody language. Self-custody contrasts use OKX’s official November 11 TSV post as an example of a different official model. This article does not invent fees, assets under custody, vendor names missing from the official announcement, or a launched tokenized fund.
