When a crypto exchange collapses, the first thing to die is not the token price—it’s the trust architecture. Knaken, a Dutch exchange holding millions in client assets, filed for bankruptcy in September 2024. The missing 7 million euros weren’t lost to a hack. They evaporated in a structure designed to isolate, but engineered for failure.
Knaken operated a classic CeFi model: a B.V. running the trading platform, and a separate foundation—Stichting Knaken Payments—that supposedly held client funds. This structure is industry standard across Europe. The foundation is meant to create legal isolation, shielding client money from the operator’s creditors. But in practice, the isolation is a legal fiction if the governance is weak, the wallets are shared, and the accounts are opaque.
The Dutch court declared bankruptcy on September 26, 2024. Clients had already been locked out, payments stopped. The court immediately removed management control and appointed a trustee. The Dutch Fiscal Information and Investigation Service (FIOD) opened a criminal investigation, citing a “substantial deficit” in client assets. The public prosecutor stated that approximately 7 million euros in customer balances were missing. No technical failure, no exploit—just a hole in the balance sheet.
I’ve seen this pattern before. During the Celsius collapse in 2022, I traced their liquidity reserves on-chain and quantified a $2.1 billion shortfall before they filed. The anatomy is always the same: management claims segregation, regulators lack oversight, and when the music stops, the assets are gone. The Knaken case is a smaller scale, but the structural pathology is identical.
Let’s dissect the core failure: the foundation trust model. The Stichting Knaken Payments was a separate legal entity. Under Dutch law, however, client funds held by a foundation are not automatically shielded in bankruptcy. There is no statutory segregation like in the US trust company framework. The isolation depends entirely on how the foundation is managed—whether client funds are kept separate from operational funds, whether the foundation has independent directors, and whether there is a clear audit trail of wallet ownership. The court’s first action was to appoint a trustee to verify the accounts against the wallets. That alone tells you that the operator had no credible, published proof of reserves. The architecture of trust was built on paper, not on code.
Now layer in the regulatory gap. Knaken was not authorized by the Dutch Authority for the Financial Markets (AFM). The Netherlands, like most EU nations, is in the transition period before MiCA fully applies to all crypto-asset service providers (CASPs). MiCA Articles 70 and 75 will require strict client asset segregation, custodial agreements, and clear return procedures upon insolvency. But those rules are not yet binding on every operator. Knaken exploited this gap. They operated in a regulatory twilight, promising segregation via a foundation but delivering nothing enforceable.
The criminal investigation by FIOD adds another dimension. This isn’t just a civil bankruptcy; it’s a potential fraud case. The prosecutor stated that customers were left in the dark, accounts were blocked, and information was withheld. That is the hallmark of a failing operator trying to buy time. Based on my forensic work with FTX, I can tell you that when management proposes to “independently verify and distribute” assets—as Knaken’s management did before the court rejected it—it’s usually a delaying tactic to obscure missing funds. The court saw through it.
The architecture of trust, engineered for failure.
So what did the bulls get right? Some argue that Knaken is a minor blip, not an FTX. That the transition to MiCA will clean up the industry, and that regulated exchanges like Coinbase or Bitstamp are safe. That’s partially true. MiCA will raise the bar. But the contrarian take is this: MiCA does not eliminate the trust deficit. Legal segregation is only as good as the enforcement. The Knaken case happened while MiCA was being legislated. Enforcement was reactive—after the money was gone. The real solution is not legal; it’s cryptographic. Exchanges should publish audited, on-chain proof of reserves in real time, allowing users to verify that their assets are backed 1:1. That is the only architecture of trust that cannot be engineered to fail.
The crypto industry loves to talk about “trustless” systems. But as long as we use centralized exchanges, trust is inevitable. The question is whether that trust is placed in a foundation controlled by the same people running the exchange—or in verifiable code. Knaken is a reminder that the former is a house of cards. The latter requires work: formal verification of wallet controls, regular third-party audits, and transparent on-chain records. We have the tools. Most exchanges choose not to use them.
Will you wait for the next failure to verify your exchange’s foundation, or will you demand the only proof that matters—on-chain attestation of reserves? The architecture of trust must be engineered for resilience, not failure.