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

Haverfordwest County vs Briton Ferry Llansawel

Premier League · Wales · 11 Sept 2026, 18:45 UTC

Final score
3 : 1
Result
Won
Pick
Haverfordwest County
Market
1X2
CLV vs fair close
+2.02%
Model prob.
46.8%
Best price
2.25
Min odds
2.18
Stake factor
1.40

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)
w56vFZVrMUc3rYeI6hsBuhMpqiXA1Term7uJbDXKYnhw623q4rLdKsLqGS9ndjRiVALFpUSN/av7KgA0DKAwe3cTjMEcsKJmSbuqM9VGg7vwxZSaLNiS2Swl4Gh5ds3F/3dgLlXr62H33Z6Sz/L7N6hOtGIrBIItZspcI8TcYMCRYNr55cI2iWwfQTzS0YrG8rL6FEk4SEgLNySN/fBSo+QAZtd67Pf7bCFBNa6VmIGFvvNWMIdk4XCJBuW2i0oliYIrAZJBMnWb5T+S+NP5f2fD6nifl4f5rHg8uOZdPClUGbKglvXNgE0lZzgFXhg8BWXS5P4dslQSDMZs9pwE3zcfuRy4aPsAICws8fyf02JuRt2kv/jXfg==
key fingerprint sha256: 80fe0ecc56dde1f2d2efcb2e9dc484ef67d9805352de8801c9e19c2b68994377
Decrypt it & read the pick
Decryption key (released after the match)
7504c3e12df3ad2bc80c3c1b89d8c8cd79dfd6c6b177079556be6f1e9dbdc03c
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 F12Console), paste this, press Enter — it decrypts the exact pick shown above:

const blob = Uint8Array.from(atob("w56vFZVrMUc3rYeI6hsBuhMpqiXA1Term7uJbDXKYnhw623q4rLdKsLqGS9ndjRiVALFpUSN/av7KgA0DKAwe3cTjMEcsKJmSbuqM9VGg7vwxZSaLNiS2Swl4Gh5ds3F/3dgLlXr62H33Z6Sz/L7N6hOtGIrBIItZspcI8TcYMCRYNr55cI2iWwfQTzS0YrG8rL6FEk4SEgLNySN/fBSo+QAZtd67Pf7bCFBNa6VmIGFvvNWMIdk4XCJBuW2i0oliYIrAZJBMnWb5T+S+NP5f2fD6nifl4f5rHg8uOZdPClUGbKglvXNgE0lZzgFXhg8BWXS5P4dslQSDMZs9pwE3zcfuRy4aPsAICws8fyf02JuRt2kv/jXfg=="), c => c.charCodeAt(0));
const key  = Uint8Array.from("7504c3e12df3ad2bc80c3c1b89d8c8cd79dfd6c6b177079556be6f1e9dbdc03c".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)));

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): 7504c3e12df3ad2bc80c3c1b89d8c8cd79dfd6c6b177079556be6f1e9dbdc03c
  • IV / nonce (hex): c39eaf15956b314737ad8788
  • Ciphertext (hex): ea1b01ba1329aa25c0d537ab9bbb896c35ca627870eb6deae2b2dd2ac2ea192f677634625402c5a5448dfdabfb2a00340ca0307b77138cc11cb0a26649bbaa33d54683bbf0c5949a2cd892d92c25e0687976cdc5ff77602e55ebeb61f7dd9e92cff2fb37a84eb4622b04822d66ca5c23c4dc60c09160daf9e5c236896c1f413cd2d18ac6f2b2fa14493848480b37248dfdf052a3e40066d77aecf7fb6c214135ae95988185bef356308764e1708906e5b68b4a2589822b01924132759be53f92f8d3f97f67c3ea789f9787f9ac783cb8e65d3c295419b2a096f5cd804d256738055e183c0565d2e4fe1db254120cc66cf69c04df371fb91cb868fb00
  • Auth tag (hex): 202c2cf1fc9fd3626e46dda4bff8d77e

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

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