World Cup 2026 β€” kicks off 11 June.See predictions β†’

> trust = math

Bitcoin-anchored picks. Cryptographically un-editable.

Most tipster sites quietly edit their history β€” delete losing picks, rewrite the wording, backdate the timestamps. Bawler can't. Every morning, before kickoff, our day's predictions are snapshotted, fingerprinted, and that fingerprint is written into the Bitcoin blockchain via OpenTimestamps. Bitcoin makes the fingerprint impossible to alter without rewriting the entire chain.

If we change even one character of any past prediction, the fingerprint changes and the world can prove it. Anyone can take the snapshot file + the proof file below, run them through any OpenTimestamps client (or a Bitcoin node), and verify the predictions were locked in before the matches were played β€” offline, no trust in Bawler required.

> anchored snapshots

Daily snapshots

One row per day. Each snapshot contains every forward-looking pick we'd committed to as of 07:30 UK that morning. Bitcoin confirmation lands ~1 hour after submission; the calendar Merkle path lands within ~24 hours.

2026-06-1944 picksβœ“ Bitcoin-confirmed
sha256: 34e984d125519a08f374baf1e50202068ab237a3ff4b2ae7b0cf89dbd9fe74e1
2026-06-1843 picksβœ“ Bitcoin-confirmed
sha256: 3b978f62c9eb4ff6b61d3e61f17fb6ad5030281da6553304b0cf9b3a640f443e
2026-06-1743 picksβœ“ Bitcoin-confirmed
sha256: 0977a8d6ba5d125a346fd8030c9877e06fc3f9ac44ee89d5dc27c2754d3faa4f
2026-06-1639 picksβœ“ Bitcoin-confirmed
sha256: 5fe1831b6d3bb9b1c711de74e3067daa121b0c56d99ddb74ce0455143b99370d
2026-06-1538 picksβœ“ Bitcoin-confirmed
sha256: 074c138f10dfbfb83afd21084a0c2c0a1ec9606df6f51a859d9bb84825e3fe61
2026-06-1443 picksβœ“ Bitcoin-confirmed
sha256: 50110ac2df97b4ee19fd5ed16c1c0a65003dd4df570314848494f092c0940bba
2026-06-1346 picksβœ“ Bitcoin-confirmed
sha256: 30fb8d7bb06c063b0609a0a2eccca750722375e2c706e2972e5c77769c9e0b1f
2026-06-1248 picksβœ“ Bitcoin-confirmed
sha256: 016d557359774467f0de2367483ed2e22c1dd872bac5f2622a29d62f7db1b888
2026-06-1148 picksβœ“ Bitcoin-confirmed
sha256: 449ac6950a6beb571d51e7e3f225764dc7ea7a0351fe5eacc4526b037ca31e8a
2026-06-1048 picksβœ“ Bitcoin-confirmed
sha256: 672d1f212cc19efe65e5712d1bddc3e74ed4f21fe1da1ea6bbe67eadd472551e
2026-06-0962 picksβœ“ Bitcoin-confirmed
sha256: b42d8301ce8fef301bdc533ed201cbc7a8ac67b0b11d75f28300290a1bafdc3f
2026-06-0864 picksβœ“ Bitcoin-confirmed
sha256: 243f15899591399ad83b9129b5597579d9015a232b931b55be60b8cce200bccc
2026-06-0764 picksβœ“ Bitcoin-confirmed
sha256: 182b28d0c079d2bf1ec87784b765e3a390937042cd9a0deae5ea98de714c1df5
2026-06-0682 picksβœ“ Bitcoin-confirmed
sha256: 07701fbe66290cac58a53acec05308bea76254bc57937ea21e0928fb39aed18b
2026-06-0597 picksβœ“ Bitcoin-confirmed
sha256: f0171a0293bed775096c89ea43a51c8c0c98271c1216dfe47d981bdfc617dafa
2026-06-04107 picksβœ“ Bitcoin-confirmed
sha256: c18cdaaa2a2d99716be033dc32538c544239042682ce32f05e3df2d5fb8ef7cf
2026-06-03113 picksβœ“ Bitcoin-confirmed
sha256: 3e7be1129ab3d592873d586ea706add3a230155547ee04646b72655e6a0de132
2026-06-023 picksβœ“ Bitcoin-confirmed
sha256: 9f54f011b38555f2803ca353ca5a2836fed473e6181ccb815ff20654b0beb41c
2026-06-013 picksβœ“ Bitcoin-confirmed
sha256: 38e377363b25e790e935f8b38676d541038300acb8733b2b3df4d8bcebc702b6
2026-05-314 picksβœ“ Bitcoin-confirmed
sha256: d58382df1feb1bc19613f70a9701fb41277f593d4f355a5ffdbe445a12855092
2026-05-304 picksβœ“ Bitcoin-confirmed
sha256: 737270082a31ac22b8563938025685f8c4b68751871e637126a3eaa5a9a8d953
2026-05-293 picksβœ“ Bitcoin-confirmed
sha256: b00fd2a6308f14bff40a05f7319ffd99299b2ae3aa1dc522dbf27b4ff9f6c0d8
2026-05-283 picksβœ“ Bitcoin-confirmed
sha256: 111c8e4f417220ccf93d1822608251e2359501bc32ccccb71801ac6e87095058

> how to verify

Verify yourself in 30 seconds

  1. 1. Download both files for any date above β€” the.json(the picks themselves) and the.ots(the timestamp proof).
  2. 2. Install the OpenTimestamps client. Browser-based atopentimestamps.org, or command-line via pip install opentimestamps-client.
  3. 3. Runots verify 2026-05-28.otswith both files in the same directory. The client computes SHA-256 of the.json, walks the Merkle path inside the.ots, and asks Bitcoin: β€œwas this hash committed in block #X at time T?”
  4. 4. You get a Bitcoin block height and timestamp. If that timestamp is before the kickoff of any match in the snapshot, the prediction is mathematically locked in. We could not have edited it without rewriting Bitcoin's entire history, which costs an unspendable amount of money and would be observed by the whole world.

Why this matters. Football tipster sites can post 20 picks, delete the 15 losers, and brag about the 5 winners. With Bawler that's impossible: the snapshot includes every pick, the proof was published before kickoff, and you have both. If you ever catch us having edited a result, the receipts are in your hand β€” you can prove it to the world.