CANUS research documents — how to verify these files yourself
=============================================================

Nothing here relies on trusting CANUS. Each file carries an independent proof.

1) Integrity (SHA-256): confirm the file you downloaded is byte-for-byte the published one.
   sha256sum -c <FILE>.sha256

2) RFC-3161 timestamp: an independent authority (FreeTSA) signed the file's hash at a point in time.
   openssl ts -verify -in <FILE>.tsr -data <FILE> \
     -CAfile freetsa-cacert.pem -untrusted freetsa-tsa.crt
   # 'Verification: OK' means the exact file existed no later than the token's timestamp.

3) OpenTimestamps (Bitcoin-anchored): a permanent, decentralised proof.
   ots verify <FILE>.ots        # after the calendar anchors it into a Bitcoin block

A timestamp proves the file existed AS OF the timestamp (forward-looking).
It does not, and is not presented to, prove any earlier authorship date.