Insights
Short-form commentary on real software-in-court cases — the specific technical artifact that decided each one.
Autopilot on trial: the marketing name versus the vehicle's own log
The first US felony Autopilot-crash case turned on the vehicle's own event data, not the brand name — why it needs a court-grade software expert.
Read the insight →Terra-Luna: when the algorithm becomes evidence
The Terra-Luna collapse shows how a failed software mechanism becomes courtroom evidence: the promised algorithm versus the on-chain record and the hidden human hand behind the peg.
Read the insight →AI Prompts as Evidence: When an Expert's AI Tools Become Part of the Opinion
A landmark U.S. ruling held that an expert's AI prompts are discoverable methodology — making the computer-engineering expert the de-facto gatekeeper for every case where opposing counsel used a language model to sift evidence.
Read the insight →When code is silent and the service speaks: Tornado Cash and the developer-liability principle
In the Pertsev case a developer was convicted over a privacy tool whose core smart contracts could not be changed after deployment — all because the team retained control over the surrounding infrastructure. The question 'who is liable for code?' has never been more urgent for Israeli lawyers representing developers.
Read the insight →COPA v. Wright: when metadata refutes a witness
In the trial where Craig Wright claimed to be Bitcoin's creator, forensic analysis of metadata, fonts and timestamps exposed documents that had been edited. The lesson: in identity and authenticity disputes, a file's history can be more devastating than a hostile witness.
Read the insight →When the watch testifies: Fitbit data vs. the defendant
In the Dabate case the victim's Fitbit step data contradicted the timeline the defendant gave. But the real lesson is not 'wearables incriminate' — it is that sensor data persuades only when an expert can explain its limits as well as its power.
Read the insight →Horizon: when 'the computer says so' is simply wrong
Hundreds of UK subpostmasters were prosecuted on shortfalls that the Horizon software reported — until it emerged the system had known bugs and remote access. The lesson for any case built on computer output: reliability must be proven, not presumed.
Read the insight →FTX, auto-deleting messages, and what survives anyway
SBF directed FTX staff toward auto-deleting messaging, and the court treated that policy as evidence. The lesson for any deletion case: ephemeral messaging rarely erases the whole story — the surrounding metadata usually survives.
Read the insight →Pegasus in the Netanyahu courtroom: what the defense actually got
The court ordered some spyware-related material disclosed to the defense while protecting method-privilege — not everything, and not the tool itself. Which layer was disclosed is a technical question that needs an expert to answer.
Read the insight →