A Netherlands court finds Tornado Cash developer Alexey Perstev is a flight risk and must remain in jail until February 20, 2023; Perstev was jailed in August
Pertsev has been in Dutch prison since August, accused of facilitating money laundering for his work on the U.S. Treasury-sanctioned app.
Context & Ripple Effects
Alexey Pertsev has been in Dutch custody since the Amsterdam arrest that followed the U.S. Treasury's sanctioning of Tornado Cash by two days, with Dutch prosecutors treating the mixer's developer as an alleged money-laundering facilitator rather than a bystander to how the code was used.
This pretrial-detention ruling is an early checkpoint on that theory of liability. The arc it opens runs through the Dutch court's later 64-month sentence for Pertsev and the parallel U.S. prosecution in which co-founder Roman Storm, profiled before his July 14 trial, was ultimately found guilty by an American jury — making the Netherlands the first jurisdiction to test developer criminal liability in custody.
First-order effects
- Pertsev remains in pretrial detention for roughly three more months, with his defense now fighting the case from a Dutch cell rather than at liberty ahead of the February 20, 2023 hearing date.
- Dutch prosecutors gain leverage in the case: a court has endorsed their framing of a code developer as a flight-risk suspect in a laundering scheme, strengthening the state's position going into trial.
Second-order effects
- Other Tornado Cash contributors face the template directly — Roman Storm's U.S. conspiracy trial proceeds on the same premise that building the mixer is itself the offense, with the Dutch detention signaling that pretrial custody is on the table for developers, not just operators.
- Privacy-tool developers across crypto now price personal criminal exposure into whether they ship mixer-adjacent code at all, shrinking the contributor pool for open-source privacy infrastructure.
Third-order effects
- If the pattern holds across the Dutch conviction and the U.S. jury verdict, the industry moves toward a regime where writing and publishing financial privacy code carries developer liability, forcing privacy engineering into jurisdictions or structures that insulate individuals — or out of the open entirely.
- Regulators gain a working playbook for treating protocol contributors as culpable actors, shifting the boundary of financial-crime enforcement from operators of services to the people who write the underlying software.
The trend: Criminal liability for crypto privacy tools is migrating from the operators of mixing services to the developers who write them, with Dutch and U.S. prosecutions converging on the same theory.