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

Bideford vs Falmouth Town

Southern League Division 1 · England · 27 Oct 2026, 19:45 UTC

Final score
1 : 2
Result
Lost
Pick
Bideford
Market
1X2
CLV vs fair close
+8.31%
Model prob.
34.9%
Best price
3.10
Min odds
2.93
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)
H6w5SiZ2hOKFJGeT525+mtvgaiaaUlVRhD2gGi0R4y20vcz/ej5dFW8b3xPQkGEXEXL4bDbWeE+7iOYRgCx7lNbr7COburUR1xa90fk7d2yG02AGeWqbZ+ZE5TGACm3CKjlxhM8z0CbpFO10KAGQ2OKUjDOh7+IsGueauUUEnfJ/JNZDqlGFpJYmHg1UcS+lVvZNcacYBoK4shTA4U5cerRuDSOca8VAvtjyV/l6RtGxoZ2s0SjsuJxb93BtLIilXaJz+8MiKs4s1EMCEXAN+kuxq7Vjxto2Pi+eMgC2Ct4kG2ZcydXXgkmW/7UjsXQ/JpYLf9qGz7wntIVGQGn1b4oBij1yIlwhJeg98cXgORxr3tyHFXncOfFM9hwI3hKcYUEfKY564MD524tCgEmoqksguNBN33BUAfa+jVQTnhUNmZJductegzUmopoUgUm1a37xu/mzRre0UPofZpuxoRjJcY7CW35zBzCkq1MEMBPyOQWetkj6tD2KiGk4YMtxp5WstOFO/YazPGUK4lGCwAIKLkabbTshsoPl488cTw1kBEzwk1f42b6wZsg4jza0EJ7AAx79ucxHD1gnZCshg+R8nyyCanHID6FnWU881OwEG9t83tGasLqDicsNqM/4LWkmhhiDniUpz7C1iMNC6z4PMZPxR8Jk6kpSXkBWXsT8hst84d/neNp4u422NSVaJen1O6TNPxIMDzit
key fingerprint sha256: 532a26926ee1abc7dc2b3d6b403d3271c39cb75712e039d89842f0fc2eb20df8
Decrypt it & read the pick
Decryption key (released after the match)
8ed7b8e82e68efad1a60780f1a0f07c53728ac6a70c8010b1b289b1a1d508a6c
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("H6w5SiZ2hOKFJGeT525+mtvgaiaaUlVRhD2gGi0R4y20vcz/ej5dFW8b3xPQkGEXEXL4bDbWeE+7iOYRgCx7lNbr7COburUR1xa90fk7d2yG02AGeWqbZ+ZE5TGACm3CKjlxhM8z0CbpFO10KAGQ2OKUjDOh7+IsGueauUUEnfJ/JNZDqlGFpJYmHg1UcS+lVvZNcacYBoK4shTA4U5cerRuDSOca8VAvtjyV/l6RtGxoZ2s0SjsuJxb93BtLIilXaJz+8MiKs4s1EMCEXAN+kuxq7Vjxto2Pi+eMgC2Ct4kG2ZcydXXgkmW/7UjsXQ/JpYLf9qGz7wntIVGQGn1b4oBij1yIlwhJeg98cXgORxr3tyHFXncOfFM9hwI3hKcYUEfKY564MD524tCgEmoqksguNBN33BUAfa+jVQTnhUNmZJductegzUmopoUgUm1a37xu/mzRre0UPofZpuxoRjJcY7CW35zBzCkq1MEMBPyOQWetkj6tD2KiGk4YMtxp5WstOFO/YazPGUK4lGCwAIKLkabbTshsoPl488cTw1kBEzwk1f42b6wZsg4jza0EJ7AAx79ucxHD1gnZCshg+R8nyyCanHID6FnWU881OwEG9t83tGasLqDicsNqM/4LWkmhhiDniUpz7C1iMNC6z4PMZPxR8Jk6kpSXkBWXsT8hst84d/neNp4u422NSVaJen1O6TNPxIMDzit"), c => c.charCodeAt(0));
const key  = Uint8Array.from("8ed7b8e82e68efad1a60780f1a0f07c53728ac6a70c8010b1b289b1a1d508a6c".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): 8ed7b8e82e68efad1a60780f1a0f07c53728ac6a70c8010b1b289b1a1d508a6c
  • IV / nonce (hex): 1fac394a267684e285246793
  • Ciphertext (hex): e76e7e9adbe06a269a525551843da01a2d11e32db4bdccff7a3e5d156f1bdf13d09061171172f86c36d6784fbb88e611802c7b94d6ebec239bbab511d716bdd1f93b776c86d36006796a9b67e644e531800a6dc22a397184cf33d026e914ed74280190d8e2948c33a1efe22c1ae79ab945049df27f24d643aa5185a496261e0d54712fa556f64d71a7180682b8b214c0e14e5c7ab46e0d239c6bc540bed8f257f97a46d1b1a19dacd128ecb89c5bf7706d2c88a55da273fbc3222ace2cd4430211700dfa4bb1abb563c6da363e2f9e3200b60ade241b665cc9d5d7824996ffb523b1743f26960b7fda86cfbc27b485464069f56f8a018a3d72225c2125e83df1c5e0391c6bdedc871579dc39f14cf61c08de129c61411f298e7ae0c0f9db8b428049a8aa4b20b8d04ddf705401f6be8d54139e150d99925db9cb5e833526a29a148149b56b7ef1bbf9b346b7b450fa1f669bb1a118c9718ec25b7e730730a4ab53043013f239059eb648fab43d8a88693860cb71a795acb4e14efd86b33c650ae25182c0020a2e469b6d3b21b283e5e3cf1c4f0d64044cf09357f8d9beb066c8388f36b4109ec0031efdb9cc470f5827642b2183e47c9f2c826a71c80fa167594f3cd4ec041bdb7cded19ab0ba8389cb0da8cff82d69268618839e2529cfb0b588c342eb3e0f3193f147c264ea4a525e40565ec4fc86cb7ce1dfe778da78bb8d
  • Auth tag (hex): b635255a25e9f53ba4cd3f120c0f38ad

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