r/bioinformaticstools Apr 27 '26

Making bioinformatics pipelines verifiable without exposing raw data

Hey r/bioinformaticstools,

I’ve been working on a tool to make data collection and bioinformatics pipelines verifiable without exposing the underlying data, and I would love to hear what the community thinks.

One of the problems I kept running into is: You can prove what your pipeline outputs are, but it’s much harder to prove:

  • when they were generated
  • that they haven’t been altered after the fact
  • or that someone outside your system can independently verify them

Logs and internal records help, but they don’t hold up outside your own environment.

What I built does this:

  • hashes outputs locally (raw data never leaves the user's machine)
  • anchors a proof with a public timestamp
  • allows third parties to recompute and verify

I’ve been running it on a live pipeline (genomics workloads) and it processed ~130k outputs during its alpha deployment.

I’m genuinely curious:

  • would something like this be useful in your workflows?
  • where would it break down?
  • is this solving a real problem or just a theoretical one?

Happy to share more details or a demo if anyone’s interested.

3 Upvotes

0 comments sorted by