Skip to content
Sprint projectFeb 1, 2026San Fransico

NeuroVer

Justin Stefan Stoica Tica, David Ghiberdic, Vladimir Necula · Team Katena

Submitted to The Technical AI Governance Challenge. Sprint projects are early-stage work by participants, not Apart Research publications.

Zero-Knowledge verification that LoRA fine-tuning followed safety constraints — without revealing training data or model weights.

Reviews

Judging this Sprint?

Review this project

Your public critique appears on this page without your name. Your private critique is not published; only the Apart team reads it. If you agree below, we share your review with grantmaking.ai (opens in new tab) and the Transformative AI Fund so strong projects can be funded.

Not shown on this page.

Shown on this page, without your name.

Only the Apart team reads this, and funders if you agree below.

Share my name publicly on grantmaking.ai *
Share my private critique with funders *

How much would this matter for AI safety if it worked? How innovative is it? For scores of 4-5: is this actually new to the field, or replicating recent work?

Scoring guide
  1. 1Negligible. No clear problem addressed, or no meaningful novelty.
  2. 2Limited. Addresses a real problem but with a generic or well-trodden approach. Incremental at best.
  3. 3Moderate. Clear problem with a reasonable approach; some novelty in framing or method beyond routine application of existing tools.
  4. 4Significant. Important problem with an original approach, or identifies a neglected problem area. A valuable contribution others could build on.
  5. 5Exceptional. Tackles a critical AI safety problem with a genuinely novel approach, or opens a new research direction. Clear theory of change. You'd be excited to share this with researchers in the area.

How sound are methodology, implementation, and findings?

Scoring guide
  1. 1Seriously flawed. Methodology broken, results uninterpretable, or implementation doesn't work.
  2. 2Weak. Approach has significant gaps: missing validation, flawed experimental design, or incomplete implementation.
  3. 3Competent. Technically solid given the short duration. Methodology makes sense, results are interpretable, limitations acknowledged, work builds toward clear conclusions.
  4. 4Strong. Thorough methodology with convincing validation. Results clearly support conclusions. Immediately useful for future work.
  5. 5Exceptional. Ambitious scope executed rigorously. Surprising findings, novel methods, or unusually robust validation.

How clearly are work, findings, and impact potential communicated?

Scoring guide
  1. 1Incomprehensible. Cannot determine what the project is actually claiming or doing.
  2. 2Hard to follow. Key information buried, missing, or diluted by excessive length. Significant effort to extract main points.
  3. 3Clear enough. Can understand the problem, approach, and results without undue effort. Core content clearly present: problem, method, findings, limitations.
  4. 4Well presented. Easy to follow, well-structured, appropriate level of detail. Target audience would get it quickly.
  5. 5Exceptionally clear. A pleasure to read. Complex ideas made accessible. Could serve as a model for how to present this type of work.

  1. Training verification is an important problem and exploring zero-knowledge proofs for this purpose is interesting. But most most important question remains unaddressed imo: Who ensures the weights committed to the proof are the actual training weights? I would suggest zooming in on that problem.

    Some other comments: The weight norm bound needs justification as a safety constraint. Why does ‖ΔW‖_F ≤ C imply safe fine-tuning? Is there literature on that? If so it would be good to reference it. Also the differential privacy invariant would need much more explanation.

    Generally, I suggest to zoom in on exactly one problem (e.g. verifying which base model was used XOR verifying model weight updates stay below a specific weight bound) but then going much more in depth on that one: What are all the steps where trust can break down? How can you address all of them? Once there is an argument that a ZK-proof actually fills a gap in a credible trust chain, you can go into full technical depth. But the context is crucial to make sure you're building sth that actually contributes to a solution.

    Read full reviewShow less
  2. I like the idea of applying ZK proofs to LoRA fine-tuning compliance. The focus on LoRA, where proofs circuits are tractable, shows good feasibility judgment. The implementation appears to be conventional Python norm-checking rather than actual ZK-SNARK circuits, though--room for development here.

Cite this project

@misc{tica2026neurover,
  title = {{NeuroVer}},
  author = {Justin Stefan Stoica Tica and David Ghiberdic and Vladimir Necula},
  year = {2026},
  month = feb,
  note = {Submitted to The Technical AI Governance Challenge, an Apart Research Sprint},
  howpublished = {\url{https://apartresearch.com/sprints/projects/neurover-gg0w}},
  url = {https://apartresearch.com/sprints/projects/neurover-gg0w}
}

Build something like this at the next Sprint

AI Collusion Research Sprint · Oct 23 - 25, 2026