List Archival

[Karl]

Stefan,

> On 10/24/21, Stefan Claas <spam.trap.mailing.lists at gmail.com> wrote:
>> Another way to create new archives may be worth exploring, is
>> IPFS (https://ipfs.io) in combination with a Bitcoin-based blockchain
>> timestamping service (opentimestamps.org), which both are available
>> for free.
>>
>> It would simply mean, that whoever creates an archive hashes the
>> contained files, uses the hashsum file with the timestamping service
>> and then uploads the archive, hashfile, and timestamp to IPFS.

I'm looking through the source code of opentimestamps.org's protocol
and I see that it adds a random nonce to its file hashes, to prevent
content identification.

I'm worried about this: doesn't it mean you need access to the
associated verification file to verify a timestamp?

I'm thinking on mutating the sourcefile to instead mark content with a
public identifier, so people can compare history and see what copy was
timestamped earlier.  Not sure I'll get that far though.