BitMillions.com- More than ฿ 1,400 in Prizes - Play with only ฿ 0.01!

[dooglus]

Can you prove that?  

You know... Bitcoin and stuff.

The pot for match-3 was far too high.  It really was worth playing until you hit it, because it was incredibly unlikely you would make a loss - unless someone else hit it before you.

The three pots will end up being 6643 BTC, 26 BTC and 0.48 BTC on average.  Having 400 BTC in the match-3 pot put it around 16 times bigger than it will be on average, and made it well worth shooting for.

You hit the match-3 pot about once every 10,000 draws.  10,000 draws cost 100 BTC to play.  So you're paying 100 BTC to win half of 400 BTC - well worth doing, even if you never win any of the other pots (which, of course, you will).

[ShaTwo]

The pot for match-3 was far too high.  It really was worth playing until you hit it, because it was incredibly unlikely you would make a loss - unless someone else hit it before you.

The three pots will end up being 6643 BTC, 26 BTC and 0.48 BTC on average.  Having 400 BTC in the match-3 pot put it around 16 times bigger than it will be on average, and made it well worth shooting for.

You hit the match-3 pot about once every 10,000 draws.  10,000 draws cost 100 BTC to play.  So you're paying 100 BTC to win half of 400 BTC - well worth doing, even if you never win any of the other pots (which, of course, you will).

You are correct, pots were initially funded for a 0.10 Ticket Price ( Average 66430 BTC, 260 BTC and 4.8 BTC ) when we reduced the price, we knew that the pool what much higher, but we decided to eat the mistake and reward our first batch of winners.

[ingrownpocket]

Can you prove that?   You know... Bitcoin and stuff.

You can check all the ticket he purchased on:
https://bitmillions.com/address/1BT4xWe5ATp37CwpxwnYViUDJq62nKbFvq

And Payment Transaction has just been sent:
https://blockchain.info/tx/d873bad7cd1a4b31f3dd634f23ce21913fade0d22abab70f09eddefd67b8381f

Congratulations to our first Lucky Winner!

I just want to know if he really is the 'owner' of that address.

Can you prove that?  

You know... Bitcoin and stuff.

The pot for match-3 was far too high.  It really was worth playing until you hit it, because it was incredibly unlikely you would make a loss - unless someone else hit it before you.

The three pots will end up being 6643 BTC, 26 BTC and 0.48 BTC on average.  Having 400 BTC in the match-3 pot put it around 16 times bigger than it will be on average, and made it well worth shooting for.

You hit the match-3 pot about once every 10,000 draws.  10,000 draws cost 100 BTC to play.  So you're paying 100 BTC to win half of 400 BTC - well worth doing, even if you never win any of the other pots (which, of course, you will).

I've thought about that yesterday, but since I could not afford to lose 100 BTC I stopped thinking about it and started doing other stuff (to stop feeding that gambling desire I sometimes have).

EDIT: Goddammit, my English sometimes is broken as hell.

[dooglus]

I've thought about that yesterday, but since I could not afford to lose 100 BTC I stopped thinking about it and started doing other stuff (to stop feeding that gambling desire I sometimes have).

Ha!  Me too...

I was thinking if I did go for it, I would have to buy lots of tickets all at once to increase my chance of winning before somebody else did.  There's no good way of buying lots of tickets for the same draw without spamming the blockchain with transactions with hundreds of outputs.  I calculated that I could buy 288 tickets with a single 10k byte transaction (each ticket you buy adds 34 bytes to the transaction size) but that I'd want to buy many more than that to have a reasonable chance of winning the pot (odds of 1-in-10k).  So I stopped thinking about it. 

[eleuthria]

Love the site, very well done.  Only one thing I'm a bit confused over:  Is there a reason you decided to have the tickets pay out for each play?  The current method is going to end up filling wallets with a lot of small inputs, making it harder to spend without long delays and/or high fees.  Perhaps a separate address to purchase a ticket which sends your total winnings after the ticket fully matures?  This saves you money, and the player as well in the long run.

[dykast]

I sent 1BTC from 1KjmoMmUMRfwFk7xu3gNXRKyBT1R13sRh9 .  It doesn't show up, but when i follow the block, it seems that my 1BTC is getting my plays at 1HDbwG9R6ubEHA7FM63TUE5W8zCget7sYP.  I am not a blockchain expert so I am not sure what is going on.  Any help would be appreciated.

[ShaTwo]

I sent 1BTC from 1KjmoMmUMRfwFk7xu3gNXRKyBT1R13sRh9 .  It doesn't show up, but when i follow the block, it seems that my 1BTC is getting my plays at 1HDbwG9R6ubEHA7FM63TUE5W8zCget7sYP.  I am not a blockchain expert so I am not sure what is going on.  Any help would be appreciated.

We use the first Input Transaction as Sender Address, if you check on yours:
http://blockchain.info/tx-index/51216827/cb17e2e132d57fb3477b748e296d83dfc03393bd04ed6da9366b80dc2ebdfc8f

You will see that 1HDbwG9R6ubEHA7FM63TUE5W8zCget7sYP is the first one.

I recommend you to use a Wallet that allow you to do coin control like Blockchain.info

[dykast]

I sent 1BTC from 1KjmoMmUMRfwFk7xu3gNXRKyBT1R13sRh9 .  It doesn't show up, but when i follow the block, it seems that my 1BTC is getting my plays at 1HDbwG9R6ubEHA7FM63TUE5W8zCget7sYP.  I am not a blockchain expert so I am not sure what is going on.  Any help would be appreciated.

We use the first Input Transaction as Sender Address, if you check on yours:
http://blockchain.info/tx-index/51216827/cb17e2e132d57fb3477b748e296d83dfc03393bd04ed6da9366b80dc2ebdfc8f

You will see that 1HDbwG9R6ubEHA7FM63TUE5W8zCget7sYP is the first one.

I recommend you to use a Wallet that allow you to do coin control like Blockchain.info

Ah, I see.  I sent it from my actual wallet instead of blockchain.info.  Looked at my wallet and my winnings are going there. Sorry for the newbie confusion.

TY for the quick answer 

[dooglus]

Love the site, very well done.  Only one thing I'm a bit confused over:  Is there a reason you decided to have the tickets pay out for each play?  The current method is going to end up filling wallets with a lot of small inputs, making it harder to spend without long delays and/or high fees.  Perhaps a separate address to purchase a ticket which sends your total winnings after the ticket fully matures?  This saves you money, and the player as well in the long run.

It's possible to buy a ticket that runs for several years.  You probably wouldn't want to wait for the end for it to pay out.  A compromise like paying out every 100 draws would seem reasonable though.  That would mean payouts every 16.7 hours on average.  And if they always paid out on draws ending with 00 then players could easily know how many more draws until their next payout.

[eleuthria]

Love the site, very well done.  Only one thing I'm a bit confused over:  Is there a reason you decided to have the tickets pay out for each play?  The current method is going to end up filling wallets with a lot of small inputs, making it harder to spend without long delays and/or high fees.  Perhaps a separate address to purchase a ticket which sends your total winnings after the ticket fully matures?  This saves you money, and the player as well in the long run.

It's possible to buy a ticket that runs for several years.  You probably wouldn't want to wait for the end for it to pay out.  A compromise like paying out every 100 draws would seem reasonable though.  That would mean payouts every 16.7 hours on average.  And if they always paid out on draws ending with 00 then players could easily know how many more draws until their next payout.

Good point, I hadn't thought of the idea of buying a single ticket that lasted for a significant time.  An every-100 blocks payout ticket would definitely be a good compromise there.  I just hate seeing the blockchain bloat and difficult to spend outputs filling a wallet [glares at SatoshiDice].

[dooglus]

Good point, I hadn't thought of the idea of buying a single ticket that lasted for a significant time.

They actively encourage you to do so with their 'high roller' bonuses:



Incidentally, the 'play for' column is wrong in a few cases.  20,000 tickets will play for 20000/144 = 138.9 days, not 143 days.

Also, the most recent draw numbers are all messed up.  Is it meant to say 'CALCULATE'?  It's kinda ugly:



Maybe an 8 letter word would work better?  TH-IN-KI-NG?  Or just write the word without breaking it into 4 parts.

[ShaTwo]

Thanks for point it out this Dooglus, but note that since the price reduction, the high roller bonuses we ajusted to:



I guess the problem with the cache still make you see something different.

Also, the most recent draw numbers are all messed up.  Is it meant to say 'CALCULATE'?  It's kinda ugly:
Maybe an 8 letter word would work better?  TH-IN-KI-NG?  Or just write the word without breaking it into 4 parts.

Yes, I removed the A in CAL to make it fit, it suppose to be something temporal, but I never got to change it... I will change it after fixing the pre-compile cache issue.

Also is import to note that you get 10 FREE PLAYS when playing anything higher than 1 BTC, I think makes much more sense to play 1 BTC and you will get 111 plays ( 18 1/2 Hours of Playing! )

[🏰 TradeFortress 🏰]

I played a bitcoin, wish me luck? 

https://bitmillions.com/tickets/2149699da87f0b36196e2571264aba845c9af13e821109bbf7e8950465bf0e0c:0

[arij]

Winning!

https://bitmillions.com/tickets/2e7e4725fc9ac4819afecd89e1a78657fcf5d293b3e5c37b2ab9bf4f92cdd3e0:0

[ShaTwo]

Still waiting for the BTC from this win...

https://bitmillions.com/tickets/2e7e4725fc9ac4819afecd89e1a78657fcf5d293b3e5c37b2ab9bf4f92cdd3e0:0

Any ETA?

Since we couldn't send a transaction with 750 inputs, we needed to consolidate all the inputs to been able to send your payment.
Please check on: http://blockchain.info/address/1ETya2BCpwgTuz88ubiLPf2kUvMpUymhBq

But looks like didn't have enough txFees and we still waiting for this transaction to get confirmed:
http://blockchain.info/tx/71d791a4666bdad7b484f07f9299840b99a524e98823c3b6761137592df8cd00
We made it almost 6 hours ago and still doesn't confirm.

All the other transactions are already confirmed, so as soon as that transaction confirms, I will be able to process your payment.

Also we will have the Pool # 3 in Hot Storage, that will prevent this problem from happen again.

Please apologies for the delay, as soon as we have the consolidated funds confirmed, we will issue the payment and post it here.

[EDIT] Payment Sent! Sorry for the delay... it should not happen again.
http://blockchain.info/tx/f7263295b490656ca7b6345cabb0ae9a423058557d952dcc929d90cc9415bfc3

[arij]

No problem, Thanks for the update! BitMillions for life!

[dooglus]

But looks like didn't have enough txFees and we still waiting for this transaction to get confirmed:
http://blockchain.info/tx/71d791a4666bdad7b484f07f9299840b99a524e98823c3b6761137592df8cd00
We made it almost 6 hours ago and still doesn't confirm.

The rules for transaction fees are well known:

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.

The transaction you sent is 14846 bytes long, and so needs a fee of at least 15*0.0005 = 0.0075 BTC.  You only included a fee of 0.001 BTC so it's not surprising it's taking a long time to confirm.  What client did you use to make that transaction?  It seems not to be following the network rules for fee size.

[ShaTwo]

The rules for transaction fees are well known:

I tried to find documentation on this, but what able to do so... thanks for the info!
Could you please tell me where can I find it on the bitcoin.it wiki?

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.

The problem I have is that I don't know the Transaction Size at an application level, I just know the number of inputs & outputs, and I need to determine the TxFee based on that... any recommendations?

[Edit] I custom build the transactions with createrawtransaction method on bitcoind at another layer of the application stack.

[dooglus]

I tried to find documentation on this, but what able to do so... thanks for the info!
Could you please tell me where can I find it on the bitcoin.it wiki?

https://en.bitcoin.it/wiki/Transaction_fees

The problem I have is that I don't know the Transaction Size at an application level, I just know the number of inputs & outputs, and I need to determine the TxFee based on that... any recommendations?

[Edit] I custom build the transactions with createrawtransaction method on bitcoind at another layer of the application stack.

http://bitcoin.stackexchange.com/questions/1195/how-to-calculate-transaction-size-before-sending

transaction with 'in' inputs and 'out' outputs has size
(in*148 + out*34 + 10) plus or minus 'in'

so long as you're using compressed public keys.

Your transaction has 100 inputs and 1 output, so will have size 14800+34+10 +- 100 = 14844 +- 100
Its actual size was 14846.

Each input adds 147, 148, or 149 to the size, pretty much at random.  The average contribution per input is 148 bytes.  It's incredibly unlikely that all 100 inputs will contribure 149 bytes.  The transaction size is in the range 14744 to 14944, but spread out with a binomial distribution centred on 14844.

But... createrawtransaction returns a string.  Count the length of the string to find (twice) the size of the transaction.  Then adjust the fee, and repeat, until the fee is suitable for the length.

[ShaTwo]

https://en.bitcoin.it/wiki/Transaction_fees

I can't believe it, for some reason I missed the part that I needed... thanks!

Your transaction has 100 inputs and 1 output, so will have size 14800+34+10 +- 100 = 14844 +- 100

Thanks!

But... createrawtransaction returns a string.  Count the length of the string to find (twice) the size of the transaction.  Then adjust the fee, and repeat, until the fee is suitable for the length.

For security createrawtransaction is not accesible from the application layer, so I can not re-create the transaction to adjust fees.