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

Margveti 2006 vs Merani Tbilisi

Liga 3 · Georgia · 03 Sept 2026, 12:30 UTC

Final score
0 : 2
Result
Lost
Pick
Margveti 2006
Market
1X2
CLV vs fair close
-2.14%
Model prob.
40.7%
Best price
2.70
Min odds
2.51
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)
MKv6q5I9AgKKDpsJsVH79ynOyB9GnXaAJ+s0ZSEk0hjOJjZcH8LpLJ5RDguIPyJWargIezYgbx3CNiZfJNCKPtgLU3J9qqZG8lOTwlpro0b6NVwsdgVCVKQ6TNu2wxbqfO7aWZX/rAED6KHORdGnO/S9pvveJo9uT09fCdoUvYjEHyqmv3oy8UuSzWM/TSsBNFqFjbRIvLJYPMKmU1Fz3+X9mhLa2FRbG+54JIJ4WQsKNrZv7ISdpM52+U76yzvE+akzJSY88n9Uhcsc8xb/DDBhvNX/IaDPk19H4yF9okmXI9/tCNKATQVjIjGEUSmgHki+biTauujsUC6wCeuvdtJ08hy2QmshIjv7R5tA
key fingerprint sha256: 34b76cb3be8d7087521fbdd558f781a3f00d0efdb93daabf4d11b882a214b767
Decrypt it & read the pick
Decryption key (released after the match)
024b0c995ce83a27b26987c74cce8fc0f96f1dec82747e390da727f994a0c7fd
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("MKv6q5I9AgKKDpsJsVH79ynOyB9GnXaAJ+s0ZSEk0hjOJjZcH8LpLJ5RDguIPyJWargIezYgbx3CNiZfJNCKPtgLU3J9qqZG8lOTwlpro0b6NVwsdgVCVKQ6TNu2wxbqfO7aWZX/rAED6KHORdGnO/S9pvveJo9uT09fCdoUvYjEHyqmv3oy8UuSzWM/TSsBNFqFjbRIvLJYPMKmU1Fz3+X9mhLa2FRbG+54JIJ4WQsKNrZv7ISdpM52+U76yzvE+akzJSY88n9Uhcsc8xb/DDBhvNX/IaDPk19H4yF9okmXI9/tCNKATQVjIjGEUSmgHki+biTauujsUC6wCeuvdtJ08hy2QmshIjv7R5tA"), c => c.charCodeAt(0));
const key  = Uint8Array.from("024b0c995ce83a27b26987c74cce8fc0f96f1dec82747e390da727f994a0c7fd".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): 024b0c995ce83a27b26987c74cce8fc0f96f1dec82747e390da727f994a0c7fd
  • IV / nonce (hex): 30abfaab923d02028a0e9b09
  • Ciphertext (hex): b151fbf729cec81f469d768027eb34652124d218ce26365c1fc2e92c9e510e0b883f22566ab8087b36206f1dc236265f24d08a3ed80b53727daaa646f25393c25a6ba346fa355c2c76054254a43a4cdbb6c316ea7ceeda5995ffac0103e8a1ce45d1a73bf4bda6fbde268f6e4f4f5f09da14bd88c41f2aa6bf7a32f14b92cd633f4d2b01345a858db448bcb2583cc2a6535173dfe5fd9a12dad8545b1bee78248278590b0a36b66fec849da4ce76f94efacb3bc4f9a93325263cf27f5485cb1cf316ff0c3061bcd5ff21a0cf935f47e3217da2499723dfed08d2804d05632231845129a01e48be6e24dabae8ec502eb009eb
  • Auth tag (hex): af76d274f21cb6426b21223bfb479b40

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