9 losses is only 1 in 512 chance.
That's not very unlikely.
I alone hit 18 loss streak once on just-dice and even then I know its luck.
But once you consider I played 10,000 games of small betting amounts.
Taking 1 in (262,144/10,000)=26.21, Suddenly my odds of this occurring was 1 in 26.21 Chance.
If a 1 in 512 event occurred here, I would of gotten, 23 losses in a row instead of 18.
The longer you play, the more its bound to occur, playing with smaller amounts just manipulates it at a slower rate.
Making 1000 bets at a small amount, or 1 bet on a large amount, turns out to be the same.
Making threads like this is only pointful, if either you found out some sort of actual cheating with proof or got something substantial, or improbable like 25 losses in a row +
or something remarkable. Then ppl would be interested just from the shock factor of such an improbable event, but still would in the end point out that each roll is independent and its bound to happen to someone. Even if it occurred 50 times in a row. Anything below is just silly and a waste of time and not worth mentioning. Unless you found
substantial evidence of some actual cheating going on from the casino house to you.
I am also saying this from a perception, I had someone win the jackpot on the slot machine twice in a row in my casino. Which is extremely improbable, but again not impossible.
As let alone, winning once is super rare, winning twice in a row, with no spin gaps, is ((super rare) ^ 2)
Hence the beauty of probably fair, where you can win at any given time, and there is no set timings.

This person hit a jackpot, and then on the second spin, he got scatters, or free spins, which pay 2X to the regular spins, and hit the jackpot again.
I was shocked myself, but again since its probably fair, this could occur at anytime.
I am quite sure the SD 50% is ripping me. I kept betting in a Martingale style over and over thinking id eventually get a win. After 9 times, no win and .80 btc shorter. This has got to be a mistake. I looked up the sd address on bchain and it was in the NEGATIVE!! This has gotta be the problem right?