I've updated KLYE's script to handle our new options ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) var bet = {base: 0.0000001, current: 0.0000001, currency: "tokens", bits:1}; //Modify these values to change your base bet, currency may be "tokens" or "bitcoins", bits is the number of drops made 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:bet.bits, currency:bet.currency, user_seed:makeid(), act:"play", v:ver, }) .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();
|
|
|
We've just added a game speed controller, you may now play at any speed from 25 - 800%, good luck and have fun everyone ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif)
|
|
|
Today the hot wallet was empty, and I requested a withdrawal. It didn't go through, so I used funds from elsewhere.
Later, I divested funds and the withdrawal that I had requested got honored (I was confused when my balance suddenly dropped),
Please add an option to cancel a withdrawal if made when the funds are empty, possibly when the request is made.
We'll be adding a cancellation option in the near future ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif)
|
|
|
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.
I'm sure the issues will be resolved, people should have a little bit of patience. Yes, the issues with the remaining few false-positives have been dealt with, 0 users appear to be currently effected by this issue right now.
|
|
|
I've just sent lightlord an email and a pm regarding this. He should be paying this out asap. He's been very busy with a project. That is all I really know.
|
|
|
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.
|
|
|
Why I must contact support to withdraw my funds?
Please PM me (zodiac) in Bitvest chat
|
|
|
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.
|
|
|
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](https://bitcointalk.org/Smileys/default/rolleyes.gif) 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.
|
|
|
Yes, it should never occur again. Also, it doesn't prevent divesting. Only investing, playing, and withdrawals are locked.
|
|
|
We modified how games are stored to allow for increased betting capacity and better storage. That error is a result of a new automated security system recently implemented. We're working out a few edge-cases where it false-positives on older accounts, or accounts which received admin credits before /tip existed.
|
|
|
We are performing some schema changes and database optimizations, the site may appear slow or down for a while. Edit: We're back, good luck everyone ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif)
|
|
|
Random 100 - 1000% Rainbot for the next hour in celebration of reaching 5,000,000 bets!
|
|
|
The API is now in a closed staff-only beta, regular users will be granted access once I've completed proper documentation, this should be done within the next 24 - 48 hours.
|
|
|
We're going to make the entire site accessible via an API hopefully by the end of today, if not, then tomorrow. Get your bots ready :p
|
|
|
Seems lightlord paid you out. We were performing some wallet maintenance around that time, so all withdrawals were manual for a short time.
|
|
|
How long does it take to fill up the hot wallet? My withdrawal has been pending for almost 12 hours now!
Sorry for the delay, our wallet is usually able to process >98% of transactions automatically.
|
|
|
Sorry for the downtime, we're back up. As for support, PMing me here is the fastest way to get a response. The manual TXs will be processed when lightlord is on. As for management of funds, you can see the vast majority are securely held and in lightlord's cold storage 15iksRMotdLu9ubZAEVJtNyDcmYYPkorth
Lightlord Holds Bitvest.io Cold Wallet Address
HMnD5h64E85C0YT1CiPhoGhEU4zZ4ThvRt7NuyA1Wv5fWrrFG5jpi3F+PSqNU0ybHpbFsOahm9CCpkwRquRCkp8=
Edit: The downtime was caused by a DDoS attack which we have now resolved.
|
|
|
277% Happy Hour on right now! Get chatting and win big
|
|
|
Just released an update drastically increasing bet efficiency, we should be able to handle at least a few 100 bets/sec now ![Cheesy](https://bitcointalk.org/Smileys/default/cheesy.gif)
|
|
|
|