← Blog

Every Student Deserves Proof of Their Work

Yonathan Shalev3 min read

If you have ever been a graduate student, you have either lived this story or watched a friend live it. You worked on the experiment for eight months. You designed the protocol. You ran the data. You wrote the methodology. The paper goes out. Your name is on it — but somewhere in the middle of the author list, behind people who did not touch the bench. By the time you have the standing to argue, the publication is already cited.

Academic authorship is a quiet area. There are no notaries in the lab. There is no court for who designed which graph. The conventions of co-authorship are old, well-meaning, and absolutely subject to politics. The supervisor remembers the project differently. The senior postdoc remembers the project differently. The journal does not arbitrate. By the time the dispute surfaces, the paper trail is messy and the timestamps live on someone's old laptop.

Signed contributions break the pattern. The student writes the methodology section. She drops the file in the GI Engine. The signed proof says: this exact text, by this person, at this minute, before anyone else saw it. She runs the experiment. The instrument output is signed. She generates the figure. The figure file is signed. By the time she submits the manuscript, she is carrying a chain of signed contributions stretching back to before the supervisor was involved. That chain settles authorship arguments before they start.

The same logic applies beyond authorship. Grade disputes get faster: the assignment is signed by the student at submission, signed by the professor at grading, and the chain shows exactly which version was graded. Plagiarism allegations resolve faster: every draft is signed in order, so the timeline of who wrote what is unambiguous. Peer review gains accountability: a reviewer who signs a critical comment cannot later deny the comment, and a paper that ignores a signed comment cannot pretend the comment was absent.

The stakes are not theoretical. Authorship disputes affect tenure, grant eligibility, citation counts, and ultimately careers. A graduate student who can demonstrate her exact contribution to a paper is in a fundamentally different negotiating position from one who cannot. That asymmetry should not depend on whose laptop kept the older copy. It should depend on the math, which is fair to everyone.

Research Shield is the GI Engine product built around this domain. It is not a manuscript-management system; it is a contribution registry. You drop your draft, your dataset, your code, your figure — anything that represents work — and the engine signs it with provenance the institution can verify offline. Once the work is signed, it cannot be quietly reattributed. Once it is reattributed, the original author can show the original signature. That is the protection every student deserves and almost none currently have.

Universities will adopt this on different timelines. Some will adopt it because their researchers ask. Others will adopt it because a high-profile dispute forces the question. Either way, the era of 'we'll just remember who did what' is closing. The math is here. The infrastructure is here. The students who use it now are the ones who will have an answer when the inevitable disagreement arrives.

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

Try Free

Keep reading