Just want to share this to anyone who think iz money :

https://imgur.com/a/muLrZuCSo thats 17 miss in a row or a 99.998 chance of that not happening.

It can happen ofc but on a total of around 50k spins the chance is smaller than 1 in a 10milions. So i will end with this site cuz you cant claim bonuses if you dont play multiply BTC and if that is my luck no point to play

I verify every single bet I make, automated on my end, just looked at my stats now and have done over 800 000 multiply bets, and of those 800 000 verficiations, I think only 4-5 failed verification probably due to some network error (and they were small bets and some of them I had won.)

The house edge is very high indeed but after verifying all these bets and the way that they designed this, it's impossible for them to cheat on the outcome, which would require them to find a sha256 collision within milliseconds. AFAIK there is no known Sha256 collision and if freebitco.in has the capability to find sha256 collisions under a second, it would have been the absolute king of bitcoin mining - they'd produce blocks as they please.

They could at worst produce network errors at the "right" time for very big bets which I have never done.

According to my calculations running a 17 loss on 2x bets has a chance of 0.0017% at the **start** of every sequence. That could be rounded to 1 time in every 50 000 bets, but since a new bet is independent of the previous bet, the chance of this 17 loss happening in a series of 50 000 bets is much higher than 1 in 50 000. If you calculate the odds of that happening here:

https://www.sportsbookreview.com/picks/tools/streak-calculator/You'll see that a 17 loss sequence happening inside of a 50 000 bet sequence is slightly more than 33%.

It's also mathematically proven that a negative expectancy game over the long run will always end up with a loss, no matter what the betting method. That's how it works and freebit makes money. But I keep playing because I may stop at some lucky point!

LIES. You didnt automated anything at all ____removed-self-promotion________ and I know damn well how much latency trying to verify 800k would add to the process (which is precisely why I dont do it) WITHOUT verification the best you can do is 3.5 bps. Adding verification cuts that in half if you do it locally or more than 90% if you use an online tool. So lets just say you try this locally and give you the benefit of the doubt and say you miraculously achieve 2bps (but i think its likely closer to 0.5bps since i dont believe u have the skill to do it locally judging by the huge over exaggeration).

So 800000 /2 == 400000 seconds. Do you even realize how many days that is? Google it. I rest my case You lie. Nice noob account btw. How convenient.

Do you rest your case so often for unnecessary things like this? You are so wrong that it's not even funny.

I made a total multiply auto-bet replacement, currently unable to monetize it because it's a chrome extension and I'm exploring ways to distribute it. I have been using it since November 2017 (just checked the local git history), and 4-5 more people have been using it. I once posted an image of the ui here but it got deleted.

The auto-bet logic is is programmed from scratch and I do automatic bet verification, because it works as an extension in the freebitco page and prepares the bet http-request and the random string also, verification is done locally.

Here's the portion of the code that does the verification:

BetVerifier: class {

constructor(clientseed, serverseedhash, nonce) {

this.ClientSeed = clientseed;

this.ServerSeedHash = serverseedhash;

this.Nonce = nonce;

this.ServerSeed = null;

this.Roll = null;

}

Verify(serverSeed, roll) {

serverSeed = serverSeed || this.ServerSeed || "stand-in";

var testRoll = roll || this.Roll || "0";

var server_seed_hash = CryptoJS.SHA256(serverSeed).toString(CryptoJS.enc.Hex);

return (this.ProduceRoll(serverSeed) == testRoll) && (server_seed_hash == this.ServerSeedHash);

}

ProduceRoll(serverSeed, clientSeed, nonce) {

serverSeed = serverSeed || this.ServerSeed || "MoCKuPsERVErsEed";

clientSeed = clientSeed || this.ClientSeed || "MoCkUpclIentseED";

nonce = nonce || this.Nonce || "1";

var string1 = nonce.concat(":", serverSeed, ":", nonce);

var string2 = nonce.concat(":", clientSeed, ":", nonce);

var hmac512 = CryptoJS.HmacSHA512(string1, string2).toString(CryptoJS.enc.Hex);

var string3 = hmac512.substring(0, 8);

var number = parseInt(string3, 16);

return (Math.round(number / 429496.7295)).toFixed(0);

}

},

The verification is definitely not the bottleneck! I just checked this and it takes 1-2 milliseconds to run the "produceroll" function. You can test it too if you are so inclined to prove me wrong.

So don't bash me just to promote yourself and link to your wonderful bot, you are being very rude and condescending without any base. I'm hesido on every avenue of the internet and you can check that I program javascript. Since you have excellent deductive skills, it should be easy for you to understand that this is a real account of a real person whose life does not revolve around freebitco.in.

Edit: Since the issue of time was derailed by your extensive knowledge in the time taken for producing sha hashes, I forgot to address it. I indeed can make at 2-3 bets per second, it's due to network latency. And it does mean it took a lot of time to stack up 800 000 rolls, it means I spent more than 3-4 days in total betting in the course of a year, but that's dwarfed by the amount of Overwatch I used to play, for example, that kind of time is nothing that's out of reach. (The betting is auto but it pauses for me to set the course if it gets above a certain preset bet amount, so I may not necessarily sit in front of it)