I haven't forgotten, I've just been busy.

I did do some tests on the site though. I left 2 accounts betting at the site, one using a fixed RNG for seed and one not for 24 hours. One account did around 900k bets and the other around 700k. During that time I got a max losing streak of 19 losses at 49.5% and a max winning streak of 20 at 49.5% one the 900k account and max losing streak of 19 (twice) and a max winning streak of 17 or the 700k account. I had no skipped or repeated nonces on either account. I used a fixed verifier for the site to check thousands of bets, especially the bets where I had a losing streak and all of the bets verified correctly.

If there are skipped nonces in the bet history database for DiceBot, it's probably because the SQLite interface can't keep up with the speed of the bets when you're close to their server. Since the all time graphs draw from the database, that explains why the graph might not show the same number of bets as your nonce. I haven't had time to verify this using either your or one of my own DBs. It's also very possible that with the time it takes to draw charts with hundreds of thousands points and because it's multi threaded, the bot is suppressing errors that arises when trying to add points to the charts.