We have identified the cause of this bug. User seeds were being stored 0-padded if their length did not exactly line up with a byte. The actual user seed used on that bet was 2b8022eb2dce9502365dc9ff803315901c84cbeef9ef13595 and not 02b8022eb2dce9502365dc9ff803315901c84cbeef9ef13595. We will be correcting our results page to account for the 0-padding in our storage shortly. This bug does not in any way affect the results of games. Just how we store the user seeds to later show proofs.
We are going offline now for planned hardware upgrades. The expected downtime is about 1 - 1.5 hours.
Planned hardware upgrades?? 15 minutes after a HUGE bug is reported? What are the odds? Were these "planned upgrades" planned 14 minutes before this announcement? The average person might not understand 0-padded seeds. Maybe we can get a better explanation? It seems that the timing here is too close for coincidence. How about just saying, "Thanks for reporting this bug. You really helped us out. We'll be going offline till it's fixed. Sorry for the downtime". Whatever happened with the person that discovered it originally? I haven't seen his account in chat since this happened.