GalaxyBets
A sponsored classic case battle funded by GalaxyBets and restricted to players signed up under my code. In classic mode the highest total drop value wins. On the result screen my player had the highest total and was paid nothing.
| Player | Own drops | Paid |
|---|---|---|
| BWife | $240.46 | $0.00 |
| noope65 | $234.64 | $475.10 |
BWife dropped $5.82 more and was paid nothing. Those two totals add to $475.10, which matches the pot on the same screen exactly, so the numbers are the site's own and they are internally consistent.
When my player raised it, GalaxyBets said the result screen was a display bug — a “frontend/backend mismatch” pulling from a stale cache — and that their internal totals were noope65 $325.23 and BWife $293.73, which would make the payout correct. They say they have patched the display and they credited my player $50 as a goodwill gesture.
Nobody outside GalaxyBets can check those figures. Only they hold the back end, so “our private numbers say we were right” is a claim, not proof. Their replacement totals also add to $618.96 — $143.86 more than the pot the site itself displayed — so one set of their own numbers has to be wrong either way.
I asked for the round-by-round breakdown that would prove it. Until a site can show me that, the only numbers I have to go on are the ones they put on the screen, and those say my player won and was paid nothing.
I ended the partnership over it. A site that shows my viewers one result and pays another is not a site I will send anyone to, and a bug that only ever gets caught when a player complains is not a bug I am willing to gamble their money on.
View the evidence →