Operator response · No replyThe report in 30 seconds
UnverifiableThe disputed bets can’t
be independently verified.
Targets and seeds are absent for all 62 disputed bets. The outcome field is null on 61 of 62.
Not provably fairNo independently verifiable
lock on the outcome.
A fresh operator seed, no published chain, nonce 0, and a fixed 2023 Bitcoin block.
No claim that any outcome was manipulated. Under this design, manipulation can be neither proven nor disproven.
01The Timeline — Three Games Named “Slide”
One on-screen name. Three different games.
tequ_slider
Third-party provider · Tequity
Bet history + results served
- Bet history
- SERVED
- Results
- SERVED
slide-vip
Winna in-house · private · gated
No bet history · no results
- Bet history
- MISSING
- Results
- NOT SERVED
slide
Winna in-house · public
Every bet verifiable
- Seed chain
- PUBLISHED
- Round proof
- VERIFIABLE
The sequence is record, not insinuation: wins and losses prove nothing by themselves. What each game could prove is where they differ.
02The VIP Slide — No Verifiable Lock on the Outcome
02 / VIP SLIDE · SEED RECOMPUTATION
The seeds reproduce the results.
That does not prove fairness.
With the client seed already public and nonce fixed at 0, a matching result cannot show when the operator selected its seed.
Three charged results reproducedfd5c47777a3bdac3… → 2.38×604162685c66487f… → 2.33×933b74433ef7a313… → 2.69×Exclusive fit: Limbo formula · edge 0.98 · block 779588
Fixed · 2023 blockFrozen at 0None foundNot verifiable
Lock A · player entropy
- The operator first commits to SHA256(serverSeed).
- The player can then change the client seed at will.
- A nonce advances every bet. The operator commits blind.
Lock B · chain + future entropy
- Generate a hash chain and publish its terminus in advance.
- Fix the client seed using a then-unmined Bitcoin block.
- Each round’s seed must hash to the terminus in exactly its round number of steps.
Three seeds. No links within 11,000,000 SHA-256 iterations in either encoding. No independently verifiable commitment binding the operator before the bets.
03The Missing Bet History
VIP Slide · 15–16 May
Result: null on 61 of 62. The win stores only “6” = payout ÷ stake.
Target: absent for all 62 disputed bets.
Seeds: absent for all 62 disputed bets.
Public Slide · $1 control
Result: 1.851 recorded against a 2.00× target.
Seeds: served through the fairness modal.
Commitment: the seed reaches the published terminus in 167,169 hashes — its round number.
COMPLETE SWEEP · EVERY DISPUTED BET
No target. No seeds.
No independently verifiable bet record.
61 null outcome fields1 payout ratio only (“6”)Targets and seeds absent on all 62
| CAPTURED FINDING | EVIDENCE STATUS |
|---|---|
01 No independently verifiable lock on the outcomeFresh operator seeds · nonce 0 · fixed 2023 block · no published chain | Not provably fair |
02 The 62 disputed bets cannot be independently verifiedTargets and seeds absent · 61 null outcomes · one bare payout ratio | Unverifiable |
04Right of Reply — No Response
What Winna needs to produce
The door stays open. Any response will be reviewed and the outcome published just as prominently either way.
For each of the 62 bets: ID, timestamp, stake, target, result, server seed and pre-bet hash.- What independently verifiable commitment governed VIP Slide on 15–16 May?
- Can Winna publish a commitment from before 15 May?
- Can records from the time, vouched for independently, show the seeds were fixed before the bets?
- Why do Winna’s systems serve no outcome data for exactly the disputed bets?
05Verify It Yourself · Scope
05 / OPEN DATA & REPRODUCIBLE ANALYSIS
Run the investigation yourself.
Check Winna’s public API records, the on-chain inputs and the disclosed seeds. Our clean-room verification script uses only the Python standard library; no player code was reused.
verify_winna_slide.pyPYTHON · NO DEPENDENCIES# Disputed VIP bets · the configuration that reproduces the charges
limbo(seed, block779588, nonce=0, edge=0.98)
fd5c47777a3bdac3… → 2.38× = charged
604162685c66487f… → 2.33× = charged
933b74433ef7a313… → 2.69× = charged
# Public Slide · $1 control
167,169 hashes to the terminus = round number
HMAC_SHA256(roundSeed, blockHash) → 1.85×Swipe code horizontally ↔
Conclusion & scope
What players should know
Winna VIP Slide · 15–16 May 2026
| ASSESSMENT | OBSERVED RESULT | VERDICT |
|---|---|---|
Pre-bet commitment | No independently verifiable lock on outcomes | Not provably fair |
62 disputed VIP bets | Targets and seeds absent · 61 null outcomes | Unverifiable |
Public Slide · $1 control | Seed chain and result independently verified |  Verified control |
INTERPRETATION
On the evidence available to us: not provably fair, and not independently verifiable.
Final verdict. The VIP Slide ran with no independently verifiable lock on the outcome, and the 62 disputed bets cannot be verified by anyone today — not by the player, not by the public, not by Winna’s own systems. On the evidence available to us: not provably fair, and not independently verifiable.
This report is not a finding that any wager was manipulated. It is a finding that the system, as documented by the available evidence, does not provide the cryptographic guarantees an independent third party would need to verify that manipulation could not have occurred.
SCOPE OF THE FINDINGS
Scope and consent: this report assesses design and verifiability, on the record served by Winna’s own systems and public documents; conclusions are limited to evidence independently available to us, with live checks last verified 28 July 2026 (UTC). Material from the player’s case file is labelled as such throughout. The player consented to publication of his betting data. Winna is invited to correct any fact in it — its response, whenever it arrives, will be reviewed and appended with a public change log (section 4).
Live checks last verified 28 July 2026 (UTC). Winna is invited to complete or correct the record.