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

San Antonio Bulo Bulo vs ABB

Liga De Futbol Prof · Bolivia · 20 Jul 2026, 19:00 UTC

Final score
2 : 1
Result
Won
Pick
San Antonio Bulo Bulo
Market
1x2
Model prob.
61.9%
Best price
1.80
Min odds
1.73
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)
zo1ScVgsBMC8Gs6wHt028YnlMjXnes8ZPV8Cswu7EH7oC0yVwXsapLJWcpp/CALMtBcqRW7WNJdPnsksB4sNYeZlh+p5jjYdytFqIymGZZv+TgD8svs9X3osx3hv/0XDm51AN4K4+Qpu4XC66g7aq6e2no73OU2NVG2vFVmChchdOUZoXWdCIPbPbK9AslMKnVIK5Clp9kCh4DPWLOm8q9jZWWyAHFhnUgPwaezimn8hKIeKEWOTz04iuxRyRos7KV/sgf4+4n3l/JGAhCD4JBl5yQJWL0PePDkVsf1KEIf3QvuWs66VqthLY+BuEfkUVqBn73V5CIt2ALTcrXmjUKck07woS2D0m5rIdmMIFP81zmLFfg==
key fingerprint sha256: 41df456a662d95a8c6864bc6bd52e34dc8b4b167f33cab6e1ebb24731a21bcfc
Decrypt it & read the pick
Decryption key (released after the match)
946494bd5654ba70f35ede7d5976fdabfe4fb9c34fa12b50bf34f3d05e62001b
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("zo1ScVgsBMC8Gs6wHt028YnlMjXnes8ZPV8Cswu7EH7oC0yVwXsapLJWcpp/CALMtBcqRW7WNJdPnsksB4sNYeZlh+p5jjYdytFqIymGZZv+TgD8svs9X3osx3hv/0XDm51AN4K4+Qpu4XC66g7aq6e2no73OU2NVG2vFVmChchdOUZoXWdCIPbPbK9AslMKnVIK5Clp9kCh4DPWLOm8q9jZWWyAHFhnUgPwaezimn8hKIeKEWOTz04iuxRyRos7KV/sgf4+4n3l/JGAhCD4JBl5yQJWL0PePDkVsf1KEIf3QvuWs66VqthLY+BuEfkUVqBn73V5CIt2ALTcrXmjUKck07woS2D0m5rIdmMIFP81zmLFfg=="), c => c.charCodeAt(0));
const key  = Uint8Array.from("946494bd5654ba70f35ede7d5976fdabfe4fb9c34fa12b50bf34f3d05e62001b".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): 946494bd5654ba70f35ede7d5976fdabfe4fb9c34fa12b50bf34f3d05e62001b
  • IV / nonce (hex): ce8d5271582c04c0bc1aceb0
  • Ciphertext (hex): 1edd36f189e53235e77acf193d5f02b30bbb107ee80b4c95c17b1aa4b256729a7f0802ccb4172a456ed634974f9ec92c078b0d61e66587ea798e361dcad16a232986659bfe4e00fcb2fb3d5f7a2cc7786fff45c39b9d403782b8f90a6ee170baea0edaaba7b69e8ef7394d8d546daf15598285c85d3946685d674220f6cf6caf40b2530a9d520ae42969f640a1e033d62ce9bcabd8d9596c801c58675203f069ece29a7f2128878a116393cf4e22bb1472468b3b295fec81fe3ee27de5fc91808420f8241979c902562f43de3c3915b1fd4a1087f742fb96b3ae95aad84b63e06e11f91456a067ef7579088b7600b4dcad79a350a724d3bc28
  • Auth tag (hex): 4b60f49b9ac876630814ff35ce62c57e

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