Replication certificate verifies deposited datasets and code for publications
Original title: Replication Certification at Publication: Checkable by Anyone, Anywhere, in Seconds, Forever
Cryptographically signed record allows anyone to check replication files without journal reanalysis.
Journals require replication datasets, but deposits alone do not prove correctness. The paper introduces replication certificate, a signed record of files and logged output. Anyone can verify it in seconds, and the archive timestamps it on a blockchain, replacing months of journal reanalysis.
- Signed record replaces journal reanalyses
- Archive computes random seed from hash
- No one can backdate or fake without detection
From the original article
1 min read at arxiv.orgAuthors increasingly deposit replication datasets---the data and code behind publications---in archives, and journals increasingly require them to, under progressively onerous rules. But a deposit alone proves little, so authors keep paying: months for the journal's reanalyses, years answering readers' questions, and rancor as failed replications become accusations because no record establishes what actually ran.
By Gary King · arxiv.org
A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.