That's the frustrating part, nobody can check. And the reason nobody can check is the first finding of the report.
On a real provably fair system, those dates would be verifiable by anyone. The derivation formula is public, so any player could take their own bet history from March or April, recompute their results and see if they matched the advertised odds. Because BetFury's implementation exposes none of that, all anyone has on the timeline is their word. We're not going to claim the window is wrong without data, but we can't confirm it either, and that cuts both ways.
Either way it's worth asking if you played Limbo during those dates, contact support and ask for your session records and what applies to your account.
Still a good and important catch and I fear there will be much more of those findings if you do your testing on other casinos.
I am still not over with the results concerning Betfury.
They attribute it to a configuration error, "not intentional," running May 29 to July 24, and say affected accounts are being adjusted.
We are not talking about days here and I don't know what the backends of casinos look like, but don't they have real-time updated P&L data for any game or slot or betting events? Isn't this how they can quickly identify if something is off?
I can only imagine what these backends look like, but if we assume that the configuration error had been the other way around, to the benefit of the users, how likely would it be that it goes undetected for 57 days? This is what I find very interesting. There is no setup that I can imagine, which would harm Betfury because of a configuration error while going undetected for full 57 days. It could be argued that the amounts are marginal, but they are not and this is not what they watch out for I think. They would just monitor whether there is a statistically relevant discrepancy and then similar to a traffic light switching to red.
Do you know what their monitoring tools usually look like? Would you think, realistically speaking, a configuration error paying out too much would have gone undetected that long? And if you didn't publish your report, how long could a "configuration error" like that go wrong if nobody raises the issue?
I can't believe they have nothing in place that automatically catches statistical anomalies.
