Same seed, same output — byte for byte. Two roots below pin the entire collection. Anyone can recompute them from the files on this page. Nothing here is trusted on word alone.
854a1a39b7cb398dd1ec4586b0c7879d6ec319599d0f45ca2bc731400e4b17e8
0e4f172b361f535214b1a7e4b2b8741666bca5007a6817abceb4f108e5dbac96
Check one image against the record — a single command:
sha256sum 0007.png
The result must match entry id=7 in files_manifest.json.
If it does not, that image is not part of the original RBTC build.
Recompute the roots from scratch:
curl -sO https://rbtc.one/provenance/manifest.json
curl -sO https://rbtc.one/provenance/files_manifest.json
sha256sum manifest.json files_manifest.json
Both lines must equal the two roots printed above.
Or run the verifier against a local image folder:
python3 verify.py <image dir>
Exit code 0 = clean. Exit code 1 = tampered or missing. Tested against a single-pixel edit: it is caught, and the offending filename is named.