observe

My UID: 362110

I knew it.... You are spy!! Arrest him at once. . . btw the quad king you hit in January? Such amazing, very time travel...

reserved

Given that every bet starts with hashing the string made by combining server seed hash and client seed string, this should prove to be a bit of a challenge without a way to either query my own bets one at a time to test in compiler via API or maybe use canary to hijack the redirect from the verify button.... [which could be incredibly time consuming] OR maybe you guys can give us an old dump of sequential bet data with many different server/client seed pairs?