constant on Nostr: NIP-03 specifies how to use Bitcoin Opentimestamps on Nostr events; the result is ...
NIP-03 specifies how to use Bitcoin Opentimestamps on Nostr events; the result is that you have a proof an event atleast existed at that time. If you apply this consistently, you can proof your older posts are indeed old.
The moment your key gets compromised, nothing stops an attacker creating events with bullshit timecodes, pretending to be old events from the past, eventhough they are just freshly created. But when you applied opentimestamps, the attack cant produce those (because it cant turn back (Bitcoin-)time), so i can never confincingly lie about your past, only lie about the present/future.
If you publish the fact that a key is compromized, and timestamp that; the attacker can no longer confincingly attack your future either.
The moment your key gets compromised, nothing stops an attacker creating events with bullshit timecodes, pretending to be old events from the past, eventhough they are just freshly created. But when you applied opentimestamps, the attack cant produce those (because it cant turn back (Bitcoin-)time), so i can never confincingly lie about your past, only lie about the present/future.
If you publish the fact that a key is compromized, and timestamp that; the attacker can no longer confincingly attack your future either.