SlipTip

Check our record

Every graded prediction, fingerprinted before kickoff

Short version: before each game kicks off, SlipTip publishes a fingerprint of its predictions. After the game, it publishes the predictions themselves. If a single number had been changed afterwards, the fingerprint wouldn't match. So nobody, including us, can quietly edit a miss.

How it works

A fingerprint (a SHA-256 hash) is a short code worked out from a file. The same file always gives the same code, any change gives a completely different one, and the code can't be turned back into the file. So publishing it before kickoff gives nothing away, but locks the predictions in.

Each fingerprint also gets an OpenTimestamps proof, which ties it to the Bitcoin blockchain through independent servers. That proves when it existed without anyone having to trust our dates, or GitHub's.

The public repository link appears here once publishing is switched on.

Recent batches

BatchLeagueGamesFirst kickoffFingerprintFingerprint publishedPredictions
8Championship45709 Oct 2026, 19:00 UTC1c244f32d3979c78-after the games
7League Two44410 Oct 2026, 11:30 UTCf8f3836a724de20c-after the games
6League One45310 Oct 2026, 11:30 UTCa7a9476c009dcd6c-after the games
5Ligue 129009 Oct 2026, 18:45 UTCd8bda8688044d7f0-after the games
4Serie A34410 Oct 2026, 13:00 UTCfa3dbe8038b7068d-after the games
3Bundesliga27709 Oct 2026, 18:30 UTC663d1862c87750fb-after the games
2La Liga31109 Oct 2026, 19:00 UTCb1d09083aab7b140-after the games
1Premier League33010 Oct 2026, 11:30 UTCf2154d424ce87b0c-after the games

Check one yourself

Download a batch file and its .sha256 file from the repository, then on a Mac run:

shasum -a 256 batch-000001.json

The code it prints must match the first line of batch-000001.sha256, which was published before kickoff. The repository's README covers the OpenTimestamps check too.

Predictions graded before the ledger started are still in the app's Results tab, but they weren't fingerprinted, so they can't be checked this way.