Verification guide

Verification is independent: you do not need to trust us, and you do not need to own an NFT. The goal is to confirm that a file matches the referenced published source by comparing SHA-256 hashes.

What you will verify

  • The file’s SHA-256 hash matches the recorded value.
  • The file reference (e.g., IPFS CID / Arweave Tx) resolves to the same bytes.
  • The metadata includes source_reference and identifiers (dataset_id, file_id).

Step-by-step (example)

  1. Download the file from the official source or our archive copy.
  2. Compute SHA-256 locally (examples):

    # macOS / Linux

    shasum -a 256 path/to/file

    # Linux (alt)

    sha256sum path/to/file

    # Windows (PowerShell)

    Get-FileHash path\\to\\file -Algorithm SHA256

  3. Compare the output with the hash shown in NFT metadata.

Important notes

  • An NFT does not prove truthfulness. It only supports integrity verification: “does this file match the referenced source?”
  • Ownership of an NFT does not grant rights to underlying source materials. Treat it as a reference and verification artifact.
  • This project is independent and not affiliated with the US Department of Justice (DOJ).