Sign in
← All matches
✅ Cryptographically verified · sealed pick #12472

Exeter City vs Fleetwood Town

League 2 · England · 24 Oct 2026, 14:00 UTC

Final score
2 : 1
Result
Lost
Pick
Fleetwood Town
Market
1X2
CLV vs fair close
-12.40%
Model prob.
39.5%
Best price
2.70
Min odds
2.58
Stake factor
1.30

Proof this pick was locked in before kickoff

The pick was encrypted before kickoff and published the moment it was sealed to Telegram and GitHub, each carrying an independent timestamp. The encrypted batch is also anchored in Bitcoin — a public record nobody, including us, can alter or back-date. After the match the key is released; decrypting that exact pre-published message reveals the pick, proving it was fixed in advance, not cherry-picked.

Encrypted pick (AES-256-GCM)
25XDWuiosP3hxsu6MQK+gNHTHGJXT/id1tBaN/ZdFOp82iShz+2r16XZL9lfFIzh2BjkH1uUshC5nbrXjU1qTefUJqH5m/CMU7Uxwea9JsIzDxG9bs+/P+pdsELM5ryJUhUGYCtJIRJJn9EHV4WJZjNnh6Sx+uIzeGRG7lKlbUFcbDlTnW49fZZhl6FLhHYOK/NlGNuDq4adqyBPB3sHkDb3qFMORt/jGJ+T7QxryFmduVMiFOLCsYu7TN1ojYj/D40YV2N37ocETbwa0mHe1C85Odl4fGoBAVLPaVjxoTECjJC3R4BRYPr+QN4JwcPPN0ZWEHzoXo47G8JSrkyZ6ScvpQ/FSgiaKcTr/Z9PB9aLBqDBfGDS3HptRHnK4ne1ZmTDtvzHy+6yVvt2s21Dw3vMwRJZiDO3WYVP+REoZ/8b1wYCc0S/XeiWjT+k9S/YKYnUDsCNLR1DbDcG+pM1y4OdosDNdvNl0RJHOnhZ3208QOHRLVmBm5h+i8+tOLuOINPrUwA8FDVmzASKrBEYGnZrwQdOoVcpbKQu0Hrl05b1sDWGpFdEMWdGykIzWB1SlJC4CdlSdhgFsZJWBuj8JTjBYrLOkMgMMKnPtBNWx/SQ/xx8VY3bZ8xtL8hR9gc3oueFyX5KZgGTjfNPO3FCuQ0WgOOLSf/O8511LJturFQ0Zq/9kGtuKYcJNIWKiMqpHxbEfkNkcIfrsHR4
key fingerprint sha256: 3c9365c2be70722587c64a2b7c1316f1cddccd3b5cd2761aa0e077bd5dbdcc78
Decrypt it & read the pick
Decryption key (released after the match)
43314071658068802412eb58f38e45eba3b7ccd2e3657e38debf6374c9885834
Decrypt in CyberChef →
Verify it yourself — paste both values, no install

The Encrypted pick above is base64( nonce[12 bytes] + ciphertext + tag[16 bytes] ), AES-256-GCM. Zero-install check: open your browser console (press F12 → Console), paste this, press Enter — it decrypts the exact pick shown above:

const blob = Uint8Array.from(atob("25XDWuiosP3hxsu6MQK+gNHTHGJXT/id1tBaN/ZdFOp82iShz+2r16XZL9lfFIzh2BjkH1uUshC5nbrXjU1qTefUJqH5m/CMU7Uxwea9JsIzDxG9bs+/P+pdsELM5ryJUhUGYCtJIRJJn9EHV4WJZjNnh6Sx+uIzeGRG7lKlbUFcbDlTnW49fZZhl6FLhHYOK/NlGNuDq4adqyBPB3sHkDb3qFMORt/jGJ+T7QxryFmduVMiFOLCsYu7TN1ojYj/D40YV2N37ocETbwa0mHe1C85Odl4fGoBAVLPaVjxoTECjJC3R4BRYPr+QN4JwcPPN0ZWEHzoXo47G8JSrkyZ6ScvpQ/FSgiaKcTr/Z9PB9aLBqDBfGDS3HptRHnK4ne1ZmTDtvzHy+6yVvt2s21Dw3vMwRJZiDO3WYVP+REoZ/8b1wYCc0S/XeiWjT+k9S/YKYnUDsCNLR1DbDcG+pM1y4OdosDNdvNl0RJHOnhZ3208QOHRLVmBm5h+i8+tOLuOINPrUwA8FDVmzASKrBEYGnZrwQdOoVcpbKQu0Hrl05b1sDWGpFdEMWdGykIzWB1SlJC4CdlSdhgFsZJWBuj8JTjBYrLOkMgMMKnPtBNWx/SQ/xx8VY3bZ8xtL8hR9gc3oueFyX5KZgGTjfNPO3FCuQ0WgOOLSf/O8511LJturFQ0Zq/9kGtuKYcJNIWKiMqpHxbEfkNkcIfrsHR4"), c => c.charCodeAt(0));
const key  = Uint8Array.from("43314071658068802412eb58f38e45eba3b7ccd2e3657e38debf6374c9885834".match(/../g).map(h => parseInt(h, 16)));
crypto.subtle.importKey("raw", key, "AES-GCM", false, ["decrypt"])
  .then(k => crypto.subtle.decrypt({ name: "AES-GCM", iv: blob.slice(0, 12) }, k, blob.slice(12)))
  .then(b => console.log(new TextDecoder().decode(b).split("\n")[0]));

Prefer a GUI? The orange button opens CyberChef pre-filled. Or split the parts yourself for any AES-256-GCM tool:

  • Algorithm: AES-256-GCM
  • Key (hex): 43314071658068802412eb58f38e45eba3b7ccd2e3657e38debf6374c9885834
  • IV / nonce (hex): db95c35ae8a8b0fde1c6cbba
  • Ciphertext (hex): 3102be80d1d31c62574ff89dd6d05a37f65d14ea7cda24a1cfedabd7a5d92fd95f148ce1d818e41f5b94b210b99dbad78d4d6a4de7d426a1f99bf08c53b531c1e6bd26c2330f11bd6ecfbf3fea5db042cce6bc89521506602b492112499fd10757858966336787a4b1fae233786446ee52a56d415c6c39539d6e3d7d966197a14b84760e2bf36518db83ab869dab204f077b079036f7a8530e46dfe3189f93ed0c6bc8599db9532214e2c2b18bbb4cdd688d88ff0f8d18576377ee87044dbc1ad261ded42f3939d9787c6a010152cf6958f1a131028c90b747805160fafe40de09c1c3cf374656107ce85e8e3b1bc252ae4c99e9272fa50fc54a089a29c4ebfd9f4f07d68b06a0c17c60d2dc7a6d4479cae277b56664c3b6fcc7cbeeb256fb76b36d43c37bccc112598833b759854ff9112867ff1bd706027344bf5de8968d3fa4f52fd82989d40ec08d2d1d436c3706fa9335cb839da2c0cd76f365d112473a7859df6d3c40e1d12d59819b987e8bcfad38bb8e20d3eb53003c143566cc048aac11181a766bc1074ea157296ca42ed07ae5d396f5b03586a45744316746ca4233581d529490b809d952761805b1925606e8fc2538c162b2ce90c80c30a9cfb41356c7f490ff1c7c558ddb67cc6d2fc851f60737a2e785c97e4a6601938df34f3b7142b90d1680e38b49ffcef39d752c9b6eac543466affd906b6e2987093485
  • Auth tag (hex): 8a88caa91f16c47e43647087ebb07478

Any standard AES-256-GCM tool returns the exact same pick — the algorithm is a public standard.

The pick is the first line of the decrypted text. Records sealed from 24 September 2026 are followed by a line break and spaces up to a fixed size, so every encrypted pick has the same length and its size reveals nothing about the selection before the key is published. The commitment hash is sha256(first line + key), exactly as before.

How to verify the Bitcoin timestamp yourself

Bitcoin doesn't store the pick — it stores a 32-byte fingerprint (SHA-256) of the encrypted batch, via OpenTimestamps. That fingerprint is frozen in a public block nobody can alter or back-date. You can't spot it by eye on a block explorer (a block holds thousands of unrelated transactions) — you verify it with the .ots proof and any OpenTimestamps tool:

  1. Download the sealed batch file (.jsonl) and its proof (.ots) from GitHub.
  2. Drop both into opentimestamps.org (or run ots verify *.ots). It replays the proof and confirms the Bitcoin block and its UTC time.
  3. See it independently: block #972375 · anchoring transaction (its OP_RETURN holds the commitment). The block's Timestamp is when it became permanent.

Note: Bitcoin anchoring lands ~30–60 min after sealing, and a block's timestamp is miner-set (approximate). So the exact “before kickoff” proof is the seal time above — timestamped instantly by Telegram/GitHub — while Bitcoin is the independent, un-forgeable anchor of permanence.