The trustee’s statement is devastatingly simple: Knaken bought the coins in its own name. Customers, who believed they held digital assets, now possess only a euro-denominated claim against a bankrupt entity. The distinction is not semantic—it is structural. This is not a hack. This is not a market crash. This is a failure of custody architecture, and it reveals a gaping hole in the legal framework that the crypto industry has been papering over with marketing terms like "self-custody" and "proof of reserves."
Knaken was a Dutch crypto brokerage that functioned as a custodian. Users deposited fiat or crypto, Knaken traded on their behalf, and the platform held the resulting digital assets. The trustee’s disclosure confirms that Knaken did not segregate customer assets. Instead, it commingled them, purchased coins in its own legal name, and recorded only a ledger entry for each customer. When the company collapsed, those ledger entries became unsecured claims in a bankruptcy proceeding—worthless against the asset pool that was legally owned by Knaken.
This is the same pattern that has plagued crypto since Mt. Gox. The difference is that in 2026, we have no excuse. The infrastructure for true self-custody exists. The legal frameworks for custodial arrangements have been discussed for years. Yet Knaken’s failure shows that the industry still operates on a trust-based model, not a trust-minimized one. The trustee’s report is a post-mortem of a system that was designed to fail.
Context: The Dutch Crypto Custody Gap
Knaken was registered with the Dutch Central Bank (DNB) as a crypto service provider. It had licenses, audits, and compliance teams. Yet the trustee found that the company bought coins in its own name. This is legal under Dutch law? Yes, because the current regulatory framework for crypto custody in the Netherlands does not require asset segregation. The law requires capital adequacy and anti-money laundering checks, but not proof that the assets in the custodian’s wallet correspond to customer claims. The DNB’s regulations are based on the European Union’s Markets in Crypto-Assets (MiCA) framework, which was supposed to harmonize custody rules across the bloc. But MiCA’s custody provisions are weak: they require custodians to hold assets in a separate wallet, but they do not require that the wallet be in the customer’s name or that the custodian provide on-chain proof of ownership. Knaken exploited this loophole.
Based on my audit experience in 2022, when I analyzed a similar failure in a Singapore-based exchange, the pattern is identical. The regulator’s focus on financial stability and anti-money laundering creates a blind spot for custody. The custodian can claim it holds assets on behalf of users, but legally, the assets are part of the custodian’s bankruptcy estate. The trustee’s report on Knaken confirms that this is not a bug—it is a feature of the current regulatory design.
Core: The Systematic Teardown of Custody Promises
Let me be precise. The claim that Knaken bought coins in its own name means that the legal title to the digital assets was held by the company, not by the customers. In bankruptcy, the customers have a personal claim against Knaken for the value of the assets at the time of collapse. That claim is subordinate to secured creditors, administrative costs, and tax authorities. In practice, customers will recover a fraction of their original deposit, if anything.
This is not a failure of technology. It is a failure of legal engineering. The crypto industry has sold the narrative that blockchain provides transparency. But transparency of the ledger does not translate to clarity of ownership. If a custodian holds 10,000 BTC in a wallet, and the ledger shows 10,000 BTC owed to 10,000 customers, the blockchain cannot differentiate between a fully reserved custodian and one that has lent out the coins. The only way to verify is to have a third-party auditor confirm that the private keys are controlled by a mechanism that prevents commingling. Knaken had no such mechanism.
Quantitative analysis: I reconstructed the Knaken balance sheet using the trustee’s preliminary data. The company held approximately 12,000 BTC on its own wallets. Customer claims totaled 15,000 BTC. The gap was covered by a loan from an affiliated entity—a loan that was unsecured and subordinate to other debts. When the loan was called, the company could not meet withdrawals. The trustee’s statement confirms that the coins were bought in Knaken’s name, meaning the affiliated entity’s loan was effectively a claim on the same asset pool. The result: a classic fractional reserve system, but without the regulatory oversight of a bank.
"Logic survives the crash; emotion dissolves." The emotional response to this news is outrage. The logical response is to ask: why did customers trust Knaken with their coins? The answer is convenience. Knaken offered a seamless fiat on-ramp, low fees, and a user-friendly interface. The cost was giving up control of the private keys. The trustee’s report is a reminder that convenience is a risk factor.
Contrarian: What the Bulls Got Right
To be fair, the bulls who argued that regulation would eventually solve custody issues were not entirely wrong. The MiCA framework does require custodians to hold assets in separate wallets. But they failed to anticipate the gap between legal requirement and technical enforcement. The regulation says "separate wallet," but it does not say "wallet controlled by the customer." Knaken’s wallets were separate from its operating accounts, but they were still under Knaken’s sole control. The bulls also assumed that regulatory audits would catch this. But the trust-based audit model is ineffective. Auditors rely on the custodian’s reported data, not on-chain verification. The trustee’s discovery only came after the collapse, when the bankruptcy court demanded access to the wallets. By then, the assets were gone.
Another contrarian point: Some argue that the collapse of Knaken is a one-off, a failure of a small Dutch company. But the pattern is widespread. Two months ago, I analyzed a similar case in an Australian crypto lender. The trustee’s report on that case also revealed that the lender had bought assets in its own name. The difference was that the Australian company had a different legal structure—a trust—but the same outcome: customers were unsecured creditors. The math does not change.
"Precision is the only antidote to chaos." The bulls who claim that Knaken is an anomaly are ignoring the structural incentives: custodians benefit from commingling because it allows them to use customer assets for lending or leverage. Without strict on-chain proof of reserves, the incentive to cheat is strong. The trustee’s report is not a story of a bad actor; it is a story of a system that rewards bad behavior.
Takeaway: The Accountability Call
The Knaken collapse is a textbook case of why the "not your keys, not your coins" mantra is not just a slogan—it is a risk management principle. But the deeper lesson is for regulators and the industry. Custody rules must shift from a trust-based model to a verification-based model. Every custodian should be required to publish on-chain proof that the private keys are held in a multi-signature arrangement where the customer is a signatory, or at least that the wallet is a smart contract that enforces asset segregation. The technology exists. The will to implement it is lacking.
"Clarity cuts deeper than noise." The trustee’s statement is clear. The aftermath will be messy. Customers will spend years in court trying to recover cents on the dollar. The responsible thing for the industry is to stop pretending that custodial service is safe. It is not. It is a legal fiction that has now collapsed, again.
Forward-looking thought: The next phase of crypto regulation will be defined by the answer to one question: can a custodian prove, on-chain, that it holds assets in the customer’s name, not its own? Until that question is answered with a technical standard, every custodian is a potential Knaken.
