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

Leeds United vs Manchester United

Premier League · England · 18 Oct 2026, 13:00 UTC

Final score
1 : 1
Result
Lost
Pick
Leeds United
Market
1X2
CLV vs fair close
-1.05%
Model prob.
40.6%
Best price
2.60
Min odds
2.51
Stake factor
1.20

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)
IaH+zUW7ao7kis7Zks//GyylHtdmlU8oUoqwUDJNvsPgew5s8rxoLv0pReWbiu4rLDRhi/PfE7myXsYt9U0tKFhh/b973E5fgruNRtd01YUZj8rHdJIUL5eYoMqzJNvU64pG7jmGBh0tklPyn5FYQfsICQVgmfYAt8M91H4pubOiS/9YjVfFQxijILXyarM3RHptJvH6yXLEqikDzeqcnkog08VbgcKeCRdCE5zATqDWKIDUPsT096orKSGrH1Es08QHXHc872FfBzgF9wA62qPOc5SxETREfamm266NT1XSLdQZt+VIDrd3DgARVV5bTVGX3c2ul6oRzdzqgMbsg7zbfaS+RTCrjC1MUj6BT2xy5IlaSbdehi1gmO0NgmdF0Dloaqon0W3k5g9Zx5jJWQixXKK7cug3Dw4YSTcbaWyP+hOwWyKxEOwb6XvgX576+kT7QGyROnm5itjuSNU2zRNomXyucrm0KWm8vD5wbzkdlNlmYmztBKfTWeTnop+dOVMp04AJkMd1YiwQey901/By4Wubw/jRZ/7PQqj68+zTF28RnGvAuCnfPVUxSo+ge2d887firnrvUdFXDCOW3j7SIURDIuzn2v8vK1AhjSVK3cH+Z5J3Bfck1h3vo3rBumKAr7wnVOgSLDV4EuuF5WfCsV4rHUfT6uP/wVMzyMiwkn7TmvGPy3Tulu0oiPMJZ56FkC2GqxKZaBb3
key fingerprint sha256: b9b696aae8f2698bb1a1d9cce2b2617d1fa94e3b8988600c8e6cf75fe20cc340
Decrypt it & read the pick
Decryption key (released after the match)
00655a5e867dc08cada1ab2ed8b457406f40799e144784f29e3de0cbe59fae67
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("IaH+zUW7ao7kis7Zks//GyylHtdmlU8oUoqwUDJNvsPgew5s8rxoLv0pReWbiu4rLDRhi/PfE7myXsYt9U0tKFhh/b973E5fgruNRtd01YUZj8rHdJIUL5eYoMqzJNvU64pG7jmGBh0tklPyn5FYQfsICQVgmfYAt8M91H4pubOiS/9YjVfFQxijILXyarM3RHptJvH6yXLEqikDzeqcnkog08VbgcKeCRdCE5zATqDWKIDUPsT096orKSGrH1Es08QHXHc872FfBzgF9wA62qPOc5SxETREfamm266NT1XSLdQZt+VIDrd3DgARVV5bTVGX3c2ul6oRzdzqgMbsg7zbfaS+RTCrjC1MUj6BT2xy5IlaSbdehi1gmO0NgmdF0Dloaqon0W3k5g9Zx5jJWQixXKK7cug3Dw4YSTcbaWyP+hOwWyKxEOwb6XvgX576+kT7QGyROnm5itjuSNU2zRNomXyucrm0KWm8vD5wbzkdlNlmYmztBKfTWeTnop+dOVMp04AJkMd1YiwQey901/By4Wubw/jRZ/7PQqj68+zTF28RnGvAuCnfPVUxSo+ge2d887firnrvUdFXDCOW3j7SIURDIuzn2v8vK1AhjSVK3cH+Z5J3Bfck1h3vo3rBumKAr7wnVOgSLDV4EuuF5WfCsV4rHUfT6uP/wVMzyMiwkn7TmvGPy3Tulu0oiPMJZ56FkC2GqxKZaBb3"), c => c.charCodeAt(0));
const key  = Uint8Array.from("00655a5e867dc08cada1ab2ed8b457406f40799e144784f29e3de0cbe59fae67".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): 00655a5e867dc08cada1ab2ed8b457406f40799e144784f29e3de0cbe59fae67
  • IV / nonce (hex): 21a1fecd45bb6a8ee48aced9
  • Ciphertext (hex): 92cfff1b2ca51ed766954f28528ab050324dbec3e07b0e6cf2bc682efd2945e59b8aee2b2c34618bf3df13b9b25ec62df54d2d285861fdbf7bdc4e5f82bb8d46d774d585198fcac77492142f9798a0cab324dbd4eb8a46ee3986061d2d9253f29f915841fb0809056099f600b7c33dd47e29b9b3a24bff588d57c54318a320b5f26ab337447a6d26f1fac972c4aa2903cdea9c9e4a20d3c55b81c29e091742139cc04ea0d62880d43ec4f4f7aa2b2921ab1f512cd3c4075c773cef615f073805f7003adaa3ce7394b11134447da9a6dbae8d4f55d22dd419b7e5480eb7770e0011555e5b4d5197ddcdae97aa11cddcea80c6ec83bcdb7da4be4530ab8c2d4c523e814f6c72e4895a49b75e862d6098ed0d826745d039686aaa27d16de4e60f59c798c95908b15ca2bb72e8370f0e1849371b696c8ffa13b05b22b110ec1be97be05f9efafa44fb406c913a79b98ad8ee48d536cd1368997cae72b9b42969bcbc3e706f391d94d966626ced04a7d359e4e7a29f9d395329d3800990c775622c107b2f74d7f072e16b9bc3f8d167fecf42a8faf3ecd3176f119c6bc0b829df3d55314a8fa07b677cf3b7e2ae7aef51d1570c2396de3ed221444322ece7daff2f2b50218d254addc1fe67927705f724d61defa37ac1ba6280afbc2754e8122c357812eb85e567c2b15e2b1d47d3eae3ffc15333c8c8b0927ed39af18fcb74ee96ed
  • Auth tag (hex): 2888f309679e85902d86ab12996816f7

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 #970807 · 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.