Public pick register
A 'verified' track record shouldn't require trusting whoever publishes it — including us. This register makes the check possible from the outside: if we altered any published pick, this very page would give it away.
How it works
- 1.When a pick is published, its sealed content (event, selection, market, bookmaker, odds, stake and dates) is summarised into a SHA-256 fingerprint that is never recalculated.
- 2.Every night the day is sealed: a root that summarises all the day's fingerprints together with the previous day's root. Days with no picks are sealed too, so a gap can't hide anything.
- 3.Because each root includes the previous one, editing an old pick breaks its day's root and every root after it. Rewriting the past leaves a mark.
- 4.The status column is recomputed live every time you open this page: it compares what was sealed with the picks as they are right now in the database.
| Day (UTC) | Picks | Root | Live check |
|---|---|---|---|
| 2026-08-02 | 68 | f5be32fc223b3c5b… | Intact |
| 2026-08-01 | 27 | 6e110abeeecdb257… | Intact |
| 2026-07-31 | 18 | 0ad5ad580380f3c2… | Intact |
| 2026-07-30 | 15 | 2086700f59a54a24… | Intact |
| 2026-07-29 | 13 | 4ced3faf7f2dff3c… | Intact |
| 2026-07-28 | 7 | dea681d07cdfa509… | Intact |
Picks published before 28 July 2026 carry no fingerprint: the register started that day, and signing the past after the fact would prove nothing.
To audit from outside: the public endpoint /api/transparencia returns the full chain as JSON, and /api/transparencia/{date} the fingerprints of one day with each pick's sealed data so you can recompute them.