Thanks for those that have already accepted!

For the record, I'm offering 0.5 BTC for 30 days of exclusivity in your signature. I based that price off of this auction, in which nimda sold his sig space for 1 month for 0.7 BTC. He has 1000+ posts, and a historical trend of posting ~9 times per day, whereas I only require 100 posts and 1 post per day.

There are still a few slots open if anyone else is interested!

Good call! We are in the process of re-designing the Buy-In window to be much more user-friendly. One of the changes is that it will allow users to choose the minimum bet at buy-in time, rather than utilizing the account's "base currency" setting. I like your idea of setting the default value here based on the user's balance.

We'll also be including Dooglus's and ErubusBat's suggestions: we're adding a "Max Buy-in" button and we're adding a "Refresh" link so that users will have an actionable link to click after sending funds to their account.


We have had 2-step withdrawals on the backburner for a while now. We are planning on allowing users to opt to require an email confirmation before withdrawing any funds, changing the email address, or changing their password. So, stay tuned, we will be adding this soon!

Note that we are already very secure against session highjacking: Our session cookies is stored as a Secure HttpOnly cookie (meaning it can't be accessed from javascript, and it will only be sent over an https connection).


Good thought! My suspicion is that this would be a little bit "busy" with too much animation. But, I'll give it a try, and see how it feels!

We'd like to buy up to 5 user's signature space for the next month.

You must be willing to post on average once per day for the duration of the month, and you must be a member in good standing with at least 100 posts. We will also pay a premium for members with high post counts.

Post here and I'll PM you the details. First come, first serve!

Thanks for reminding me about this! We had meant to update Roulette along with Craps when you originally suggested this change, but it got lost in the shuffle of all the changes that were going on at the time. I've went ahead and updated Roulette so it has a more informative status message.


Hm, I hadn't really considered this. I'm not sure if there is a perfect solution though, because as you mention, the games do have some fundamental differences.

One solution would be in Blackjack to reduce the user's balance as they type different numbers into the Bet box. I don't love this solution though, because it doesn't adhere to what a user would expect in this game. I would hate to reduce the usability of one game just to get consistency between games.

Another solution is in  Craps and Roulette to only reduce the actual balance when the user clicks the bet button. But, likewise, I think this may be confusing to users in these games.

So, I think I'll leave it as-is for now. But, thanks for bringing this up, because it is an angle that we should consider when developing future games.

Thanks again for the feedback, I really appreciate your attention to all the little things! These type of improvements add up to a much better overall experience for our users.

You've always been incredibly helpful, Dooglus, so I just went in and added 1 BTC to your account.

This is a really cool story! I originally built bitZino with the main purpose of bringing bitcoin to the masses, so I'm glad to see that is starting to happen



I'm sorry about that! I have updated the original post so that it is more correct.

We do take bets up to 10 BTC, but only in Blackjack and Roulette. Video Poker has a max bet of 1 BTC per hand, and Craps has a max bet of 2 BTC per wager-type. Roulette also has a max bet of 1 BTC for the number wagers.

The main reason we have to make our Craps maximum wager smaller is because we support up to 5x odds wagers. This means that a wager of 2 BTC on pass and a subsequent maximum odds wager of 10 BTC is technically a 12 BTC wager on pass.

Thanks, and I'm glad you're liking it! We are indeed constantly working on new games. Our next game to launch will probably be three-card poker. We are also working on adding more varieties of video poker.

We would like to add multi-player games at some point - but for now we are focusing on having a full selection of single-player casino games.


Thanks for catching this typo! I can't believe how long it's been live this way, but it's fixed now I also fixed the colon issue on our user page.

Right now we only show the maximum bets in the rules dropdown if you're cashed into a real-bitcoin table. We are planning on changing this soon so that it will show on all play-money tables as well. Thanks for bringing this up, so that we expedite this change.


Thanks for the advice! I agree with you that a refresh button would be good here.

Another good catch, thanks!

That's a good idea. That box is already a little cramped, but I think we can find a way to do this without making the UI too busy.


Yeah, in general, the base currency settings need some re-working, which we are definitely doing. I like your idea of having a "set default" checkbox.


Ah. good catch, thanks!

Thanks for all the feedback Dooglus! This stuff really helps us make bitZino a better website.


This was one pretty bizarre! It turns out it was due to the way parseInt is implemented in javascript. We were calling parseInt without the optional second argument (which is the base of the number), and so javascript was trying to parse '08', and couldn't automatically figure out the base of the number. If you just pass the second argument (which is the correct defensive way to code it anyway), then the string is parsed correctly.

We've fixed all our javascript to call parseInt with the correct number of arguments.


Thanks for catching this! We definitely don't want people to accidentally wager for more than they were wanting to.

We've changed the behavior here to just disable the "Cash in" button if the value you entered is invalid. So, now we will never automatically change the value on you.

The default minimum bet on a table will always be the value of your account's "Base currency" (which you can set in your account edit page). I think it may be confusing if we remembered the minimum bet of the last table you cashed out from, rather than using the value you set for your account. I hope that the new behavior of disabling the button should also help to make it clear what's going on.

We don't have the option to increase the maximum bet of an in-progress table, since this would result in a lot of corner-cases usability-wise.

We are still looking at getting rid of the whole concept of "Base currency" though, and possibly having users just always enter the minimum bet when they cash in to a new table. There are just many corner cases and usability issues to consider when making this type of change.

[/quote]
Good catch! We fixed this button so that it greys out when you click it.


Oh yeah, I had forgotten about the notification messages style. I changed the background here to be darker, and also changed the location so that it's not right at the top of the page.

This should make it somewhat better, but we'll probably give the notifications a more comprehensive UI adjustment soon.


I will never get annoyed with anyone's feedback! Keep it coming!

I've added another quarter-BTC to your account, Dooglus to thank you for all the feedback. We highly value useful feedback, so that offer is good for anyone else too!

The "pass odds" and "don't pass odds" wagers don't have any popups associated with them when there isn't a point established. This is because it yet to be determined what the payout of that wager will be. But, I kinda agree that this is confusing. Maybe we should just show a popup and not show any payout information before the point is established.


Your wish is my command You're right though, the status message was showing up too late, and going away too quickly. We've pushed a fix for this.

We've pushed a fix for this, so now it shows a much more informative status message, including how much was won, lost and pushed on the last roll. Hopefully this make it easier to drink and gamble

We also added a subtle indication as to which wagers are active, and which ones aren't: the inactive wagers have a less dark background on mouseover.

Additionally, we've added the fact that all bets are always working to the rules dropdown.

Thanks for all the feedback everyone, keep it coming!

Ah, that is definitely the issue! It's not a huge issue, since it seems you can't even see the specific problem - but the issue is that all of the wagers have a few pixels of spacing between them, where they should be flush with each other. We'll see if we can fix it so that it looks good at all zoom levels.



This is actually intentional, since we want to allow the user to click and see what the odds of that bet are, and also potentially click and see exactly how much they have wagered. However, I see that this may not be the most intuitive UI - it may be better at least not to highlight the area on hover. I'll play around with the UI here...


Each casino typically does things slightly differently with regard to whether bets are automatically 'working' on the come-out roll. We decided to go with the least confusing option, and always have all visible bets working. From our survey, this is consistent with how other online casinos handle it. Compared to a brick-and-mortar craps game, it's just much easier to quickly remove and re-add your wagers, so it's not really even worth it to have a concept of 'working'. Maybe it would help to have some UI elements to make it clear that all bets are always working though...?

Thank you for taking the white-hat approach


Yeah, we've fixed that wager too. The same issue was affecting all of our "Single Rolls" wagers, and we fixed them all.


Your feedback has consistently been incredibly informed and very helpful. You're definitely an asset to the community, and an asset to anyone that listens to your feedback


Yeah, that was just a bad typo. Our simulation testing didn't catch it, because the odds were still paying out what was expected, it was just paying out for the wrong rolls. Fortunately, no one had made any real-bitcoin bets on that wager since launch.



Hm, yeah good point. We originally decided to show the hardways bets as 9.5 to 1 and 7.5 to 1 in order to contrast with the typical 9 to 1 and 7 to 1 payouts. 19 to 2 and 15 to 2 is probably more consistent with the rest of the table now though. I went ahead and updated this.

Fortunately, it's all in HTML, so it was an easy change


I did a little more looking into this, and it seems that it is generally acceptable if you're trying to create a contrast between different elements - which is definitely what we're trying to do: contrasting the table against the rest of the webpage. So, for now, I think we'll keep it as-is.


This is very strange. I have the exact same version of Chromium on linux and I can't replicate the issue in your screenshots. Is the Roulette table still doing a similar thing for you? I saw your Roulette screenshots, and I was able to replicate that and I think I fixed it: The issue was using decimals in the CSS for width and height, which Chromium rounded differently than other browsers. But, now we're not using decimals in the CSS anymore, so I can't figure out why a standards-compliant browser would be off by a few pixels in this way.


Yeah - all the payouts were always 35 for X, where X is the number of possible winning rolls. We simply converted it into "Y to X" notation completely incorrectly.

Thanks again for all your help!

We do plan on adding instructions for all of our games at some point, but for now, we are focusing on attracting gamblers that already know how to play these games. However, I do think that the fact that we present all the odds in an easy-to-digest manner should at least help those that are passingly familiar with craps.


We did intentionally go with a serif font for the table. It's supposed to contrast somewhat with the rest of the site, and look a litlte more like a traditional craps table, which typically uses elegant serif fonts to display their bets. Although, I'm no typography expert, so maybe this is a faux pas.. I'm open to suggestions.

Also - are you still using Chromium on Ubuntu? All of your screenshot's table layouts look like they are off by a few pixels, which is pretty ugly. I can't seem to replicate it on my linux Chromium install though.

Those were definitely some very bad bugs. Thank you for finding them! They have now been fixed. You are truly a bug finding master, Dooglus! I have added 1 BTC to your account to thank you.

I have also credited everyone that has made prop bets double the full value of their bets +1 BTC of all real-bitcoin prop bets that they've made in order to make up for these bugs. (Fortunately, only 2 users have made these bets, and they were for micro-stakes, so I really hope the 1 BTC bonus makes up for this egregious error).

The reason we made this error is really quite silly of us. All of our prop bets pay out 35 for X, where X is the number of possible outcomes. Of course, 35 for 2 does not equal 34 to 2, which is the error that we made. Unfortunately, we spent the majority of our QA testing the more complicated multi-roll wagers.

Thank you again for spotting this Dooglus, you really have helped so much in making bitZino a better site.

We have officially launched Craps!





It took us a little longer to make than we anticipated, but I think it is well worth the wait

Like all of our game, our craps game is Provably Fair. And, it features the slick HTML5 user interface that you've come to expect from us.

Additionally, it has the best odds of any craps game that you'll play: We start by offering 3x,4x,5x odds on our Pass and Don't Pass wagers, which is somewhat standard (although, many online casinos don't even offer this). Then, moving up, you'll see that our Field bet offers 3x payment on a 12, and a non-standard 2.5x payment on a 2 (the usual is only 2x on the 2). Our Hardways bets pay 9.5 to 1 and 7.5 to 1 instead of the standard 9 to 1 and 7 to 1. The largest deviation from the norm is in our prop bets: 1,1 and 6,6 pay 34 to 1 instead of the standard 30 to 1. Our 1,2 and 5,6 bets pay 33 to 2 instead of the usual 15 to 1. Finally, our Any Seven pays 29 to 6, and our Any Craps pays 31 to 4 - these are substantially better than the standard 4 to 1 and 7 to 1.

We're also proud of the lack of confusion in our Place/Buy and Place to Lose/Lay bets. Most casinos offer a "Buy"  and "Lay" bet which are identical to the "Place" and "Place to Lose" bets, but with slightly better odds on the 4 and 10 bets, and occasionally better odds on the 5 and 9 bets. This is confusing to new players, and often results in them making sub-optimal bets. We have simply removed the confusion, and instead we simply always offer the bets odds on our Place and Lay bets.

Give it a try and let me know what you think!

Congrats on the royal! I can't believe how many royal flushes we've seen in such a short time Thanks for the reminder on 4-color decks. We will roll that out before too long.

Also, by the way, our max bet for Video Poker is 1 BTC. We have to keep it lower than our other games because it has a much higher variance. If you're interested in risk of ruin analysis, I discussed our strategy for how we choose our max bets earlier in this thread:

https://bitcointalk.org/index.php?topic=87656.msg1145478#msg1145478

Congrats on the Royal Flush! That's the second one we've seen on our site so far

Thanks for letting me know about the display glitch, we'll make sure it's fixed for the next time you hit a royal

Thanks for the feedback! That definitely explained it very well. Comp sent

This is a very strange bug, because that button is actually just a single element, so the border shouldn't have a different behavior than the inside. Also, the interaction with the elements behind it are bizarre and unexpected. I can't seem to replicate the issue on either Firefox or Chrome, so I can't figure out what would be causing it. We will definitely keep an eye out for this bug though, and fix it if we can.

Thanks again for the feedback!