Sigstore Verification
MLB Picks · Sunday, September 20, 2026
The Sigstore log entry below cryptographically proves that the picks file existed at a specific moment in time. The hash in Sigstore matches the SHA-256 of the picks file — meaning the file cannot have been altered since the log entry was created.
What was signed
- File
- mlb/8 picks · 2026-09-20.json
- SHA-256
- 5d365597f81ba0bf5fd64cad3cc632c1828f764250de48a54cb13f97a1a31a22
- Source
- Open raw file
Contents — 8 picks
- ·
Genoa
Parma—Genoa -0.25 @ 2.10 - ·
Manchester United
Fulham—Manchester United -0.50 @ 2.00 - ·
SEA
ARI—SEA -4.5 @ 1.98 - ·
WAS
DAL—DAL -4.5 @ 1.98 - ·
CAR
ATL—TEASER 6pt 2-leg: ATL +8.5 / JAX +8.5 @ 1.83 - ·ATL
HOU—Under 8.0 @ 1.95 - ·
DET
CWS—DET ML @ 2.00 - ·
PHI
TEN—TEASER 6pt 2-leg: PHI -1 / TB -2.5 @ 1.83
hashes match
What Sigstore logged
- SHA-256 of signed content
- 5d365597f81ba0bf5fd64cad3cc632c1828f764250de48a54cb13f97a1a31a22
- Integrated at (Rekor log time)
- 2026-09-20 16:47:48 UTC
- Log index
- #2,901,426,749
- Signed by
- github.com/jvalenza11/dailybet
.github/workflows/daily_pipeline.yml@main
What this proves, in plain English
Sigstore is a third-party transparency log. When our pipeline ran at 2026-09-20 16:47:48 UTC, it computed the SHA-256 of the picks file and submitted that hash to Sigstore. Sigstore recorded it, then notarized the entry with the GitHub Actions identity that submitted it (visible above). The entry can never be deleted or backdated.
If we changed even one character of the picks file after this entry was created, its SHA-256 would change — and the file no longer matches the hash Sigstore has on record. That's the chain: file → hash → Sigstore log entry → identity. Anyone can independently re-compute the SHA of the picks file above and confirm it matches the hash shown on this page and on search.sigstore.dev.