5 comments

  • timeproofs 2 hours ago

    Hi HN — I’m the creator.

    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.

  • marifjeren 2 hours ago

    That's cool. What's an example of when this would be useful?

      timeproofs an hour ago

      For example: you generate a file (code, dataset, document, AI output) and later need to prove it already existed at a certain time. TimeProofs lets you create a small proof file you can keep. Anyone can later verify the timestamp without seeing the original content.

        marifjeren an hour ago

        To me that's "what it does" whereas I'm wondering when it would be useful.

        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

          timeproofs an hour ago

          Fair question. It’s useful when you need to prove priority or existence without revealing the content. Examples: – You wrote something (code, research, idea) and want proof it existed before publication or disclosure. – You generated AI output and want to prove it wasn’t altered later. – You exchanged a document (contract draft, design, dataset) and want a neutral timestamp without involving a third party or storing the data. – You want evidence before a dispute, not after one starts. It’s not for everyday files — it’s for moments where “this existed at this time” might later matter. This keeps it grounded, avoids hype, and sounds like a real human explaining a niche tool.