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

NC Courage II W vs Charlotte Eagles II W

USL W League · United States · 27 Jun 2026, 22:00 UTC

Final score
0 : 4
Result
Lost
Pick
NC Courage II W
Market
1x2
Model prob.
73.0%
Best price
1.52
Min odds
1.45
Stake factor
1.90

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)
q1ZXdDCc6BBlhfG/mgPaDzcfjw1DJfEgvDLmznREPXnLz3GXkysjnOHp7Sz2rcbfXBesP7PKMpoAIzugLw9u2L2LozaRZNspEawOdikJe/yaPqxIVOd/TXmQEEV7zQIkeX0RgnkEt79WesRB0E76M7S5Jp7C+bbkNKixBM7dILdthj8OczvMmd8jyZbjTJRxphSUp8Fcq2wZlIznr05m668BgrP0KeLMIpUE0Jqs3xs/rNQ6nm25QIwMZ+UZQEhDRp7zJaPAVSZS6OuWS4e/V6M7wQl/rfRLixxipOOx3AkBji2SjKDG1coECnR4d1J8ak3SYNmyBU6MjQ+9nvi8DbHm3MOS6R0j3LjCqzc/p+s=
key fingerprint sha256: 2e84f3680082caf4c575a01039524d6768e22dce34b14d44e0a6516bc82fb11b
Decrypt it & read the pick
Decryption key (released after the match)
48c299485a04154f6ed13db923f03b146aaa7835758abd525f9e197834e16ac6
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("q1ZXdDCc6BBlhfG/mgPaDzcfjw1DJfEgvDLmznREPXnLz3GXkysjnOHp7Sz2rcbfXBesP7PKMpoAIzugLw9u2L2LozaRZNspEawOdikJe/yaPqxIVOd/TXmQEEV7zQIkeX0RgnkEt79WesRB0E76M7S5Jp7C+bbkNKixBM7dILdthj8OczvMmd8jyZbjTJRxphSUp8Fcq2wZlIznr05m668BgrP0KeLMIpUE0Jqs3xs/rNQ6nm25QIwMZ+UZQEhDRp7zJaPAVSZS6OuWS4e/V6M7wQl/rfRLixxipOOx3AkBji2SjKDG1coECnR4d1J8ak3SYNmyBU6MjQ+9nvi8DbHm3MOS6R0j3LjCqzc/p+s="), c => c.charCodeAt(0));
const key  = Uint8Array.from("48c299485a04154f6ed13db923f03b146aaa7835758abd525f9e197834e16ac6".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): 48c299485a04154f6ed13db923f03b146aaa7835758abd525f9e197834e16ac6
  • IV / nonce (hex): ab565774309ce8106585f1bf
  • Ciphertext (hex): 9a03da0f371f8f0d4325f120bc32e6ce74443d79cbcf7197932b239ce1e9ed2cf6adc6df5c17ac3fb3ca329a00233ba02f0f6ed8bd8ba3369164db2911ac0e7629097bfc9a3eac4854e77f4d799010457bcd0224797d11827904b7bf567ac441d04efa33b4b9269ec2f9b6e434a8b104cedd20b76d863f0e733bcc99df23c996e34c9471a61494a7c15cab6c19948ce7af4e66ebaf0182b3f429e2cc229504d09aacdf1b3facd43a9e6db9408c0c67e519404843469ef325a3c0552652e8eb964b87bf57a33bc1097fadf44b8b1c62a4e3b1dc09018e2d928ca0c6d5ca040a747877527c6a4dd260d9b2054e8c8d0fbd9ef8bc0d
  • Auth tag (hex): b1e6dcc392e91d23dcb8c2ab373fa7eb

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