Hi HN, 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

Hi HN, 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 https://timeproofs.io Spec: https://timeproofs.io/proofspec.html https://timeproofs.io/proofspec.html Honest feedback welcome.