You can check every claim in a proof without CloneBuster, with free tools. A store reviewer or the copy's developer can follow these steps from the export's Timestamps folder.

Hash the file

Compute the SHA-256 hash of the version's preview, or of its original file:

sha256sum "Previews/Key Art v4 preview.png"

On Windows:

certutil -hashfile "Previews\Key Art v4 preview.png" SHA256

The result must match the hash How to verify.txt lists for the version.

Find the hash in its manifest

Open the manifest.txt of the version's batch, which How to verify.txt names. Each line holds the SHA-256 of one file, then the SHA-256 of its preview, or - when it has none. Search the manifest for the hash:

grep 3f943c0b6328ffbf544a5ee6b8415b6a Batches/20261025T194250Z-0cc7/manifest.txt

The manifest names no files, so it reveals nothing about the other files of the batch.

Check the RFC 3161 timestamp

From the batch's folder, verify the authority's token against the manifest with OpenSSL. For FreeTSA, download its certificates first from freetsa.org/files/cacert.pem and freetsa.org/files/tsa.crt. For another authority, use its own certificates.

openssl ts -verify -data manifest.txt -in manifest.txt.tsr -CAfile cacert.pem -untrusted tsa.crt

OpenSSL prints Verification: OK. To read the date the authority vouches for:

openssl ts -reply -in manifest.txt.tsr -text

Check the OpenTimestamps proof

From the batch's folder, verify the Bitcoin proof with the OpenTimestamps client:

ots verify manifest.txt.ots

The client names the Bitcoin block and its date. It reads the block from a Bitcoin node; without one, drop manifest.txt and manifest.txt.ots on the verifier at opentimestamps.org.

Check a preview

A preview is checked the same way as a file: hash it, and find the hash as the second value on its version's line in the manifest. A matching preview was timestamped with the version, so it shows what the version looked like on that date.