opentimestamps-client

if you sign your commits, you should also consider timestamping your commits. I use OpenTimestamps for this. Docs and some rationale here: https://github.com/opentimestamps/opentimestamps-client/blob... from the doc: > My signing keys (e.g. blog or Qubes code signing keys) do not have expiration dates. This is not laziness. There is a fundamental problem with using an expiration date on keys used for code signing (e.g. git tag -s), because it is unclear what the outcome should be when one verifies some old code (written and signed when the key was still valid) in the future when the key has already expired? > Naturally we would like the old code, written and signed when the key was still valid, to continue to verify fine also in the future, after the key expires (and the developer passed away, perhaps). However, it is very problematic to

> Hashing the data that's added to the archive and then putting the hash in the blockchain would reasonably prove the data in the archive hasn't been modified at a later date. Here have yourself a timestamp https://petertodd.org/2016/opentimestamps-announcement https://github.com/opentimestamps/opentimestamps-client pip3 install opentimestamps-client ots stamp myfile.txt

> I don’t have a record of every signature I made Use opentimestamps git wrapper. Each commit is signed and timestamped. When you revoke your key, the original signed commit is still timestamped, presumably before your revocation date. https://github.com/opentimestamps/opentimestamps-client https://opentimestamps.org/

No Javascript version: https://raw.githubusercontent.com/opentimestamps/opentimesta... https://archive.org/download/opentimestamps-calendar-backups... https://ia801509.us.archive.org/13/items/opentimestamps-cale... https://github.com/opentimestamps/opentimestamps-client https://alice.btc.calendar.opentimestamps.org/calendar/ https://bob.btc.calendar.opentimestamps.org/calendar/ https://finney.calendar.eternitywall.com/calendar/