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

Viktoria Plzen vs Crvena Zvezda

Europa League Qualifiers · UEFA · 27 Aug 2026, 17:00 UTC

Final score
1 : 1
Result
Lost
Pick
Viktoria Plzen
Market
1X2
CLV vs fair close
+4.70%
Model prob.
50.0%
Best price
2.12
Min odds
2.04
Stake factor
1.80

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)
FKZYIroW4NZRlRbijejwug4qijfN0ol6hr+rxV8917n8eyRXti527FQjaOo7Th7IyG8yTSuAc4tz5Lp32RlQAHXTKiMZBkDI+Qpc7/xTUb6aYYALd2diVEtZLIotel/g48FuypHmTC6Nvh+ZAbUOn7tYW1pXCFKlBHzT8Xbdbx7CkSj4IfgsIs2qZB8H7zR2enWYLbgzHhCtqD+Z4Btrxc9tA+ocC253jokU5Z7WRv6bdM7DUhlZ4/3tsDvyHHXEhTWxi9d+GGmB6l6imP4yQM/hnYUzDo+KN42PGu97U/czDwgA1tvTA6qciDTJsjZpYmvYE8USL91EC8KomabBS8o8yYVEi5ixZfZMXjKZBzs=
key fingerprint sha256: 97c72947398431c14fff5aad5bf9137209d9893e6b5aa60fc0949a50e1de2dba
Decrypt it & read the pick
Decryption key (released after the match)
a0119c87d36674199325b7e3e70cd9583d2adc2747cd1b6e1da3792d7e28716f
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("FKZYIroW4NZRlRbijejwug4qijfN0ol6hr+rxV8917n8eyRXti527FQjaOo7Th7IyG8yTSuAc4tz5Lp32RlQAHXTKiMZBkDI+Qpc7/xTUb6aYYALd2diVEtZLIotel/g48FuypHmTC6Nvh+ZAbUOn7tYW1pXCFKlBHzT8Xbdbx7CkSj4IfgsIs2qZB8H7zR2enWYLbgzHhCtqD+Z4Btrxc9tA+ocC253jokU5Z7WRv6bdM7DUhlZ4/3tsDvyHHXEhTWxi9d+GGmB6l6imP4yQM/hnYUzDo+KN42PGu97U/czDwgA1tvTA6qciDTJsjZpYmvYE8USL91EC8KomabBS8o8yYVEi5ixZfZMXjKZBzs="), c => c.charCodeAt(0));
const key  = Uint8Array.from("a0119c87d36674199325b7e3e70cd9583d2adc2747cd1b6e1da3792d7e28716f".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): a0119c87d36674199325b7e3e70cd9583d2adc2747cd1b6e1da3792d7e28716f
  • IV / nonce (hex): 14a65822ba16e0d6519516e2
  • Ciphertext (hex): 8de8f0ba0e2a8a37cdd2897a86bfabc55f3dd7b9fc7b2457b62e76ec542368ea3b4e1ec8c86f324d2b80738b73e4ba77d919500075d32a23190640c8f90a5ceffc5351be9a61800b776762544b592c8a2d7a5fe0e3c16eca91e64c2e8dbe1f9901b50e9fbb585b5a570852a5047cd3f176dd6f1ec29128f821f82c22cdaa641f07ef34767a75982db8331e10ada83f99e01b6bc5cf6d03ea1c0b6e778e8914e59ed646fe9b74cec3521959e3fdedb03bf21c75c48535b18bd77e186981ea5ea298fe3240cfe19d85330e8f8a378d8f1aef7b53f7330f0800d6dbd303aa9c8834c9b23669626bd813c5122fdd440bc2a899a6c14b
  • Auth tag (hex): ca3cc985448b98b165f64c5e3299073b

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