-
@ Constant
2024-10-12 15:27:20The following is a combination of a series of posts on Bitcoin Timestamps on Nostr that were originally made between 2024-10-11 02:10:29 GMT & 2024-10-12 13:57:20 GMT.
To everyone whose phone i have harassed with my nfc card that therefor now see this message: This is actually a forrest picture channel https://image.nostr.build/2df97ead480b057df1a9a622f12c6209d82cfd4cc7e4e3f9254267a7199ec46e.jpg
https://image.nostr.build/74358001cab02b32e4c6bb4af04714cb6f4ce69b190514dad330f52c397c665f.jpg
Amethyst now lets you create NIP-03, Bitcoin based Open Time Stamps.
Unfortunatly i cut off the timestamp that is part of the original version of this picture (because it is ugly), so you will never know this foto was taken on july 12, 09:54. https://image.nostr.build/4f96ab676d551e4866b1d4856a8db756b53e094e17ba3c9bb75ff24ecd54839b.jpg
forestr
Everyone can timestamp everything at any time; the time-proof is valid regardless of who initiates its creation.
For example, at 01:37 on oct 12, I signed this kind 1040 event: nostr:nevent1qqsyxw4l6030ugpufwr820leasv630c3an87pcm9sp0uek22gtwzsmszyp02geyqgka3lu3zv4wa6dhxmnkacs6epsnqjrzgd0hn3m69pkjm6qcyqqqqgyqrapa2r
Which contains a proof that this kind 1 event can be tied into bitcoin block 865239: nostr:nevent1qqsd3u78nkjn78tcfcqjmrclxns9667chycmlzxxgnxxvd26yw7z85sppemhxue69uhkummn9ekx7mp0qgs2jy6jwcfsyqmpfp3tjggt505n4vnemqn3jcf6t3qw2e426mg7k9crqsqqqqqp277t4j
And the timestamp of block 865239, is 00:02 on oct 12. The event itself claims it was signed 22:11 on oct 11; this may be a lie still, but at least it was not signed much more than 1 hours and 51 minutes later.
Aside from all these time related dates, the described lunch date could also just be a complete fabrication of course; at the very least the pictures correspond with the stated dishes
woodpeckestr
https://image.nostr.build/9e12ea3eb66e2b686539abe9349b4d205b2ccde17bdbc30c65b9ad5953ace901.jpg
Timestamps only give very weak indications of truth; but they are really good at catching certain lies.
Take for example the following note: nostr:nevent1qqszw6fwhl28y974y9vjw6ej63xdax4gu5rf8fw52jqkf8x5kk98skgppamhxue69uhku6n4d4czumt99upzqpuvjsr4gjkpxf5jacv3pgpy8x2c4czgwu23xsh2jmztdv66f863qvzqqqqqqyg7gvfg
your client may have a hard time loading it, depending on when you look at this post. This is because the event claims to be signed at Thu Oct 17 2024 03:00:00 GMT. Given it is currently Oct 12, this is a blatant lie, and relays tend to not accept this event because of this.
But, what happens in 5 days? As soon we pass that 3 o’clock mark on oct 17, how would any outsider know that this event was not signed at that time, but 5 days earlier? It is easy to catch these sort of lies when you are present in real time and pay attention, but if you arrive after the fact, NIP-03 timestamps allow you to identify such a lie for certain if adequate proof exists.
And in this case, this proof does exist! Because I timestamped this event already, tying it into block 865274, which was mined around 05:31, oct 12. Which results in the following screenshot of Amethyst: https://image.nostr.build/01ca55a150444cab7b3025b70f9c1dab7c1382a3d54ed3faefaa722ee2f208aa.jpg
The app claims the event was posted ‘now’ (probably because it simply interprets any date in the future as ‘now’), but also tells me a timestamp exists that is 9 hours old.
Now this particular type of lying (pretending to be in the future), it not all that interesting, I was just curious. But it does go to show that you should not trust the time the event claims it was signed, because it is trivially easy to lie about it.
Say hello to my fren btw: https://image.nostr.build/ec4b37e2d259015f1a3b9b39b4163c98ceab56ead83bd08ce82350a061c7814c.jpg
Thus concludes my forrest picture presentation for now.
Time, such a fascinating thing, inescapably ever moving onwards. Winter is coming: https://cdn.satellite.earth/6761a5ff81c5a5ac3daa74e0d33cddf4912b770a13d272b933499839b5b03757.mp4