Are you getting any sort of error message/popup?

If you are getting an error popup, it would be helpful for you to help us determine the cause of this. To do this, please open your debug console (in GoogleChrome press Ctrl-Shift-J) and then watch the console while the bot is running. When the bot stops, check your "Console" tab for an error and also check your network tab to see the response received for the request which caused the reset. Please forward this info to us and we'll see what's going on.

Thanks in advance.

Just to clarify why this is actually impossible: due to our integration with MoneyPot.com, your balance actually lives (and comes from) the MoneyPot server. MoneyPot holds the wallet, manages your deposits and withdraws and is the leading server; our server just fetches info from MoneyPot and displays the relevant info (in reality things are a bit more involved that this, but this captures the basic idea). Now, when you're logged in as a guest user, you don't have a MoneyPot account and as such don't have a balance. Even if we gave you a guest-balance through some clever programming trick, you would not be able to gamble against the MoneyPot server, since you don't have an account there.

The way we have solved guest access is to implement a roll-generating algorithm (modeled after PrimeDice) which performs the roll on our local server, thus not involving MoneyPot in any way shape or form.

I hope this explains why you don't get a guest balance. Please also note, since sites like PrimeDice own the entire front- and back-end, they can sign you up automatically, thus automatically creating an account and then let you access the faucet. With us it just doesn't work that way. In this case it's a drawback, but integration with MoneyPot gives us to many other benefits that it's well worth it to accept issues like this one.


Thanks. We've put lots of effort into the front-end and always appreciate positive remarks like yours.  

Hi, thanks for your suggestions/comment. Please see my answers below:

1) Correct, I'll fix that ASAP.

2) Well, we've debated this internally and it is my conclusion that the percentage bar is most appropriate. Let me explain the drawbacks of using a fixed number rather than a percentage:
a) Lets assume that 3 days before months end you have 50 raffle tickets. You then decide to edit your account preferences and say that want to enter 25 (50%) of your tickets into the monthly raffle.
b) Over the next few days you gamble like crazy (or just run the built-in bot for a few hours) and 3 days later you have 80 raffle tickets.
c) If you still want to enter 50% of your tickets into the monthly draw, you'd have to into "Your Account" again and adjust this number. If we assume that you're busy with your job, trading altcoins or walking your dog, you might well forget to do this, resulting in you submitting about 35% of your raffle tickets, which is probably not what you intended.
d) Lets assume that you do #c and during the next month, you don't gamble a lot and forget to update this setting. You would then submit either all or a much larger percentage of your raffle tickets, which again may not be what you want.
To summarize: With a percentage setting, you can set the percentage and forget about it; it will always adjust based on the number of available raffle tickets. I believe that this a better (and lower-maintenance) solution when compared to using absolute numbers since lets face it, you'll always submit a given number of raffle tickets based on the total number of raffle tickets available to you (this is essence is a percentage expressed as a fixed number); allowing you to set this preference percentage-based just means that it's a low (or even "no") maintenance operation and is generally a more flexible solution which nicely auto-adjusts without you having to worry about the details.

3) We are working on making those achievements give you a/some tangible benefit(s) on the site and are debating a number of ideas for this. More news on this in the future.

I hope this explains our reasoning behind choosing a percentage based setting.

We hear you loud and clear and we'll work something out to make this possible. Thanks for your feedback.

Thanks for your kind words.

As for our future plans: we will spend some time putting the final polish on current site/functionality and take care of a few little things that we didn't get to in the pre-launch frenzy. Once that has settled down, we will start working on more games. While we won't reveal our exact plans, I'll just say that we  plan on launching games which are in the traditional casino/gambling space but we also have some exciting ideas for original games which we hope will  excite our users.

Thanks for your feedback. We'll be fixing minor glitches like the one you reporting for the odds interface over the coming days. We've been extremely busy getting things ready for launch and it's only fair to admit that a few minor things slipped through the cracks.

As for the horse racing game, we'll be improving this as well and have some cool ideas for it. We just need to figure out how to turn these into an atomic, provably fair game so that it integrates well with the MoneyPot.com engine.

Once again, thanks for providing us with feedback, it's well appreciated.

Thanks for liking our site. Yes, we're aware of this issue, but the problem is that due to our integration with MoneyPot.com, we can't just auto-register people the same way other casinos do. The integration with MoneyPot.com buys us a lot in terms of features and security so we don't we figure this trade-off is worth it.


I'm sorry to have to tell you that at this point we don't.


No. However, we are integrated with MoneyPot.com, which basically means that we're using their system services & architecture to generate provably fair bets and all surrounding services.

This is our dedicated dev-post where we will be communicating site updates and enhancements.

First of all, we would like to announce our security related bug bounty program: if you find a security related issue that we are not yet aware of, please report it to us in private (email is best). In return, we will pay a bounty of 0.2 BTC for any issue we deem a valid security concern. If we determine that we won't pay you, we will clearly communicate why we believe that we don't need to pay you. Before you think we'll scam you on this and just not pay you, please consider the fact that we are extremely happy (well, maybe not happy, but certainly grateful) for any such issue which is brought to our attention and that we've paid out 3 bounties over the first 4 days after the site went live. But please also realize that you might be reporting an issue which we are already aware of or that we determine after looking over the code in question, that it is not an issue after all. Either way, we will happily pay a bounty for any valid security-related issue which is brought to our attention.

Update (2014-08-02): we're increasing the bounty for security issues which can lead to loss of bankroll or players funds to 3 BTC.


Version 2.04 (2016-02-25) fixes the following issues:
#204: Fix Bot API issues
#203: Improve chat update timings, make them variable
#202: Ensure that Chat Rain sends a notification to chat
#201: Correctly escape URL content for chat messages on JQuery level
#200: Create bet verification page for Rubies bets
#199: Add menu link to bet verification page
#198: Add menu link to wallet page


Version 2.03 (2016-02-23) fixes the following issues:
#197: Change deposit address input box from disabled to readonly to allow selection
#196: Max payout calculation is incorrect
#195: Show which coin was used for a bet in betInfo modal
#194: Show which game a bet belongs to on betInfo modal
#193: Add rain functionality to new chat system
#192: Add number separators to daily bet volume info box
#191: Add username coloring according to user level to new chat
#190: Switch to self-hosted chat


Version 2.02b (2016-02-16) fixes the following issues:
#189: Add coin used to bet-info popup
#188: Luck forging is broken
#187: Most unlikely wins needs to lower selection threshold
#186: Account wagered volume display is broken


Version 2.02 (2016-02-15) fixes the following issues:
#185: Achievement level code needs to be aware of new table structure
#184: Remove UpdateBalance button (not needed anymore)
#182: Affiliate payout modal display is broken
#183: Affiliate payout calculation needs to be aware of new table structure


Version 2.01 (2016-02-15) fixes the following issues:
#181: Add CopyToClipboard button to deposit dialog
#180: Fix BetMining Display and credit all affected users 25 RBIES


Version 2.0 (2016-02-14) introduces the following features:
- Support and integration of betting using RUBIES coin
- Wallet integration for deposits and withdraws
- Live update of balance
- Lots of other little fixes


Version 1.40 (2015-08-25) fixes the following issues/bugs:
#179: Fix Plinko payout injection vulnerability


Version 1.39 (2015-08-17) fixes the following issues/bugs:
#178: Make HighRollers bet log tab display live updates
#177: depositAddress API is broken
#176: Hotfix for security issue


Version 1.38 (2015-08-04) fixes the following issues/bugs:
#175: Affiliate payout report in popup window is incorrect
#174: Fix slow bet speed


Version 1.37 (2015-08-02) fixes the following issues/bugs:
Security review and site hardening (no bug number).


Version 1.36 (2015-07-29) fixes the following issues/bugs:
#172: Incorrect exception type caught in API handlers
#171: Incorrect loop count in cron scheduler
#170: Throttle API bets smaller than 100 Satoshi
#169: Saved/restored plinko wager can display 'undefined'
#168: Make colored payout dot in plinko wheel larger
#167: Fix duplicate mouseover on Plinko payouts
#166: Guest/Demo mode is broken
#165: Add /depositAddress to API
#164: Add /bet entry point to API


Version 1.35 (2015-07-27) fixes the following issues/bugs:
#26: Implement site API


Version 1.34 (2015-07-20) fixes the following issues/bugs:
#158: Don't open game links in new window
#157: Fix wager conflict between games


Version 1.33 (2015-07-15) fixes the following issues/bugs:
#154: Add screenshots of games to landing page
#153: Add another icon to the dice widget to toggle the bot widget
#152: Highlight winning horse on HorseRace Game
#151: Create a unified games page with a each game on a separate tab


Version 1.32 (2015-07-10) fixes the following issues/bugs:
#143: Add additional site statistics to top header


Version 1.31 (2015-07-08) fixes the following issues/bugs:
#144: Add validation to affiliate code on home page
#145: Plinko bets report 1-off incorrect winning slot in bets table


Version 1.30 (2015-07-05) fixes the following issues/bugs:
#135: BetterBets Cashback Program: add player volume bonus model tracking and variable house edge bonuses


Version 1.29 (2015-07-01) fixes the following issues/bugs:
#123: Change Raffle Ticket base bet from 1 satoshi to 100 satoshis with staggered rewards with increasing bet size
#142: Convert leftover raffle tickets at a rate of 10%
#141: Add generic variable storage framework (needed for some planned stuff)
#140: Chat focus resetting results in overzealous input clearing
#139: Update Indonesian Translation
#136: Formalize Raffle Ticket Assignment Code
#134: Plinko does not validate available balance before allowing betting


Version 1.28 (2015-06-28) fixes the following issues/bugs:
#133: Automatically save and restore Plinko settings
#90: Chat needs to keep better focus upon entering message
#132: Plinko sometimes returns all zero payouts
#131: Plinko bets should first subtract wager and then add winnings in 2 separate steps
#130: Bet requests should also pass X-Forwarded-For extra header
#129: RemoteRequest extraHeaders directive doesn't work
#127: Plinko rain-bets do not properly update balance


Version 1.27 (2015-06-26) fixes the following issues/bugs:
#126: Display a browser warning on Plinko page for non-Chrome browsers
#124: Allow Plinko to drop multiple balls at once
#118: Putting a zero in the betterbot 'increase by' field and hitting calculate pops an error
#115: Hall of fame, bets and wins are switched.
#5: Implement offsite backup scripts


Version 1.26 (2015-06-25) fixes the following issues/bugs:
#122: Add Plinko game


Version 1.25 (2015-06-22) fixes the following issues/bugs:
#120: Add indonesian language translation
#119: Vulnerability in tip function through chat
#114: Ensure dice house edge is always 1%


Version 1.24 (2015-06-16) fixes the following issues/bugs:
#111: Open game menu items in new tab
#110: Content pages show user as not being logged in
#109: Create blog page/section


Version 1.23 (2015-06-13) fixes the following issues/bugs:
#108: Implement client-based faucet integration/authentication
#107: Implement MP-integrated Deposit/Withdraw dialogs
#106: JS error for guest users on content pages
#104: Better timeout reporting for MP connection issues


Version 1.22 (2015-06-08) fixes the following issues/bugs:
#103: BetInfo dialog needs max height with scrollable area
#102: Have bet size info dialog calculate bets until balance is too small
#2: Fix server-side rounding errors (turns out to be actually quite tricky to get right)


Version 1.21 (2015-06-09) fixes the following issues/bugs:
#100: Save & Restore AutoBot settings
#94: Bot seconds not decreasing while running
#101: Auto-Set AutoBot Multiplier to 9999 when win chance is 0.01
#92: Allow fetching bet info through chat
#98: Add random increasing sleep after curl failure before retry
#91: Increase chat log size to 150
#96: Increase timeout for MP curl requests to 3 sec
#97: BetInfo page needs some CSS fixes
#95: Show next server seed on BetInfo dialog


Version 1.20 (2015-06-05) fixes the following issues/bugs (just in time for Friday Happy Hour):
#88: Implement max bet limit on Bot
#87: Bot Status is not updated when premature exit condition applies
#86: Add bet flip/flop between under/over to bot
#85: Max Loss/Win in BetterBot is not working properly.


Version 1.19 (2015-06-05) fixes the following issues/bugs:
#84: Implement better tracing/logging for curl errors
#83: INVALID_HASH handling code passes incorrect user info into recursion
#82: Fix broken horse game
#81: Fix multiple chat messages issue


Version 1.18 (2015-06-02) fixes the following issues/bugs:
#53: Allow inspection of any roll by submitting roll ID
    -- you can now go to https://betterbets.io/app/bet/?id=123456 to verify any bet by supplying the desired bet-id
#79: Add turn ID for AutoBot bets to help with verification


Version 1.17 (2015-06-02) fixes the following issues/bugs:
#78: Implement Cron job to submit chosen percentage of RaffleTickets at month end
#77: Incorrect label for WinChance in account sideblock
#76: RaffleTickets amount display is not updated live
#74: Hotkeys "on/off" button now misaligned.
#75: Bet win check is range inclusive when it should not be
#11: Implement Cron job for querying MP bankroll
#20: Add a BetLog tab for largest bets taken for user
#67: Security issue in chat
#70: Make right account block float near top of window when scrolling down
#72: Catch INVALID_HASH error and code around it


Version 1.16 (2015-05-29) fixes the following issues/bugs (just in time for Friday Happy Hour):
#66: Create a tool to pre-calculate bet sizes for AutoBot runs


Version 1.15 (2015-05-29) fixes the following issues/bugs:
#64: Limit chat message input field to 140 chars to avoid dropped messages
#59: Create additional bet log tabs
#60: Save UserAccount button is broken
#55: Chat loses focus after entering message
#63: Create appropriate DB indexes to ensure SQL runs efficiently
#62: Incorrect house edge specified in HorseRace odds explanation
#61: Information disclosure on Login and Dice redirect


Version 1.14 (2015-05-28) fixes the following issues/bugs:
#57: Maximum bet & Average bet fields do not reset when restarting AutoBot
#58: Fix JS error on empty chat after restart of chat server


Version 1.13 (2015-05-27) fixes the following issues/bugs:
#51: Improve delay slider layout to better fit into site-style of using input-groups
#50: Pressing "Stop Bot" resets stats too early and thus nukes current run summary
#31: Allow AutoBot to be configured for more than 10000 rolls
#21: Make sure that AutoBot runs at highest speed possible (result: about 2.5-3x as fast at max speed)


Version 1.12 (2015-05-26) fixes the following issues/bugs:
#49: Create a timing adjust slider for horse animation
#28: Create Ajax function for LFActivation and LFProgressComplete
#48: Have curl wrapper retry on timeout
#47: Disable chat debug output in JS console
#41: Chat Admins/Moderators should have a different color name
#13: Revamp bet log update to use Interval rather than Timeout + save on unncessary DB queries
#16: Disable activation of LuckForging during Autobot run
#30: Ensure that list of chat messages does not grow into infinity
#39: Swapping from Chat to Account for > 1st time, changes slider into textbox
#42: Change Raffle Ticket submission slider to use a 5% step
#38: Place game icons before menu text in left-side menu
#36: Implement more detailed Autobot statistics
#19: Do not notify user if LF completion during Autobot run
#40: Swapping into chat for > 1st time, doesn't display chat history anymore
#43: Call User::logout() when retrieving user account fails and redirect back to home page
#37: Add French translation


Version 1.11 (2015-05-24) fixes the following issues/bugs:
#15: Add link to MP bet verification to Provably Fair popup
#34: Fix right sidebar loading state issue/error when sidebar is already loaded + add nice animation
#32: Message in Chat needed when a user tips another user
#27: Implement tipping via chat


Version 1.10 (2015-05-22) fixes the following issues/bugs:
#33: Update/Change registration link to include app_id
#25: Improve registration flow and place CallToAction button on homepage
#24: Horse bet results appear in the "All Bets" table before animation is complete.
#23: Autobot "Win Chance" field doesn't change when multiplier is changed.
#22: AutoBot status needs to switch message between Turns/Seconds
#17: Disable user alias change since changed aliases cause problems with the tipping API
#8: AutoBot win/loss limits don't work
#7: AutoBot roll under/over doesn't work correctly
#3: Make site accessible to guest users
#1: Implement Chat