<<  >> (p.3)
    Author Topic: Freebitco.in provably cheating  (Read 25121 times)
    docthusinh
    Jr. Member
    *
    Offline Offline

    Activity: 225
    Merit: 4


    View Profile
    January 08, 2019, 09:58:48 AM
    Last edit: January 08, 2019, 10:46:13 AM by docthusinh
     #41

    Since acusation of the site's cheating right before 1Jan2019, the winning claim on another post popup like coming from nowhere (at least 5 nick names with $20 win). "God of luck" ilsten to you guys..lol.
    Nothing changed there, there were always many users winning $20. This topic is not claiming nobody is winning, it's claiming not enough users win.

    What i mean is the rate of win = as what you said or the mean of this thread's topic "not enough users win", please check back how many posts (per day) that won $20 prior to this acusation topic, and how many of them right after this topic. Only on the date 1 Jan 2019 alone (after this topic) there are multiple claims of $20 winning within the same day, you can check back days before that and count to see how many $20 are there per day to see if "win rate" is normal.

    To cheat on this it is too easy, since everything is on their servers even the s3.amazon... verifer is belong to them also, they can easily do it, i.e (if you are not IT related/coder then study first as if it can be done):

    If (SiteProfit <= ExpectedProfit){
        If (UserRollResult > 9997){
             Response1 = HTTP504 --- try again later site unavailable (damn it let just blame Cloudflare protection haha).
             Response2 = YourNextServerSeed;
             Response3 = Nonce;
             Response4 = YourPreviousServerSeed(modded);            
        }
    }
    else {
           GameDefault = ProvablyFairGame;
    }

    P/s: If they really want to have "Provably Fair", it is easy, let a third party company/trusted organization to host the verifier as well as before & after seeds from both what user received & what is on the roll server. The user can then verify by compare both the result with server & third party saved data. Too easy, unless they don't want to do so.
Page 2
Viewing Page: 3