Knaken Bankruptcy Proceedings After Customer Funds Freeze

On 2026-06-30, the Dutch Public Prosecution Service asked a Rotterdam court to declare Knaken Cryptohandel and Stichting Knaken Payments bankrupt, describing the request as being in the public interest.^[1] The proceeding followed a period in which Knaken had been offline since early June, with reporting indicating that an estimated 30,000 customers were unable to access their holdings.^[2][3] At the level of the present record, this was an exchange-collapse event defined by loss of customer access and a regulatory intervention, rather than a confirmed on-chain exploit or a publicly quantified theft.

The earliest pivotal development in the available timeline was the platform's loss of availability in early June.^[2] Reporting states that customers could no longer reach their holdings once the service went offline, and that the company had stopped paying customers out.^[2][7] That sequence matters analytically because it places the first documented failure at the custody-and-withdrawal layer: users were not described as facing market losses from trading activity, but as being unable to retrieve assets already held through the platform.^[2][3][7] The same reporting further stated that Knaken had reportedly told customers not to file damage claims, although the present dossier does not establish the legal basis for that instruction or whether it was uniformly communicated.^[7]

A second documented element concerned licensing and regulatory status. Decrypt reported that Knaken offered services including euro-to-crypto exchange, trading, and digital-asset storage, and that these activities required a license from the Dutch markets regulator, the AFM, under the applicable EU crypto rules; the same report stated that Knaken never obtained that license.^[4] In the present record, that point does not by itself establish insolvency or misappropriation. It does, however, establish that the platform's operating posture was already in tension with the regulatory framework governing the services it was providing.^[4] The timing is also notable because the brief records that the EU transition period for firms operating under older national rules was due to expire on 2026-07-01, immediately after the petition date, although the dossier does not establish whether that deadline directly precipitated the outage or the bankruptcy request.

The next pivotal step was enforcement activity on 2026-06-29, when investigators in a separate FIOD criminal investigation searched premises, seized laptops and phones, and confiscated company assets.^[5] The report stated that no one had been arrested at the time of publication.^[6] This distinction is material. The search-and-seizure activity indicates that Dutch authorities had escalated the matter beyond supervisory concern into a criminal investigative posture, but the absence of arrests means the public record had not yet advanced to charged individual culpability.^[5][6] Nor does the present dossier establish the suspected offense theory underlying the FIOD action. As of 2026-06-30, the documented facts support the existence of an active criminal probe and asset seizure, but not a concluded attribution of fraud, theft, or embezzlement.

Against that background, prosecutors then sought formal bankruptcy orders in Rotterdam on 2026-06-30.^[1] The petition named both Knaken Cryptohandel and Stichting Knaken Payments.^[1] In practical terms, the bankruptcy route appears to have been used as a public-interest mechanism to place the failed entities into a court-supervised insolvency process after customer access had already been interrupted and payouts had reportedly stopped.^[1][7] What the filing did not yet resolve was whether customer assets were fully segregated, whether any shortfall existed, or whether recoveries would depend on tracing, liquidation, or ordinary insolvency administration. None of those points is established in the current dossier.

The documented consequences were therefore operational, legal, and customer-facing rather than numerically quantified in monetary terms. Operationally, the platform had been offline since early June.^[2] Customer-facing impact was reported as an estimated 30,000 users unable to access holdings and a halt in payouts.^[3][7] Legally, the matter had moved on two tracks by 2026-06-30: a bankruptcy petition brought by the Dutch Public Prosecution Service and a separate FIOD criminal investigation involving searches, device seizures, and confiscation of company assets.^[1][5] As of that date, no arrests had been reported, no final bankruptcy ruling had been established in the dossier, and no customer distribution or recovery percentage had been documented.^[6]