Attest locally.
Git hooks link each commit to its parents' receipts and timestamp the commit bytes. Proofs live in refs/momento/proofs — a hidden ref, not a branch.
Open source timestamping
A moment in time.
A proof you can keep.
Give any file a signed timestamp. Create a receipt in seconds, verify it whenever you need. Your file never leaves your device.
↳
your-file.zipStays on your device
LOCALSHA-256 fingerprint↓
m.Timestamp receiptMomento / ML-DSA-65✓
- FILE FINGERPRINT
- e3b0c44298fc1c149afbf4c8996fb924…
- SIGNED AT · UTC
- 2026-09-25 12:34:56.789
Example receipt · Your next moment is yours.
01 Hash locally→02 Sign the fingerprint→03 Keep your proof
TIMESTAMP TOOLS
A timestamp for your file.
No account. No setup.
Just your file and a little cryptography.
Checking Git commits? Jump to Git checks ↓ or use the Check repository tab above. How Git verification works →
Time is supplied by the signing server. What does a timestamp prove? ↗
ATTEST GIT COMMITS
Every commit, checked.
Hooks attest each commit as you create it.
Three checks prove the history is intact.
Check before you push.
git verify checks signatures, hashes, parent links, and time ordering offline. The pre-push gate blocks unconfirmed commits.
Check in CI.
verify-history re-runs the same offline check in CI and publishes the coverage badge to momento-badges.
SIMPLE BY DESIGN
Your files. Your workflow.
The file stays with you.
Your browser calculates a SHA-256 fingerprint. Only that hash reaches the signing service.
Your file→
sha256→ReceiptBuilt to be checked.
A JSON receipt, an ML-DSA-65 signature, and a public key. Verify locally, without contacting the issuer.
Understand the trust model ↗Make it part of your process.
Timestamp from your app, a script, or your API client.
POST /api/v2/stamp
{ "hash": "<SHA-256>" }What it proves: the issuer signed this hash and its stated time.
What it does not prove: authorship, ownership, original creation time, or independent clock accuracy.