Houseworks - sorry, I still haven't had a chance to look into your posts yet, but I did find something that might have been exploited.

1st - I accidentally used the wrong field for the betid, meaning your roll*10000 is yoru betid, not your actual betid. While not
2nd - my roll verifier has a bug in which will result in about 30% of rolls will not verify correctly.
3rd - This is the important one. I didn't do proper research about how .nets Random class works, and I've been using Random directly to generate client seeds. I've since found out that after x numbers, Random can be predicted. This means it's possible that they(and a lot of other sites) could predict the client seed before it was sent to them and could thus choose server seeds that would lose.

My next update will address all 3 of these issues. If suddenly, after the update, people get fewer losing streaks, we can be somewhat certain that they exploited the client seed, although it's not really provable.

I cannot guarantee that this update will make it to their hosted dicebot though, so it's possible that that will never be fixed. If they are actually cheating, that bot will never get this update.