I built TimeProofs, an open, privacy-first protocol to prove when a piece of data existed — without uploading the content.
You generate a hash locally, get a signed timestamp, and store a portable .tproof.json file. Verification can be done later, online or offline.
No blockchain. No accounts. No tracking. Just cryptographic proof.
This is v0.2 (stateless, bundle-based). Looking for feedback from devs and infra folks.
Docs: https://timeproofs.io Protocol: https://timeproofs.io/proofspec.html
In other words, I can't think of a use case in industry or academia or daily life or whatever, where someone needs to prove that a file existed at a specific time
What prevents an issuer from generating a proof that something existed arbitrarily far in the past?
Opentimestamps achieves that by Proof of Work. Do you require trusting the issuers instead?
I’m the creator of TimeProofs, an open, stateless proof-of-existence protocol and API.
The problem it tries to solve is simple: How can you prove that a digital event or file existed at a given time, without uploading or exposing the data?
TimeProofs works by: - hashing data locally - issuing a signed timestamp - producing a portable proof file (.tproof.json) - allowing independent verification later (online or offline)
Key constraints: - no data storage - no metadata collection - no blockchain - no identity or compliance claims
It’s designed as a neutral infrastructure layer, similar in spirit to DNS or TLS, but for timestamped evidence.
One challenge we’re facing is discoverability: search engines often confuse “TimeProofs” with existing timestamping vendors or proprietary services, despite very different goals and architecture.
I’m posting here mainly to get technical feedback: - Is the problem clearly stated? - Is the scope too narrow or too broad? - Does the stateless + bundle approach make sense?
Website: https://timeproofs.io Spec: https://timeproofs.io/proofspec.html
Honest feedback welcome.
timeproofs•1mo ago
TimeProofs is a small protocol to prove that some data existed at a given time, without uploading the data itself.
You hash locally, get a signed timestamp, and store a portable proof file (.tproof.json). Verification can be done later, even offline.
No blockchain, no accounts, no tracking.
Happy to answer questions or hear criticism.