Oddbean new post about login | logout Nip request: Add the most recent blockhash as a tag of an event. Together with the open time stamp, this generates a verifiable time windows when the note was posted.
Amethyst can already stamp your post with OTS, is that the same thing as your idea?
OTS shows that a post is older than X, including the block hash shows that it's newer than X. Both seem useful.
Exactly, proof of absence and proof of existence.
It doesn't fully prove absence, because nothing stops you from reposting the same thing with a different block hash. Though people would find you annoying :-)
True, but single use seals might fix that.
Can you give an example where this latter attestation might be useful? Usually the need is to prove that something is _older_ than X.
"Hey, you said politically incorrect thing!" "But back then it was normal" "No you said it recently, you're cancelled!"
I recently caught nostr:nprofile1qqsdjyv3uv8qq3ztjskqaqk263ctx2h3w9mycgn4hmstmxfh0m75qagpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsz8rhwden5te0wfjkccte9e5xjemgd35kw6r5v4ezucm0d5hszxmhwden5te0wfjkccte9ehx7um5wfhkx6m9wshx7un89u7vcg6t red handed in a time stamp scam. He printed a t-shirt with only a block height of Nostriga, and when I told him that's not a proof, he admitted that in fact he printed the shirt weeks before and just picked an estimate of which block number will be produced during the conference. He could not have included the actual block hash of the event before it was mined, because nobody knows the hash in advance. If he wants to prove that the shirt was produced during the conference, add the time stamp of the block at the beginning of the event on the shirt, and add a picture of him wearing it in an open timestamp proof on the blockchain.
How can this help with past events? They can easily be forged.
You cannot create an event today, and put it's hash into a block from yesterday.
both are useful the block hash proves knowledge of some information that couldn't have been available before (same as using a newspaper headline, for example), so it puts a >= bound on the timestamp OTS stamping can be used to prove that information already existed at a certain time (by putting it in a merkle tree that will be published in a block), so puts a <= bound on the timestamp together these can "box in" the timestamp of the event
Exactly, it's kinda mind blowing that bitcoin can literally proof a time window.
Are you the first to think of this? Amazing I haven't heard of this anywhere.
nostr:nprofile1qqs94rjcrut2qyhzf54xgq2j44tzqkxtqe0pmu5wjp7ph75zc9gv3wspzamhxue69uhhyetvv9ujumn0wd68ytnzv9hxgtcwenq0q told me about this years ago, he called the protocol Juratum and it's actively being used for all nostr:nprofile1qqsr70lh4keezkwy9s92zm2ncpyrh7l6647ly257n6fkfgcxws0t9ncpzdmhxue69uhhqatjwpkx2urpvuhx2ue0zlzxad orders.
yes... as someone who was entangled in a court case which involved someone lying about the relative order of events many times, i appreciate this kind of thing 😀 both backdating and postdating fraud happen one wouldn't use this kind of thing for random shitposts, but for important announcements it makes a lot of sense just in case
I created the production version of OpenTimestamps in Sept 2016... right after Isis Lovecruft accused Jacob Appelbaum of rape, and after I noticed she had lied about certain details that I had first hand knowledge of. One of the first things I used OpenTimestamps for was to timestamp all my communications with Lovecruft. I strongly suspect this is one reason why even though it was damning to her false accusations against myself, she never tried to deny them in court. Ironically, in one of those damning messages Lovecruft had asked me to timestamp something for her with Bitcoin: https://archive.org/download/todd-vs-lovecruft/pond-msgs/2016-05-01.txt https://archive.org/details/todd-vs-lovecruft
Relevant: https://github.com/opentimestamps/nist-inject tl;dr: I have a long standing project that timestamps the NIST random beacon, and a bunch of other blockchains, with OTS/Bitcoin. This means that Bitcoin blocks can be proven to have been created _after_ those random beacons, giving even more evidence as to the accuracy of Bitcoin block header times. Also, I'm time-stamping Bitcoin block headers with a bunch of Roughtime servers: https://github.com/opentimestamps/restamp Again, this provides evidence proving Bitcoin blocks were create prior to those trusted Roughtime servers.
Nice, using the timechain for time stamps 👍 Universal time enough, like a stardate, no disputes about timezones and dates
I am not sure when this is useful, but it seems it will be for something.