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.