Skip to main content
5 events
when toggle format what by license comment
Jul 12, 2017 at 16:55 comment added Swapnil Bhatia Thanks Paul. But could you not also timestamp it to Jan 1 2017 since that info is public? The delta is a fixed given resolution and you can "cheat" within it. But the scheme must prevent cheating outside of it. Is that clearer? Many thanks for giving my query the privilege of your thinking!
Jul 11, 2017 at 2:35 comment added Paul Uszak @SwapnilBhatia I'm probably still misunderstanding you . You can time stamp this comment as of yesterday's market close (1630 hrs). The few hours delay is the resolution /delta that you're talking about. And you clearly can't time stamp into the future as you don't have the market figures for next week. And you can't make them up either as you'd have to predict >8000 bits of entropy.
Jul 11, 2017 at 2:02 comment added Swapnil Bhatia Thanks Paul, for your answer. Perhaps my question is not completely clear. When I say the creation time of the bit string is chosen by the creator, I mean that the timestamp on the bitstring is may be chosen by the creator to be the current "time" at any time, and not that the owner can choose to timestamp it to any time in the past or future. Your scheme appears to fail this admittedly vague constraint. I will clarify my question so it is not confusing in this regard. Thank you again for your work!
Jul 7, 2017 at 3:57 comment added Kind Contributor The main reason for timestamping is to prove something happened "long ago". The past is well recorded and public, so you can use that as a signature. That is, at 2000-02-02 you can use "public entropy" of the day, then later in 2010-01-01 before a court case, you can also know and use the "public entropy" as of 2000-01-01, and re-sign a document. Such entropy could be a useful entropy source for generating a random key (in addition to many other additional sources which are XORd), but not as a timestamping mechanism IMO.
Jul 7, 2017 at 3:07 history answered Paul Uszak CC BY-SA 3.0