Looking for 100 Beta Testers to Try BitMillions.com - Get ฿ 1 to play for FREE!

[dooglus]

The FAQ:

"The payments for each winning ticket are made when the block is confirmed. When the block ends, all the relevant calculations are made and payments are processed after 6 confirmations."

I think it would be clearer if you said what needs 6 confirmations.  My bet, or the block on which my bet won.

[1713546598]

1713546598

[dooglus]

Oh, another thing:

When I search for the address I used to buy 5 tickets with, I see the 5 tickets, but nothing about how much they won.  I seem to have to click all 5 tickets individually to see winnings.  There's a green button with the ticket price on it next to each ticket.  Perhaps that could show the winnings instead?  I can't even tell if any of the tickets matched more than single numbers, except by checking on the left ("10 Free Plays Pending"), adding up the wins-per-ticket (3+2+1+1+2 = 9) and deducing that I must have hit pot 2 once, and hit single numbers 8 times.

[dooglus]

None of the recent payout transactions have confirmed.  I think it's because of this transaction having too-low a fee.  It's 16.6kB which means the fee should be at least 17 * 0.0005 = 0.0085 BTC, but you only included 0.0015 BTC fee.

Here's the transaction at http://bitcoincharts.com/bitcoin/txlist/ showing up as 'low priority' and unconfirmed 2 hours after it was sent:

[ShaTwo]

None of the recent payout transactions have confirmed.  I think it's because of this transaction having too-low a fee.  It's 16.6kB which means the fee should be at least 17 * 0.0005 = 0.0085 BTC, but you only included 0.0015 BTC fee.

I will double check that now... thanks for let it me know.

[dooglus]

I will double check that now... thanks for let it me know.

Note that transactions up to 10,000 bytes can be free (depending on the size and age of the inputs), but over that there's a minimum fee of 0.0055 BTC (0.0005 BTC per 1000 bytes or part thereof), so it might be worth breaking your transactions up into a series of smaller ones.

Another thing:

Every one of your payout transactions depends on the previous payout transaction, in a big long chain.

If a single one of your betters ever double-spends to buy a ticket, you'll end up with none of your payouts ever confirming, because they'll all depend on the double-spend that will never confirm.

What will happen when you have a million people buying tickets for each draw?  You can't have a million inputs to a transaction - it will make the transaction bigger than the maximum allowed block size.

[ShaTwo]

Note that transactions up to 10,000 bytes can be free (depending on the size and age of the inputs), but over that there's a minimum fee of 0.0055 BTC (0.0005 BTC per 1000 bytes or part thereof), so it might be worth breaking your transactions up into a series of smaller ones.

We will review our TxFee Policy, but if you check here
http://blockchain.info/address/1EnHPvDZfG9CzwK4Ai9ZpT6t7iJWPSCp77

Most Transactions seems to confirm just fine... looks like the problem only caused when there is a lot of ticket purchased in a single Draw.

[EDIT] The problem seams to be when a TX is more than 1000 bytes as you pointed out. Looking into it.

Every one of your payout transactions depends on the previous payout transaction, in a big long chain.

If a single one of your betters ever double-spends to buy a ticket, you'll end up with none of your payouts ever confirming, because they'll all depend on the double-spend that will never confirm.

A Double spend transaction will never made it up to this point, all the tickets included on the transaction have already 6 confirmations.

What will happen when you have a million people buying tickets for each draw?  You can't have a million inputs to a transaction - it will make the transaction bigger than the maximum allowed block size.

I don't think we will get to that point, specially because our idea is to launch mode games with diferente prizing, etc... but if that is the case and he do get to that point, I guess we will be forced to break the transaction up in a few parts... hopeful we still have time for that to happen.

[dooglus]

[EDIT] The problem seams to be when a TX is more than 1000 bytes as you pointed out. Looking into it.

I said 10,000, but whatever.  You'll look at your fee policy and make sure you're including the correct fees.  Then everything will work out.

A Double spend transaction will never made it up to this point, all the tickets included on the transaction have already 6 confirmations.

That's a very good point.  So it's just a matter of paying the right amount of tx fee to get timely confirmations.

[dust]

I owe you guys a review 

I'm impressed with the design of the site, very few Bitcoin businesses look as professional as this one does at launch.  Betting is straightforward, although in my opinion the number picking is somewhat cumbersome as it is impossible to pick all 4 numbers when placing a single bet.  The free plays are also nearly worthless as 1BTC already adds a single free play.  Adding 2, 3, and 4 free plays to the jackpots is kind of silly, too.  Depending on the transactions used to bet, it can be difficult to use the same inputs to claim free plays.  Besides these nitpicks, the site is easy to use and the detailed information on each draw is well presented.

BitMillions is a credible competitor to SatoshiDice.  It has more replay value in my opinion, offers no risk to the owners once the jackpots are initially seeded, and is sometimes even +EV for players, driving traffic to the site.

[payb.tc]

speaking of nitpicks, i can't believe people were complaining about a ~$2 ticket price... seriously i think it should have stayed at 0.1.

[anonymous_acc]

Is it normal "blank" first page?

I would test your casino.

my BTC address 1cccp7JUoQVAo2kKqSyGBs3zGmZcwoHe3

[ShaTwo]

Is it normal "blank" first page?

The problem has been fixed, looks like Firefox doesn't support MP3 Files on it Audio API, sound effect was replaced with the .ogg file extension and the problem was resolved. I tested on the last Firefox version and seams to be working fine now.

Could some some please confirm you can see it correctly on Firefox now?

Important: Please delete your cache, before testing.

[dooglus]

The free plays are also nearly worthless as 1BTC already adds a single free play.

If you're talking about the 'high roller bonuses' then it looks like you need to spend at least 5 BTC to get free plays now, and those free plays happen automatically; you don't have to claim them.

The free plays you get for winning, on the other hand, are hard to claim.  The FAQ says: "For each Free Play you want to use, you have to play 1 BTC".  That means you have to play 100 draws to claim one free play (maybe the FAQ is out of date, and should say 0.1 BTC, who knows...).  Those 100 draws will on average earn you about 15 more free plays, which you'll also have to claim.  So you'll end up with more free plays than you can ever claim.  In effect, every 100 draws you pay for will give you 101 draws.

Please let me know if my analysis is wrong here.

[SgtSpike]

The free plays are also nearly worthless as 1BTC already adds a single free play.

If you're talking about the 'high roller bonuses' then it looks like you need to spend at least 5 BTC to get free plays now, and those free plays happen automatically; you don't have to claim them.

The free plays you get for winning, on the other hand, are hard to claim.  The FAQ says: "For each Free Play you want to use, you have to play 1 BTC".  That means you have to play 100 draws to claim one free play (maybe the FAQ is out of date, and should say 0.1 BTC, who knows...).  Those 100 draws will on average earn you about 15 more free plays, which you'll also have to claim.  So you'll end up with more free plays than you can ever claim.  In effect, every 100 draws you pay for will give you 101 draws.

Please let me know if my analysis is wrong here.

I came to the same conclusion.

[ShaTwo]

The free plays are also nearly worthless as 1BTC already adds a single free play.

With the new Price Structure, Free Plays can be redeemed by playing BTC0.10, so if you play BTC0.10 and had free plays from previous winner rounds, you will get 11 plays instead of 10 plays.

Important: Delete your browsers' cache if you still not seeing this on the page.

[Micon]

wow I can't believe how late I am on BitMillions. 

bravo OP / amazing site.

I bought some tickets today of course.  I will be covering this site in my next Bitcoin Magazine gambling article.  Absolutely brilliant.  Tough fight between this and bitcoinvideopoker for best new pure btc gaming site recently. 

love seeing projects like this pop up - and also pretty awesome how you did all the work then just dropped it on the community almost perfect - really, really great job.

I will be firing.  This will create another good blockchain stress test similar to SatoshiDice - I think this will be that level of popular.

[SgtSpike]

wow I can't believe how late I am on BitMillions. 

bravo OP / amazing site.

I bought some tickets today of course.  I will be covering this site in my next Bitcoin Magazine gambling article.  Absolutely brilliant.  Tough fight between this and bitcoinvideopoker for best new pure btc gaming site recently. 

love seeing projects like this pop up - and also pretty awesome how you did all the work then just dropped it on the community almost perfect - really, really great job.

I will be firing.  This will create another good blockchain stress test similar to SatoshiDice - I think this will be that level of popular.

I agree, stellar site.  Am looking forward to your writeup. 

[dooglus]

Important: Delete your browsers' cache if you still not seeing this on the page.

It's unreasonable to ask people to delete their entire browser cache whenever you update your site.  The cache is there to prevent me having to download the same pages over and over.

Is there no way you can get my browser to notice that you've changed the FAQ page without me deleting my whole cache?

I've viewer the site in a different browser, and the FAQ really is different there.  I'd like to be able to see the new FAQ in my regular browser without then having to re-download all the pages I usually have in my cache.

[payb.tc]

Important: Delete your browsers' cache if you still not seeing this on the page.

It's unreasonable to ask people to delete their entire browser cache whenever you update your site.  The cache is there to prevent me having to download the same pages over and over.

Is there no way you can get my browser to notice that you've changed the FAQ page without me deleting my whole cache?

I've viewer the site in a different browser, and the FAQ really is different there.  I'd like to be able to see the new FAQ in my regular browser without then having to re-download all the pages I usually have in my cache.

all he needs to do is add ?v=1.1 on his links, or ?v=1.2 ?v=1.3 etc, etc.

or if he's using codeigniter-style urls it could work by putting some other dummy variable on the end:

eg. change http://blah.com/faq/v1 to http://blah.com/faq/v2  where the 'faq' code may decide to just ignore the version variable

then your browser won't show you the cache because it'll think it's a totally different page.

[dooglus]

all he needs to do is add ?v=1.1 on his links, or ?v=1.2 ?v=1.3 etc, etc.

or if he's using codeigniter-style urls it could work by putting some other dummy variable on the end:

eg. change http://blah.com/faq/v1 to http://blah.com/faq/v2  where the 'faq' code may decide to just ignore the version variable

then your browser won't show you the cache because it'll think it's a totally different page.

Take a look at the source code for https://bitmillions.com/faq - it's just a little javascript, which presumably loads the FAQ content.  I tried loading https://bitmillions.com/faq?really! but it gives me the same old cached content since the javascript hasn't changed, it's the deeper content that has.

[payb.tc]

all he needs to do is add ?v=1.1 on his links, or ?v=1.2 ?v=1.3 etc, etc.

or if he's using codeigniter-style urls it could work by putting some other dummy variable on the end:

eg. change http://blah.com/faq/v1 to http://blah.com/faq/v2  where the 'faq' code may decide to just ignore the version variable

then your browser won't show you the cache because it'll think it's a totally different page.

Take a look at the source code for https://bitmillions.com/faq - it's just a little javascript, which presumably loads the FAQ content.  I tried loading https://bitmillions.com/faq?really! but it gives me the same old cached content since the javascript hasn't changed, it's the deeper content that has.

well that implementation kinda kills my idea