We Source
Every run starts with curated, liquid inventory buyers actually want—no filler.
Every run starts with curated, liquid inventory buyers actually want—no filler.
Each box is professionally sealed for integrity and handled under controlled access.
Boxes are randomized before shipment to eliminate cherry-pick risk.
The checklist and manifest are published and locked with a SHA-256 hash.
Your shipment includes the checklist link(s) so anyone can independently verify.
Those same links remain live after the break—so buyers and auditors can always check our work.
With sourcing, sealing, randomization, and cryptographic hashing in place, this is the most transparent repack we’ve ever made—and it’s provably transparent, because the public checklist you receive upon shipment matches the sealed hash.
Every series checklist is posted before any show goes live. Each card and box count is visible to the world.
/series/<n>/checklist.csv /series/<n>/manifest.json
Before any break, the checklist is frozen in time with a SHA-256 hash and a local timestamp.
"sealed_at": "2025-10-02T14:00:00-07:00" "sha256": "7223e6…1abefb28"
After the break, the same files remain online for anyone—fans, buyers, or auditors—to confirm against the original hash.
Field | Value / Link |
---|---|
Series / Batch | Series 45 — Batch 10001 |
sealed_at | Oct 2, 2025, 2:00 PM PT |
json_url | GitHub JSON |
csv_url | Published CSV (Google Sheets) |
sha256 | 7223e607b4ab4af72b31a97a19603e862e9352c5e8da77cf11e71afe1abefb28 |
This is a sample entry for illustration. Live batches link to the actual sealed files with their original timestamps and hashes.
# 1) Download the published CSV curl -L -o checklist.csv "https://…/checklist.csv" # 2) Compute SHA-256 shasum -a 256 checklist.csv
:: PowerShell Get-FileHash .\checklist.csv -Algorithm SHA256 :: Command Prompt certutil -hashfile checklist.csv SHA256
If your computed hash matches our published sha256, the file is identical to what we sealed.
We do not edit sealed files. If a correction is ever needed, we publish a new revision with a new timestamp and hash. Originals remain online for audit.
The links we seal are the links we share post-show—no switch-outs, no mystery mirrors.
The combination of public checklists, timestamps, and SHA-256 means the community can verify us independently—forever.