Japan vs Sweden
World Cup · World · 25 Jun 2026, 23:00 UTC
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.
spJ7/5aSP9BrU40W7gVchPk8z+r30OR3a1III9vXPnyQJUoMTIUDyfpOLiMBU+4g7mBceKIuD6tHliXOeuE+kKU3haQXgU71xBK/j1rpJSLP9iKwvI0FW8Hou6ZBLr+m5oN8PivdgGlqfR3wyfvkmD3VayNG1W3AQ3PYPMLjcy6Da++emUeF8FNkgvXOLtEaZi9P7vqaKFAS/7/LRFXRxvSpBh33Mb5E6xaibs7ycWyVuC44cR92hRtw+B4g2hXj/kgk65AfHzSZ0Oi0eHPu/sWIhN8mUiKWMaIhqliQFZjtYb+z6mLLpPHgKdNgthetPdSofe3gvC800C/t3sr2Nc5KczNHZA==
e839ec2e855cb0cbc7ea6366f106c6190cb2ead5d2e8e7cdd5faead02580a973Decrypt 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("spJ7/5aSP9BrU40W7gVchPk8z+r30OR3a1III9vXPnyQJUoMTIUDyfpOLiMBU+4g7mBceKIuD6tHliXOeuE+kKU3haQXgU71xBK/j1rpJSLP9iKwvI0FW8Hou6ZBLr+m5oN8PivdgGlqfR3wyfvkmD3VayNG1W3AQ3PYPMLjcy6Da++emUeF8FNkgvXOLtEaZi9P7vqaKFAS/7/LRFXRxvSpBh33Mb5E6xaibs7ycWyVuC44cR92hRtw+B4g2hXj/kgk65AfHzSZ0Oi0eHPu/sWIhN8mUiKWMaIhqliQFZjtYb+z6mLLpPHgKdNgthetPdSofe3gvC800C/t3sr2Nc5KczNHZA=="), c => c.charCodeAt(0));
const key = Uint8Array.from("e839ec2e855cb0cbc7ea6366f106c6190cb2ead5d2e8e7cdd5faead02580a973".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):
e839ec2e855cb0cbc7ea6366f106c6190cb2ead5d2e8e7cdd5faead02580a973 - IV / nonce (hex):
b2927bff96923fd06b538d16 - Ciphertext (hex):
ee055c84f93ccfeaf7d0e4776b520823dbd73e7c90254a0c4c8503c9fa4e2e230153ee20ee605c78a22e0fab479625ce7ae13e90a53785a417814ef5c412bf8f5ae92522cff622b0bc8d055bc1e8bba6412ebfa6e6837c3e2bdd80696a7d1df0c9fbe4983dd56b2346d56dc04373d83cc2e3732e836bef9e994785f0536482f5ce2ed11a662f4feefa9a285012ffbfcb4455d1c6f4a9061df731be44eb16a26ecef2716c95b82e38711f76851b70f81e20da15e3fe4824eb901f1f3499d0e8b47873eefec58884df2652229631a221aa58901598ed61bfb3ea62cba4f1e029d360b617ad3dd4a87dede0 - Auth tag (hex):
bc2f34d02feddecaf635ce4a73334764
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:
- Download the sealed batch file (.jsonl) and its proof (.ots) from GitHub.
- Drop both into opentimestamps.org (or run
ots verify *.ots). It replays the proof and confirms the Bitcoin block and its UTC time. - See it independently: block #955213 · 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.