▄■▀■▄ 🌟BITVEST.io🌟 💰WIN BY 🔶PLAY 📈INVEST➡🔺🎲🎰🔲

Yes, it should never occur again. Also, it doesn't prevent divesting. Only investing, playing, and withdrawals are locked.

Quote from: Zodiac1233 on January 17, 2016, 12:35:04 AM

Yes, it should never occur again. Also, it doesn't prevent divesting. Only investing, playing, and withdrawals are locked.

really? would this lead the people to discontent this site due to the locked withdraws? you just wish people to lose? not a good sign to others including yours. Roll Eyes

Quote from: lottery248 on January 17, 2016, 12:38:59 AM

Quote from: Zodiac1233 on January 17, 2016, 12:35:04 AM

Yes, it should never occur again. Also, it doesn't prevent divesting. Only investing, playing, and withdrawals are locked.

really? would this lead the people to discontent this site due to the locked withdraws? you just wish people to lose? not a good sign to others including yours. Roll Eyes

The system only triggers when the site thinks a user's balance isn't what it should be. Any accounts made within the past month onward are unaffected by this auditing bug, as well as <1% of older accounts being effected. The audit errors are mostly caused from less data logging from the early days of Bitvest. The withdrawal "locking" only makes it so the withdrawal requires manual review instead of processing automatically.

Quote from: Zodiac1233 on January 17, 2016, 12:46:05 AM

Quote from: lottery248 on January 17, 2016, 12:38:59 AM

Quote from: Zodiac1233 on January 17, 2016, 12:35:04 AM

Yes, it should never occur again. Also, it doesn't prevent divesting. Only investing, playing, and withdrawals are locked.

really? would this lead the people to discontent this site due to the locked withdraws? you just wish people to lose? not a good sign to others including yours. Roll Eyes

ill make sure to explain this to new users who don't understand it.

My current build im using recommended starting is 60k plus but ive built to 0.01 with 20k sats.

Code:

var bet = {base: 0.0000001, current: 0.0000001}; //Modify these values to change your base bet
var placeBet=function(){
	$.post( "action.php", { prizes: "1000,16.9,0,0,17,0,0,0,0,0,0,0,17,0,0,16.9,1000", 
						token: token, 
						secret:0,
						bet:bet.current,
						bits:null,
						user_seed:makeid(),
						act:"play"
						})
  .done(function( data ) {
	if (!data.success){
		alert(data.msg);
		return 0;
	}
    
	var win=data.game_result.win;
	console.log( win, data.data.balance );
	if (win>bet.current){
		bet.current=bet.base;
		if (bet.current<bet.base) bet.current=bet.base;
	}else if (win<bet.current){
		bet.current=(bet.current-win)*1.1; //Modify this value in order change the on loss multiplier
	}
	//console.log(balance);
	placeBet();
  }).fail(function() {
    setTimeout(function(){placeBet();},3000); //This is the value the script uses to re-send the rolls if the server doesn't respond 
  });
}

//re-randomize our client seed to ensure provably faireness

function makeid()
{
    var text = "";
    var possible = "abcdef0123456789";

    for( var i=0; i < 16; i++ )
        text += possible.charAt(Math.floor(Math.random() * possible.length));

    return text;
}

placeBet();

Quote from: SparkedDev on January 17, 2016, 01:45:31 PM

My current build im using recommended starting is 60k plus but ive built to 0.01 with 20k sats.

Code:

var bet = {base: 0.0000001, current: 0.0000001}; //Modify these values to change your base bet
var placeBet=function(){
	$.post( "action.php", { prizes: "1000,16.9,0,0,17,0,0,0,0,0,0,0,17,0,0,16.9,1000", 
						token: token, 
						secret:0,
						bet:bet.current,
						bits:null,
						user_seed:makeid(),
						act:"play"
						})
  .done(function( data ) {
	if (!data.success){
		alert(data.msg);
		return 0;
	}
    
	var win=data.game_result.win;
	console.log( win, data.data.balance );
	if (win>bet.current){
		bet.current=bet.base;
		if (bet.current<bet.base) bet.current=bet.base;
	}else if (win<bet.current){
		bet.current=(bet.current-win)*1.1; //Modify this value in order change the on loss multiplier
	}
	//console.log(balance);
	placeBet();
  }).fail(function() {
    setTimeout(function(){placeBet();},3000); //This is the value the script uses to re-send the rolls if the server doesn't respond 
  });
}

//re-randomize our client seed to ensure provably faireness

function makeid()
{
    var text = "";
    var possible = "abcdef0123456789";

    for( var i=0; i < 16; i++ )
        text += possible.charAt(Math.floor(Math.random() * possible.length));

    return text;
}

placeBet();

nice amount big win small bets with great custom bet
but the custom bet so risky with big bet
to hit 17x so difficult but its imposible with low chances , on my side better red line

Quote from: SparkedDev on January 17, 2016, 01:45:31 PM

My current build im using recommended starting is 60k plus but ive built to 0.01 with 20k sats.

Code:

var bet = {base: 0.0000001, current: 0.0000001}; //Modify these values to change your base bet
var placeBet=function(){
	$.post( "action.php", { prizes: "1000,16.9,0,0,17,0,0,0,0,0,0,0,17,0,0,16.9,1000", 
						token: token, 
						secret:0,
						bet:bet.current,
						bits:null,
						user_seed:makeid(),
						act:"play"
						})
  .done(function( data ) {
	if (!data.success){
		alert(data.msg);
		return 0;
	}
    
	var win=data.game_result.win;
	console.log( win, data.data.balance );
	if (win>bet.current){
		bet.current=bet.base;
		if (bet.current<bet.base) bet.current=bet.base;
	}else if (win<bet.current){
		bet.current=(bet.current-win)*1.1; //Modify this value in order change the on loss multiplier
	}
	//console.log(balance);
	placeBet();
  }).fail(function() {
    setTimeout(function(){placeBet();},3000); //This is the value the script uses to re-send the rolls if the server doesn't respond 
  });
}

//re-randomize our client seed to ensure provably faireness

function makeid()
{
    var text = "";
    var possible = "abcdef0123456789";

    for( var i=0; i < 16; i++ )
        text += possible.charAt(Math.floor(Math.random() * possible.length));

    return text;
}

placeBet();

Nice work dev was looking forward for it

Quote from: SparkedDev on January 17, 2016, 01:45:31 PM

My current build im using recommended starting is 60k plus but ive built to 0.01 with 20k sats.

Code:

var bet = {base: 0.0000001, current: 0.0000001}; //Modify these values to change your base bet
var placeBet=function(){
	$.post( "action.php", { prizes: "1000,16.9,0,0,17,0,0,0,0,0,0,0,17,0,0,16.9,1000", 
						token: token, 
						secret:0,
						bet:bet.current,
						bits:null,
						user_seed:makeid(),
						act:"play"
						})
  .done(function( data ) {
	if (!data.success){
		alert(data.msg);
		return 0;
	}
    
	var win=data.game_result.win;
	console.log( win, data.data.balance );
	if (win>bet.current){
		bet.current=bet.base;
		if (bet.current<bet.base) bet.current=bet.base;
	}else if (win<bet.current){
		bet.current=(bet.current-win)*1.1; //Modify this value in order change the on loss multiplier
	}
	//console.log(balance);
	placeBet();
  }).fail(function() {
    setTimeout(function(){placeBet();},3000); //This is the value the script uses to re-send the rolls if the server doesn't respond 
  });
}

//re-randomize our client seed to ensure provably faireness

function makeid()
{
    var text = "";
    var possible = "abcdef0123456789";

    for( var i=0; i < 16; i++ )
        text += possible.charAt(Math.floor(Math.random() * possible.length));

    return text;
}

placeBet();

Cool, thanks Sparked! I might have to pop back in to give this script a shot...

Quote from: Zodiac1233 on January 17, 2016, 12:35:04 AM

Yes, it should never occur again. Also, it doesn't prevent divesting. Only investing, playing, and withdrawals are locked.

I cannot tip, play, invest or withdraw.

EDIT: This issue was resolved to my satisfaction at the developers earliest convenience.

Odds i found on page three of OP

Chance to hit -

Red Bar:
1111x - 1 out of 32768 chance to hit!
111x - 1 out of 2048 chance to hit!
22.7x - 1 out of 273 chance to hit!
7.77x - 1 out of 58.5 chance to hit!
4x - 1 out of 18 chance to hit!
2x - 1 out of 7.5 chance to hit!
0.25x - 1 out of 1.6 chance to hit!
0.2x - 1 out of 5 chance to hit!

Orange Bar:
444x - 1 out of 32768 chance to hit!
55.5x - 1 out of 2048 chance to hit!
15.5x - 1 out of 273 chance to hit!
6x - 1 out of 58.5 chance to hit!
3.52x - 1 out of 18 chance to hit!
1.5x - 1 out of 7.5 chance to hit!
0.7x - 1 out of 4 chance to hit!
0.5x - 1 out of 2.85 chance to hit!
0.2x - 1 out of 5 chance to hit!

Green Bar:
111x - 1 out of 32768 chance to hit!
44.4x - 1 out of 2048 chance to hit!
11x - 1 out of 273 chance to hit!
5x - 1 out of 58.5 chance to hit!
3x - 1 out of 18 chance to hit!
1.2x - 1 out of 7.5 chance to hit!
1x - 1 out of 4 chance to hit!
0.6x - 1 out of 2.85 chance to hit!
0.25x - 1 out of 5 chance to hit!

Teal Bar:
33x - 1 out of 32768 chance to hit!
11x - 1 out of 2048 chance to hit!
3.3x - 1 out of 273 chance to hit!
1.8x - 1 out of 58.5 chance to hit!
1.3x - 1 out of 18 chance to hit!
1.14x - 1 out of 7.5 chance to hit!
1.1x - 1 out of 4 chance to hit!
1.03x - 1 out of 2.85 chance to hit!
0.4x - 1 out of 5 chance to hit!

Blue Bar:
4x - 1 out of 32768 chance to hit!
3x - 1 out of 2048 chance to hit!
2x - 1 out of 273 chance to hit!
0.14x - 1 out of 58.5 chance to hit!
0x - 1 out of 3.3 chance to hit!
0.1x - 1 out of 7.5 chance to hit!
1.05x - 1 out of 2.85 chance to hit!
3x - 1 out of 5 chance to hit!

Your custom bar:
Same odds as of red! Wink

Hope it's helpful for all of you!

since some users where having issues not understanding odds

Quote from: SparkedDev on January 17, 2016, 06:23:29 PM

Hope it's helpful for all of you!

since some users where having issues not understanding odds

Nice this will help me a lot in the future,back i touth it was 1111x to 1111x chance

The odds to hit at each position, from the center outwards are

1:5.092, 1:5.729, 1:8.184, 1:15.004, 1:36.009, 1:117.029, 1:546.133, 1:4,096, 1:65,536

That is assuming you consider being 1 left of center not the same result of 1 right of center and so on. Double the odds of all but the center if you're using a mirrored row.

Quote from: Zodiac1233 on January 17, 2016, 07:13:44 PM

Thanks for the info zod

Why I must contact support to withdraw my funds?

Quote from: BitBitCoin on January 19, 2016, 04:51:48 PM

Why I must contact support to withdraw my funds?

Please PM me (zodiac) in Bitvest chat

Quote from: BitBitCoin on January 19, 2016, 04:51:48 PM

Why I must contact support to withdraw my funds?

Is that a new rule from bitvest? as I experienced some time ago I did not need to contact support to withdraw my funds. Are you going to withdraw big amount?

Quote from: Bitinity on January 19, 2016, 05:09:30 PM

Quote from: BitBitCoin on January 19, 2016, 04:51:48 PM

Why I must contact support to withdraw my funds?

Is that a new rule from bitvest? as I experienced some time ago I did not need to contact support to withdraw my funds. Are you going to withdraw big amount?

Normally the issues only happens when hot wallet has been emptied.
Some people win big and cash the whole hotwallet out sometimes so you have to wait for it to be refilled.

As of recent do to the new update there has bee some issues but i think its mostly older accounts that are effected.

The issue is caused by an automated auditing system we developed. We're still working out a few edge cases which appear to be effecting older accounts, in total <1% of users are effected. We found out what caused it to get triggered for the majority of the users who reported issues so far. We're currently working on a full fix for the remaining users.

Trivia is currently going on 0.006btc left to giveout