← Blog

Academic Fraud Was Always Preventable

Yonathan Shalev4 min read

In 2023 a senior cancer researcher at a major U.S. medical school had eighteen papers retracted across a fifteen-year career. The retractions traced back to figures that had been edited after the original microscopy was captured — bands shifted, intensities normalized, occasionally a control panel reused across unrelated experiments. The researcher's defense was that the underlying conclusions were sound and the figures were merely 'cleaned up.' The journals concluded otherwise. Twenty grants worth seventy-three million dollars were under investigation by the funder. Two clinical trials based on the retracted findings were halted. The doctoral students who had graduated on the back of those papers spent the next three years answering questions about their own work that had nothing to do with their own work.

The technical part of this story has been preventable for ten years. Every modern microscope, every flow cytometer, every plate reader, every mass spectrometer has on-board firmware capable of signing its raw output at the moment of capture. The capability has been there since the manufacturers started shipping ARM cores in their controllers. What has been missing is the workflow that flips it on and routes the signed output into the lab notebook. Without the workflow, the path of least resistance is to export to TIFF, drop it in the figure-prep tool, and tweak. With the workflow, the raw is signed before any human can touch it, and the figure derivation is a separate signed transformation with the raw as input.

The Research Shield product, in active deployment at twelve research institutions across Israel, Germany, and Canada, does exactly that. The lab's instruments are paired with the institution's signing infrastructure on day one. From that day forward, every measurement carries a signature from the instrument that produced it, with the timestamp, the operator, the run conditions, and the device's calibration state embedded inside the signed payload. The figure that goes into the manuscript carries its own signature derived from the raw — the figure-prep tool reads the raw, applies declared transformations (background subtraction, contrast normalization, crop region), and signs the output along with the transformation chain. A reviewer or an investigator can verify both ends without involving the researcher.

The cultural part of the story is harder. Researchers have spent careers in a workflow where 'making the figure presentable' was a normal Friday afternoon. The mathematics of the signed-by-default workflow does not eliminate the impulse — it simply makes the impulse visible. A figure derived from raw with declared transformations is fine. A figure derived from raw with an undeclared transformation will still verify, but the verification will list the undeclared transformation, which becomes a question the reviewer asks. Most of what used to be called 'cleaning up' was actually small instances of undeclared transformation. Once those become listable, they become discussable, and the culture moves.

Funders have started to require signed-data workflows in new grants. NIH issued draft guidance in October 2025 mandating cryptographic provenance for all imaging-derived figures in funded research starting in fiscal 2027. The European Research Council's update to its Open Science requirements in March 2026 contains nearly identical language. The Israeli Council for Higher Education issued a similar requirement for institutional grants the same quarter. Once the funders require it, every research institution moves; once research institutions move, journals move; once journals move, the rest of the field follows within a publication cycle. The infrastructure has to be ready before the requirement lands. The institutions that started in 2025 have it ready. The institutions that start in 2027 will not.

There is a question I keep getting from PIs in the deployment kickoffs: 'Will this slow my lab down?' The honest answer is: for the first month, very slightly — the equivalent of one extra mouse click in the figure-prep tool. After that, the gain in audit-trail completeness is recouped many times over the first time a paper goes through review and the reviewer's authentication question is answered by the verification dashboard instead of by an email exchange that takes three weeks. After two years, the labs that have been operating signed-by-default produce manuscripts that move through review noticeably faster, because the figure-authentication leg of review collapses.

The eighteen-paper retraction case is now used as a teaching example in three research-integrity courses. The instructor's slide deck includes a chart showing what each retracted figure would have looked like under signed-by-default — the verification panel listing the undeclared transformation, the reviewer's question that would have been asked at the time, the response that would have either justified the transformation (and let the figure pass) or revealed the issue (and triggered correction before publication). The fork in the road was always available. The instruments could sign. The labs did not ask them to. That choice has changed in the institutions that took the question seriously, and it is changing in the rest because the funders are about to require it.

Try the proof layer yourself — drop a file, get a signed proof.

Try Free

Keep reading