|
Is there any page or post that lists apps sorted by wagered amount? I think it could be an interesting list to see and possibly have some kind of competition/promotion for app developers to dethrone betterbets from the top spot
|
|
|
|
I'll do my best to have them working in the next release. I don't know when the next release will be, I get very little time to work on the bot. At the soonest it will be end of next weekend (12 Jun)
Besides fixing that what else do you have in mind for the next release? If you're taking suggestions I'd like to see more conditions for the martingale losing streaks. Instead of just one "After x Losses in a row, change chance to y" I'd like to have 2 or 3. Otherwise I can't remember anything else I wanted. I'm not adding new features at this point, only bug fixes (and possibly new sites if any are interested) I generally work on the zero-one-infinite concept. After a while you're going to want 4, and then 5, etc. So I'm going to have to say no to the request, at least until v4 is ready. |
|
|
|
Hi seuntjies im noob here, i just serching the "increse by x %" on the bot, its just on the basic settings, in "times bet by" ?? Or where  I cant find it, and its too on the advanced settings too??? Thank you man for all your work and please reply i really need it I don't use % in the bot. Yes, in basic mode, it's times bet by setting. To increase by 100%, times your bet by 2. In advanced settings, it's called multiplier. |
|
|
|
|
I noticed this past weekend that the Source code on github is out of sync with v3.1.5. It seems I deleted some uncommitted code while switching between the master branch and the v4 branch that was included in the 3.1.5 stable release.
I suggest using 3.1.4 if you don't trust me 100% since the source for 3.1.4 and the 3.1.5 beta is in sync with github. I'll need to decompile the current 3.1.5 and figure out exactly what changes I made between the 3.1.5 beta and the stable 3.1.5 release and commit them to github before I can continue updating the bot.
Sorry for this slip up.
|
|
|
|
|
I'll do my best to have them working in the next release. I don't know when the next release will be, I get very little time to work on the bot. At the soonest it will be end of next weekend (12 Jun)
|
|
|
|
I took a quick look at his code and it seems legit. This does not mean that his EXE isn't going to steal your coins. Performance and resource utilization could be improved a ton by interacting directly with the api calls instead of using an embedded browser.
so if you can vouched this mate might more members here will try using it as what you said that this bot seems to be legit we are just all wondering or taking extra precaution with this kind of a programs. Note that I said the source is ok but the exe might not be. I guess you could say I halve vouched it then. |
|
|
|
Password was recently reset. Beware. He might ask for a vouch, then change the download link/the downloaded files to some malicious duplicate. Always check for yourself, download a copy with sandboxies, run it and then do a virus scan, then take it out of sandboxie.
A better approach would be to self compile from github |
|
|
|
999dice only? have you tried betterbets, bitdice,coinmillions,crypto-games,fortunejack,monerodice or safedice? I can confirm that the bot doesn't work on betking and rollin at this moment because of recent changes to the site. Just-dice should still work fine but i haven't checked in a long while. Primedice does still work fine and there are many people using it there and I tested it a few days ago. If you're having trouble logging in. see "I am unable to log in to site x (Failed to log in or create new account) even though I'm sure my username is correct. Please Help!" on my faq page: https://bot.seuntjie.com/FAQs.aspx#faq25 |
|
|
|
|
Also, the site doesn't remember your account. So if you deposit into an account and do not set a username and password, you WILL lose access to your account and your coins the moment you close your browser.
This page should be in closed beta running on testnet coins at the best.
|
|
|
|
Raw as in things doesn't work.
So I wasn't able to make a list last night, had some more important things to do. I'll summarize: If the socket is unable to connect I cannot see the chat and no bets are loaded into the bet history tab. This is fine, i feel it's mostly a cosmetic thing but should be addressed. What's not fine is that if the socket doesn't connect, I can't see the result of my OWN bets, even though the client gets the data. get an xhr fallback for the socket or something and stop relying on the socket for ones own bets if you get the data from the post anyway. You're doubling your network traffic. Now the big thing. Your site isn't provably fair. On your provably fair page, you claim the client seed is generated client side (as in in my browser using javascript), so why is there a call to randomize_seed.php when I click randomize and why do I get the new client seed from the server? as shown in the image below.  There's no way of changing the client seed locally. Even if you open the provably fair box and change the seed, and then close it again, that seed is not posted when you place a bet. As you can see below.   If I set the client seed manually in a custom post, there's no way to determine if it even gets used since there's no way to check a bets' details after the fact, other than what's displayed in the grid. This all basically means that you can generate client and server seed pairs that are biased towards a direction. You claim not to be a copy of rollin but you're provably fair page is a word for word copy of theirs, and this occurs all over your page: Left you, right rollin  |
|
|
|
^ I am more curious about above. BitZino allows 32 "aZ09" characters (62^32?) as clientseed and the MT seed is a SHA256 based on that. Isn't that a lot more than 2^32? Maybe I misunderstand that part though.
Good catch, but sadly, the seed maxes out at 2 32 – 1. bitZino combines the server seed and client seed, hashes it with SHA256, but then only uses the first 8 bytes of it. So, the range is 0x0 to 0xFFFFFFFF. (FFFFFFFF) 16 = (4294967295) 10. They write about this in their techblog: https://techblog.bitzino.com/2012-06-30-provably-fair-shuffling-through-cryptography.htmlAh, right. So this seems like a limitation of MT19937. So if they would use MT19937-64, would this be a sufficient solution? This is still less than 52! but at least less feasible to calculate? Like JackpotRacer I am wondering what "the best solution" would be to get a provably fair random card deck. I can imagine something like the "dice nonce method" but adding an extra nonce so it could calculate more numbers (since a "duplicate card" cannot happen, so might need to loop a bit more.) But this might get a bit heavy in performance the more unique cards you need  How about something like this: PseudoCode: list<int> UnshuffledDeck = new list<int>();
//Populate UnshuffledDeck from 1-52, where 1= ace of spades, 2=2 of spades etc etc.
list<int> shuffleddeck = new list<int>(); //empty list
string clientseed = "something"
string serverseed = "randomly generated server seed"
int nonce = 1 //or whatever your nonce should be
while (UnshuffledDeck.count>1)
{
int tmp = UnshuffledDeck [rng(clientseed,serverseed,nonce,unsuffledeck.count)]
shuffleddeck.add(unshuffledeck[tmp])
shuffleddeck.removeat(tmp);
}
shuffleddeck.add(unshuffleddeck[0])
unshuffleddeck.removeat(0)
function int RNG(string client, string server, int nonce, int max)
{
int randomnumber = Using a nonce based RNG system similar to Justdice or betking, generate a random number between 0 and 1 000 000.
return randomnumber%max
}
So take a "brand new" deck. Pick 1 card at random from the deck and put it at the top (or bottom) of a new deck. Continue doing this until there are no more cards left n the unruffled deck. The random card picked from the deck depends on the client seed and the nonce of the bet. If you feel this isn't random enough, repeat the shuffle using the shuffled deck as the new unshuffled deck |
|
|
|
Direct API calls can be flagged as spam i think
That'd mean anything from a browser would also be flagged as spam, since the browser calls the api calls when you click a button. Cut out the middle man (browser) and the bot should be faster and less resource intensive since you don't need to render anything |
|
|
|
|
Raw as in things doesn't work.
|
|
|
|
|
This Page feels really really raw and I don't think it should be publicly available yet. I'll post some motivation for my statement here after a I get home in a few hours and have had time to compile a list.
|
|
|
|
|
I took a quick look at his code and it seems legit. This does not mean that his EXE isn't going to steal your coins. Performance and resource utilization could be improved a ton by interacting directly with the api calls instead of using an embedded browser.
|
|
|
|
Is there any to export all the real bets like we can do in a simulation?
Or at least can I see all streaks above a certain number?
All bets are stored in a sqlite database (Dicebot.db) and can be viewed using the bet history form (View->Bet History) or you can browse,query or export the DB using something like sqlite browser |
|
|
|
 I've fixed the bug great dicebot Mind telling me how you fixed the bug so I don't need to do the same work a second time? Edit: Also, mind telling me what you fixed? |
|
|
|
Hi Seuntjie
The bot sometimes goes blank and then come back on. Other times just never comes back. Have to exit, restart the bot and login again to PD . It also like to stall for some seconds and continues again or goes blank. It also can flash a blank page and continues.
Any reason for this.?
I have tried all versions. Still the same. Version 3.1.3 , 3.1.4 and 3.1.5 .
Last week was not so bad. But since yesterday I have to restart many times.
Please help.
Please see this post: https://bitcointalk.org/index.php?topic=307425.msg14674738#msg14674738 |
|
|
|
what do you think of this diceBot strategy?  Any comments/feedback is welcome.. Looks like a typical martingale to me yes, martingale with twist where initial few bets after any win are high and all 4th bet onward are minimum(i.e. 1 satoshi) Is this strategy worth trying with big amount? maximum drawdown is approx 1 and profit is 1.6 All strategies lose in the end. There is no system that will profit indefinitely or are guaranteed to make a profit for so many bets or whatever. The aim of the bot is not to make a profit, it's to make dice more interesting. To answer your question, if you enjoy the strategy and can afford/don't mind to lose a "big amount", then yes, it is. |
|
|
|
|
Show Posts
