◆ Research data
Record your dataset and analysis plan before you begin.
A reviewer, a co-author, or an integrity office asks which version of the data and plan you used. Record the raw files and analysis plan before you begin, and keep them for later comparison. The fingerprints do not establish when you collected the data or began the analysis; keep study records separately.
The record is in Base’s public transaction history, which we cannot edit and an integrity office can read for itself. Keep the raw files and the receipt exactly as recorded.
What happens if we shut down →A finalized record means we observed a successful Base L2 receipt, not Ethereum settlement. Independent checking needs the retained file, receipt and suitable Base history access. Read the evidence limits.
◦ Use cases
Ways to use a dated file record
Raw collection set
Record the raw files the day collection ends and keep them unchanged. Re-exporting can change the bytes; if it does, the fingerprint will not match. Keep the exact file you recorded.
Pre-registered analysis plan
Record the plan alongside the data. Each fingerprint gets a public chain reference. Two records may share a transaction and timestamp; their positions do not prove which artifact came first.
Reviewer packet
Hand a reviewer the file and the receipt. They can run the comparison themselves on the public verify page, with no account and nothing to install.
▸ FAQ
Common questions, answered plainly.
Does this prove the data was collected before the analysis?
No. It provides dated references for the dataset and plan, not evidence of when collection or analysis happened. Two fingerprints may share a transaction and timestamp; their slot order does not establish artifact chronology. Keep study records separately.
Can I record data I am not allowed to share?
Check the restrictions that apply before recording it. Keeping the file body local does not grant permission to publish its fingerprint. Predictable inputs can be tested against a public fingerprint, and a shared transaction reveals submission in the same short window. File metadata stays off-chain.
What if I re-export the dataset later?
Re-saving a CSV or re-running an export can change its bytes even when it looks the same. If the bytes change, the fingerprint will not match. Keep the exact file you recorded, and record a changed export separately.
Do I need an account?
No account is needed to check a file or download the independent verifier. Create an account and verify your email to notarize files and manage your records.