[BITLOTTO] Mar 1 draw over $2000 or 50BTC! Tickets now 0.1 BTC for Apr 5 - page 24.

bitlotto

hero member

Activity: 672

Merit: 500

BitLotto - best odds + best payouts + cheat-proof

Quote from: Stephen Gornick on March 30, 2012, 07:05:26 PM

But the primary question I have has to do with the sha256 algorithm. The algorithm wasn't built to be used as a lottery picking system. Generally, using an algorithm for a purpose that it wasn't designed for can expose problems that might not normally exist when used for the algorithm's stated purpose. Using SHA256 for this alternate approach, is each "pick" truly random? Or is there some association where, lets say since the megamillions pick can only be 01 through 46 then does knowing that the character in the second to last character position won't exceed 4 mean that the resultant hash will be more likely to result in one that begins with one set of characteristics over another?

Because it's a sha256 of a random event we can be pretty certain that the hash is totally unpredictable. That's what we really need. A mix of digits that we can't predict. The chance of each digit are unknown until the event occurs. My main reason for adding the blockhash was someone could, in theory, create a list of every possible mega millions outcome and create a hash for it. They could then see if the hashes have certain digits at the beginning occurring more than others. This would give them an unfair advantage as they could manipulate their tx so that a tx hash occurs that has more of those digits. Adding the blockhash makes it impossible to figure out frequency outcomes for winning picks.

The main problem is really with the selection process. I'm actually in the process of possibly slightly altering the algorithm for picking the winner. The important thing is that I do it at least a few days before the draw of course. I hate changing it though, but I think it needs to be done. It does add a *little* more complication to the calculations. The problem with known ticket hashes prior to the draw is people could do frequency analysis of the tx hashes. They could see if by random chance some combinations of digits are not as frequent amongst the hashes. Then get tickets with those more rare combinations. It would be pretty tricky to do but I guess as the money goes up, people will try to get any advantage they can no matter how slim. I'm sure it would be pretty hard to do as the tx's go up there is a lot of tx's to analyze. They would also have to wait till the very end so it would be quite the feat for a very very tiny advantage.

So, to make it pretty much impossible to do any analysis I was thinking of rehashing ALL tx's!! It would make it harder for others to check the results casually but I'd release a txt file with contents something similar to this for every draw:

Code:

720b8516a286a6588ae636c16e8c550366931620623050b34d9dc0e3856c945c -> c533da9261c21db0bf12d9e6061b10f7652db674a6a0007ec9dfa1b9fe15e219  -
99a38da78eee8132ac2be9d2cbef69df7d81c2adf78423d9c2ee21819f70772d -> 6a4e06c1a1d4bcfd21ddc0bd060a09a92c58334c3aca067106c515beaf7b7bcd  -
.520000
b46482a6f375297e0c2dc74603fb0d455912a6748ca65efd8130a96211e9f36a -> be7baa0fc748e3c44e5cc26f9165ed15fc7da62db3443a6cefbf0cf4986575d8  -
.150000
5ae95246eabb8fb7229db1fcc3aebe258d1a68aae21b4747ecf992a946e902df -> 093c9522b279bf0653304eb33cc9e6b1599199bc413dd647cf99fe604f6d4561  -
9120dec5bfe999743ba3b44d7828dd76196a82cca3486497b74e37fd6a8500d0 -> 198cb6b9ebd194bd79f19fac8b153808b385024929c1cffd320819be4983fa38  -
367b185f2af5d60a72469839d66e07f4c0145a646c48bc6fb2a8304096865266 -> a9a52a45e7252e7e0238f4dc7cdf0f7d6d2ed5a3d4c70e55f9960c103cf1d4a1  -
985ec0242ba5ca7d8af982644eaa056d8e1af8de3bb5c056aa39ae3ff358ab8b -> 7ea9843c17026e2c7681cd1185b4edc32e51aecc4414174cf5082bbfd8aa8b58  -
5b2b7fe513b77bf333b3e202f370699cb914526cdeb49f14b0df78ae16608926 -> 97cfa87250deab7f2d821fc26a7eadb561428f28b1540af51baa22867111994f  -
5dc34f516c14115ce10051f3f73f92892ce704083d22832e4d155f6c87c3abc6 -> 2312b230ae328384202d7b65b7bac25d036a5bd0a86b805c56cffbdf618eac35  -
15ce39e11aecf0a402d2da8bd829cec6505b5fbad023ba8021f663df1d077716 -> 6bdd36da928e20617baa139e0ee6b1c096d891cad8cb5fa2997abc9c7eb4c8cf  -
b67003391d72709ce1b8cf159a7c38e69ce09cc64f8c509fb898dd20af967237 -> 09a63f04c4775eb5976d68df695f679667a59cb68bc07afa889f8539bc2591df  -
1328e3d465132c4b012d44e5d28bff76e6f31566dc87f1e59c593bc94b73da39 -> e767f076d208cfdcf388bc0e7edd06367d95c1dc9a08c87bbd6848ecf4fb23bc  -
7514500e9d536146575055de0f6ef9675d4b829f3329a8e4a2c20cc4bdcd09dd -> 3550fb0a84247be1656d46b23874ca357827e0423cba2e58f56062c6a4bb919a  -
bba5ee2812dbb43da4014f27c83a63488dcc2305ece1f7412b8646911cc9ba67 -> 8c023c452e1cc5207eb8de8d3af3b132aee553adc4098d4767a7543125025ac5  -
111dc53308d19a5a74a0537165a7f3a002269a5049d590f7a664909c3c07263f -> 5518205694948464143c4b30959ce36b8f2dd431502e7bbbbd9b361742a683d3  -
07f664b68ec82238a3465ce570215eb001ef795f906abe67e8f11e7d4fa1e338 -> eec308f8df80ad59dff7c9902acde257feb9efb6f1f499838d1a08ef06c518ec  -
470daaedb373af852030e71eace9cfffe51f2e38fb085f08d42098e627d58b82 -> e71dd2934da9c61b045fb7a1ed5213ad6cdb8533191297632ee0287a3bca8bcc  -
ba5e9c70817ffe8148d99774b4dc777dab5949727c8f7a73e49624d662501f02 -> 8d07912630e1ba0b96fe72d0bcfccf906498b6b9f12bfbb4aff55558de673535  -
9629cfd252f00c0de1063874e46ed3f574a0732425ae28e2776502da8613b017 -> a64fd00c9f22b7ee992ee6949f4e0ae2c1ff658ff04eb8c4fe3aad5612c9ee77  -
9e37ee5af0fc5d0c20cf1f7e93a579ff149a29bcdbc92da9181bde88074170c5 -> b2919892d4aca12f2269bf4401a86bb6abfd2487ebabd9402cf3e5ed1996f5b5  -
4.260000
bf9f0c11fc2f1ff82fa5f4b4769169c619b237dd62e93fbcdf2e091abc1d29ec -> 233c01ffba150ad136ee4d589d03ea9f82067e6bce581e6a404d200f0fddb463  -
.250000
f08f16cb4acac8e334d4e99155085cd5f03730936b06e1ea68c2d1fd0ece18d2 -> dba501b70e179611a39515b2c7c32882a9ecc56154444f351994420c616ce3ab  -
.350000 
59e8d1b6c351cb4d2a738f246a74f373f5245bdf0e485e622d4411a048ac8802 -> 52d8914b1aea413a6ecae1108cb6653bdf38799d3a152bfc15a9de64f0fbfaf5  -
.250000

(I added "test" at the end of the hash then sha256 it, and yes the 0.15 hash can't win since it's too small)
This would show the original tx hash and the new hash that's used for picking the winner.
Doing this makes it impossible for anyone to analyze tx's since the hashes can't be know till it's over! I'll probably end up hashing the tx's with the winning picks added. THEN use the new hashes to find the winner.

It fits in with BitLotto's goal of being cheat proof and still remains transparent.

Unless of course someone can think of something more simple and still cheat-proof? Wink

bitlotto

hero member

Activity: 672

Merit: 500

BitLotto - best odds + best payouts + cheat-proof

Quote from: Stephen Gornick on March 30, 2012, 07:05:26 PM

One risk is ... what if the block isn't solved by the time the lottery starts? We've had hour plus delays between blocks before. I'm sure there are several solutions, including reverting to the last block solved before the lottery pick occurred I suppose. But not having this decided in advance could give someone an argument against the results on the off chance that this actually happens one day.

Very good point!!! Ya, figuring it out in advance is definitely a must! It would have to be hours of no blocks but I guess it's possible. In that case the draw would not be over. IN the VERY rare chance that occurs, the lottery numbers will come from the mega millions draw that occurs on Friday but with the same time limit for tickets having to be in. Wednesday block time. I'll add a note about that in the details.

Quote

But the primary question I have has to do with the sha256 algorithm. The algorithm wasn't built to be used as a lottery picking system. Generally, using an algorithm for a purpose that it wasn't designed for can expose problems that might not normally exist when used for the algorithm's stated purpose. Using SHA256 for this alternate approach, is each "pick" truly random? Or is there some association where, lets say since the megamillions pick can only be 01 through 46 then does knowing that the character in the second to last character position won't exceed 4 mean that the resultant hash will be more likely to result in one that begins with one set of characteristics over another?

I have thought about that. I'm really busy right now but I'll tell you my thoughts on that the next day.

Stephen Gornick

legendary

Activity: 2506

Merit: 1010

This MegaMillions madness is making me think about the long-term possibilities and risks of BitLotto.

Now since the winning hash is a SHA256 hash of: luckyblockhash+lotterynumbers I am comfortable trusting that a miner won't be holding on to any blocks mined to affect the results of BitLotto because at that time mining that block occurs the MegaMillions lottery results are not yet known.

One risk is ... what if the block isn't solved by the time the lottery starts? We've had hour plus delays between blocks before. I'm sure there are several solutions, including reverting to the last block solved before the lottery pick occurred I suppose. But not having this decided in advance could give someone an argument against the results on the off chance that this actually happens one day.

But the primary question I have has to do with the sha256 algorithm. The algorithm wasn't built to be used as a lottery picking system. Generally, using an algorithm for a purpose that it wasn't designed for can expose problems that might not normally exist when used for the algorithm's stated purpose. Using SHA256 for this alternate approach, is each "pick" truly random? Or is there some association where, lets say since the megamillions pick can only be 01 through 46 then does knowing that the character in the second to last character position won't exceed 4 mean that the resultant hash will be more likely to result in one that begins with one set of characteristics over another?

I don't know nor do I think that for the current sub-$1K BitLotto prize is there anyone putting much though into any using characteristics of SHA256 to gain an advantage at BitLotto. But with MegaMillions at $640 million or some similar number, at some point the BitLotto jackpot could grow to where if there is any gain possible, the incentive will be there for it to be found.

I've no idea the answer, I just wonder to what degree the question has already been considered.

bitlotto

hero member

Activity: 672

Merit: 500

BitLotto - best odds + best payouts + cheat-proof

Otoh I like the signature! Thanks!

Oh, and I guess it's worth mentioning?, so someone does not try hacking blockexplorer hoping to alter the site to fake the hashes or something, that the hashes come from BitLotto's own wallet itself for determining the winner. Blockexplorer is a great site to check the results though!!!

bitlotto

hero member

Activity: 672

Merit: 500

BitLotto - best odds + best payouts + cheat-proof

Quote from: Otoh on March 30, 2012, 03:22:25 PM

oops BW ty, I forgot the total on BE is -1% for the JP

I think it would be cool if you could commission some Casascius 1 BTC coins with your web site URL around the top www.bitlotto.com that people could use for promotional purposes, tips etc -

That would be sweet. Probably out of my price range though. I think the BTC in my name are in the single digits! LOL. It's the few lucky ones using my service that seem to have more! Wink

Anyways, if the odd chance someone does pay a tiny bit extra (none 0.25 multiple) I'll just add it to the jackpot. Minus the 1% and pay it out. I honestly don't think it will happen that often though. That tiny little bit will probably help in paying any tx fees that occur. I usually end up paying a bit as there are so many tx's being summed together. I'll add a note in the details on my website.

Otoh

donator

Activity: 3052

Merit: 1110

oops BW ty, I forgot the total on BE is -1% for the JP

I think it would be cool if you could commission some Casascius 1 BTC coins with your web site URL around the top www.bitlotto.com that people could use for promotional purposes, tips etc - I don't think that Casascius offers this service as yet but someone should suggest it to him as many companies may wish to have a run of promotional physical Bitcoins made (sometimes maybe on pre-order if that's the right word, so that the run isn't produced until enough people have pre-ordered the total quantity required to make it happen, if there weren't enough orders in by a given cut off date then they just get regular Cas coins, this could also work for limited edition coins) - also he would probably need to have his own web site https://www.casascius.com/ prominently shown first which I'm anyway surprised isn't on the coins atm as far as I can see, around the edge would be good too or a shorted version like http://goo.gl/ajbZb maybe

& this would make a nice round 100 bets coin with www.bitlotto.com URL around the top - great for those little client gifts & perks where you don't want compliance or the regulators to know just how generous you've been Wink

Stephen Gornick

legendary

Activity: 2506

Merit: 1010

Quote from: Stephen Gornick on March 17, 2012, 09:25:42 PM

I notice the winner of the last draw (March 7th's) hasn't gone public nor has spent the funds (102.5275001 BTC) yet:

The coins were spent shortly after that post:
- https://blockexplorer.com/tx/c7cfda90010b1629ace639e3b996cd1eb36473510c9f5ea9c07ee4fb9366b96b#i4919097

But the winner remain anonymous.

That's another difference that differentiates between BitLotto and a state-run lottery like MegaMillions!

BurtW

legendary

Activity: 2646

Merit: 1137

All paid signature campaigns should be banned.

Quote from: Otoh on March 30, 2012, 09:24:02 AM

Quote from: BurtW on March 30, 2012, 08:56:29 AM

Quote from: Otoh on March 30, 2012, 08:06:47 AM

I vote announce & start that any amount may be sent & what's not divisible by 0.25 coins (the last left over bit) goes in to the JP tip jar starting with next week's May lotto (to keep things simple this time, as we've already had the one major change this month to accept multiple 0.25 bets in one tx) & I confirm that I shall be seeding it with 100 coins on day 1 or sooner if bitlotto sends me the address beforehand which he said that he's going to do

Second. The 1% rake is fantastic. This will keep the rake the same but give bitlotto a bit more - either on purpose or by accident.

actually I meant for any over-payments portions to go to the pot as bitlotto said; it keeps the total received = jackpot, so nice & simple, but I'm cool with them going to bitlotto as a tip for vanity amount bets etc also

edit: jackpot now plenty enough for a BTF Lab's BitForce Single Tongue

I get it now JP = jackpot, I was wondering about that. Either way is fine with me. I can always send a donation directly to bitlotto. It is nice to be able to look at the block explorer and see the total jackpot amount (minus 1%).

I cannot decide. You all decide. It is not enough to worry about either way.

Whatever is easier for bitlotto - that is my vote.

finway

hero member

Activity: 714

Merit: 500

This is really facinating lotto ,
just got in this month,
hope this lotto grow to 10kBTCs size this year.

Otoh

donator

Activity: 3052

Merit: 1110

Quote from: BurtW on March 30, 2012, 08:56:29 AM

Quote from: Otoh on March 30, 2012, 08:06:47 AM

I vote announce & start that any amount may be sent & what's not divisible by 0.25 coins (the last left over bit) goes in to the JP tip jar starting with next week's May lotto (to keep things simple this time, as we've already had the one major change this month to accept multiple 0.25 bets in one tx) & I confirm that I shall be seeding it with 100 coins on day 1 or sooner if bitlotto sends me the address beforehand which he said that he's going to do

Second. The 1% rake is fantastic. This will keep the rake the same but give bitlotto a bit more - either on purpose or by accident.

actually I meant for any over-payments portions to go to the pot as bitlotto said; it keeps the total received = jackpot, so nice & simple, but I'm cool with them going to bitlotto as a tip for vanity amount bets etc also

edit: jackpot now plenty enough for a BTF Lab's BitForce Single Tongue

BurtW

legendary

Activity: 2646

Merit: 1137

All paid signature campaigns should be banned.

Quote from: Otoh on March 30, 2012, 08:06:47 AM

I vote announce & start that any amount may be sent & what's not divisible by 0.25 coins (the last left over bit) goes in to the JP tip jar starting with next week's May lotto (to keep things simple this time, as we've already had the one major change this month to accept multiple 0.25 bets in one tx) & I confirm that I shall be seeding it with 100 coins on day 1 or sooner if bitlotto sends me the address before which he said that he's going to do

Second. The 1% rake is fantastic. This will keep the rake the same but give bitlotto a bit more - either on purpose or by accident.

Otoh

donator

Activity: 3052

Merit: 1110

I vote announce & start that any amount may be sent & what's not divisible by 0.25 coins (the last left over bit) goes in to the JP tip jar starting with next week's May lotto (to keep things simple this time, as we've already had the one major change this month to accept multiple 0.25 bets in one tx) & I confirm that I shall be seeding it with 100 coins on day 1 or sooner if bitlotto sends me the address beforehand which he said that he's going to do

bitlotto

hero member

Activity: 672

Merit: 500

BitLotto - best odds + best payouts + cheat-proof

Another interesting draw could be next month! Earlier in the thread Otoh mentions that he may spend 100 BTC in tickets. That would be 400 tickets at the beginning of the month! Who knows what kind of growth will occur after that.

bitlotto

hero member

Activity: 672

Merit: 500

BitLotto - best odds + best payouts + cheat-proof

Quote from: Otoh on March 29, 2012, 03:24:26 PM

As that's now implemented & to save you the hassle of returning odd < 0.25 BTC amounts to anyone who can't do maths, why not make the rules that all money sent gets put into the jackpot regardless & if anyone sends over what is divisible by 0.25 then that is treated as a tip to the jackpot, it will be less than 0.25 BTC so no big deal - maybe peeps want to send their lucky 5.55 (22 bets + 0.05 coins tip) or 7.77 BTC (31 bets + 0.02 coins tip), before it mattered (like when I was totally maths/wallet spastic or whatever Embarrassed

) but now it's a trifling amount & you shouldn't need to be working out & sending back < 0.25 coins imo

another advantage with this is that the total shown to have been sent in is always correct for = jackpot

or the extra could be tips for you or a good cause, jp would be a fraction less but negligible difference

edit: bet you get a bunch of 6.66 BTC tx with 26 bets & a generous 0.16 coins sacrificed to the tip jar Wink

That is actually not a bad idea! It is kind of a pain returning little bits of BTC. Before each ticket had to be bought one at a time and some still would pay 2 BTC for example. That would have been 1.75 not valid. Now that it has changed the most it will be is 0.2499999. Hmmm. Ya, you are probably right, it should just go to the pot.

What do people here think? Is it fair to implement that rule now? No one has yet made a payment NOT divisible by 0.25. Or is it better to mention something at the next draw address announcement and do it then?

bitlotto

hero member

Activity: 672

Merit: 500

BitLotto - best odds + best payouts + cheat-proof

Quote from: Stephen Gornick on March 29, 2012, 02:10:48 PM

And that ticket purchase (worth 25 BTC) puts this month's BitLotto into the record book with over 600 tickets for the month (as far as the most number of tickets sold for a single monthly lotto) as well as giving this draw the record high in terms of BTCs (now over 150 BTC).
....
Perhaps the ability to purchase multiple tickets with one payment will some day boost BitLotto's monthly jackpot above the previous "valued in USDs" record, but that probably won't occur this month.

Ya, this month kind of caught me off guard. I'm hoping the easier payments do make it more popular. I imagine some people with lot's of BTC may not have entered only for the reason it was too much hassle to buy tickets.

I used to keep track of USD values but with the price changes I kind of just left it at BTC values. I think I remember one being worth about $1200 USD at the time or something similar.

bitlotto

hero member

Activity: 672

Merit: 500

BitLotto - best odds + best payouts + cheat-proof

Quote from: BurtW on March 29, 2012, 10:39:38 AM

I just bought 100 tickets. I would like bitlotto to please send me a file containing all 100 official hashes. Also is there a web site or script I can run that will take my initial hash as input and give me a list of all of my ticket/hashes so I can verify the values myself and compare them to the "official" entries? Adding an input box to the bitlotto web site for a hash and a number of tickets would be pretty cool.

I'll look into adding something on the website! In the mean time:

Code:

#!/bin/bash
hash=be12265113cf6012dfecda1cf7d23de321b852135c37d139f0123279c2e68665
for (( c=1; c<=99; c++ ))
do
	echo -n $hash$c | sha256sum 
done

Code:

be12265113cf6012dfecda1cf7d23de321b852135c37d139f0123279c2e68665 -
d510cb891cb4ba4fda40579e97253e87485a0138a794d79b1aab942d9d3dbcc9  -
9b95f898845e4dfd680b76138009d60afd75657c4efb61a140eaa24c6fd31ace  -
77b4de84d1d91af427dd37090c64b735e7576acc96de05b63d3ebf7d4211a0c1  -
5f42899ace7d785e94ba6ab2a6537a16ad49eec8f5a014be47685aaff862bcc6  -
8eea925d05a619be3702a4028ee6c9060c9beaa087f7d6029cb9c3fbc91f8920  -
b5f67b6b3124746f10ad55f37db1f1021e3b98f275ed37e0f3497f9f81f0c379  -
38b78257f4d777755b0961b0416654fa9c0baa387a83d58a95d9d495d85195a0  -
75d7d79465a31f37768d9733bf9ede03879d77a946a415fec97a09fd9d52643f  -
2ef0bc957fdcebb14869844916e61a90e041d9de176f76368947034d5f4d0aef  -
0525f323f83110016a367d489ba179b7001ebdb6a339da781265d7300f663dd1  -
5a6426d39e9e3ce52c797162adf6931592d348a594de230401c59e3596209c68  -
b0e6e70174c77d0d592d30484e176c064d8d8ce3deac5565513eb4a0768ca529  -
0e4677dbeea256cecc00b97d5a2ce07fa52b0d55b455ddaa4e15b123fa087e4e  -
d79e399b9738747439468664ea9af3e74d4ca108972968a86a40508e8c8c41d8  -
60eff396998d0e3e5ea41c404e34bf6072461aa7b08a17fec0cf0ac34a61b1a6  -
7a779b6ed5d71fdd42ebf3c5e0c4b8c5c807f11f2984497bfbebad1729470ceb  -
2feaf36c62d0de3ff387c5c0dd07e6d8acfc4812515fcf12c0a37fc94ae3ccd8  -
cbdab27b4a04ff12895117f7ffe76589500c52463a3680a6ad96db5b0cd6323c  -
1f68427c3ccdb49d874a742483fe5e10a3cc7dc448d285d6d2f42c706e8fc8b4  -
63584db02a7bbe5060d603cb90b4f3a62f5cbc4de0ee4c52b8da5ea8dc2b66b0  -
11c37b77ed8ada1ae473aef222a9128b73f76248c03768da0152cab414275cd0  -
d36c8408a1243d199462f7ad02f6d4fb3922569d0c4287ad6f7f265316e0150e  -
1b6033049aadf3b46ea4b5f91aa266ed92b126a4ce5f347746c00cd8e647fcf1  -
c31b5693515d38c5bdf47e75a7eeedb01ff26ec6dfdb5b094adafc9a542ce591  -
b9f4778c85225a57d0c0897bf172054ec1fc48afe994be78c2b7d8fd68f4d983  -
c32cdb7d39d0c92c57edfe6d92ab291baf51ca64ab610781ce0ed1404b80523b  -
d3cb3ec93a7ec0ac9f5161506ee27e0931768ae8d4a31a43360575a7b492a36c  -
cb4fbf6fc15da722c40bd9ad313929db826b233e6bed17c5c96917205dbecaa9  -
7f765f077e4639d55e5f5fea5dc5f33b6dc42534b27800e380bbeb8a8824daea  -
be4e4ae82ea06af03c3f181060431e760d16e8cf9ceea76f9da6f24ffebc3528  -
459bad709ea9e02ca782ed64651952a49ab0284229209941ad9d29fe910bd6c6  -
a377f31ba749959eddcb6c1501ff25e9eef2d2ddfbfdc42a0fb4f3b9fbbdc1af  -
10b21980c28106750b42ac8c06dbcaa65123d4940fcf5f1f970829f9c61093e9  -
a11c6f628659e7f30f7ab81f84c3018898c8621d2e4b374e364e5db07691ea8c  -
d39d99cba5d7102132bb4465668a4b495c06901b865c1bb682989311d38cbe98  -
8cb6c812a8743c9c8b7c1a1d2bb5fe78cfe96d06fd398545997ccf2433bf6966  -
cc3e7fce0228c4be210fb193c63f05afea74fc3885e539b04f86e780188dccdb  -
f2515ffeadeae12615ca2003dbdc277084bf90f92128b83d01681f098ff8fe36  -
11b0500988fd290ec1a78df677966d86f1411123e2ffa1c8c5e5529d66739dc8  -
e55b365702fef6d6e532d4129b94c17129f72d18a392372ffeb64e5abdd96299  -
19e2f8ea2d43bc634c3d9e2eecd93ba4835147d5c14704d64da92c9c34bfc895  -
218accc89d2d30fd4606503f3859ce278cf04ab3b4f93325f14c4980a1e5894e  -
9913985e60a0874dbba3fa32efd94fcc4d7de14d1dbe0ae65ec50a99fef3b29f  -
58c4705feafe1f07baf6311f5d696c785c06cf836b4cf0fbd174dfce1788d3b2  -
f7508273e875ba72c97c02fac00d899647ca91d2f5fc636bede956d9d3836570  -
b2771d2f787249be91d410a4cdec8c08ca2a7f4aadd2f64e6a5734d52b3dbf43  -
ab31c03d4a8728eacc447f7581d40983ff9a50bc30138c06f74aceaa768f8345  -
890fedd15bb8665d96467b09fe6cabc21b55bfcedde96e68b7e1655a5fe5ac88  -
7d0dea5c73aab7a4ba349b3666335d987bee1ccd67e05e8a3c6b7b15314cc63d  -
bd50733a60fc8f504093e3376c5d357cfe690f00d6fea9dfe50238d8a86160bf  -
a3166795c86e42c61958189a075ae4785eba4ad61c99d290140122736c45046a  -
8b5e838894b22e153c9412bac63adc485d35f44c29bef02709e20e9151a7b316  -
3832415307553a964499135be32757e633948b973d2ec748571a180db1c8ecde  -
e9177442d5a5130981765422d4e18427b43c3f4ecbcf12dbec92c8816e6ccec4  -
17afb4ab06fc1e39ebcade76c1f3aa6fc054eb941a942f560d489de9d9246980  -
6fa9d5548ff781c10e0dcd905214563e6faefd48f21c2672d5819acb61b5e0c4  -
eb3ef482777c12074bd985ad60cd678c70ff74868028b3baf3f25b6a3cbd3354  -
b4675cc2163ab748d6ad6639df55c49ed5818146452a625d58a89917eb3969a3  -
8139d7ffb71a9bb16c440270cba7aa964805aeb63200bbed9954e1b2f0c6b823  -
e2e1b3de864a80ecfbdba094df25c8909c6cea3bd2af1ab08b173477030a5b11  -
9e503db5ce5844795b534cb213dbd8a94c9a28981c94ab8496ef94a323fafe70  -
2d374ac31c76b8e91cd7957e5b949d84fba8c00153143dc3b71a015e6b2a18fb  -
9a6893bd977a43ff2eb218e2e396de179f1326b58490eb18412efa06f954cb19  -
98b67ddc7f11da131dfd1a09d737a0518257dd148665ed71b70374f1e8a7ece0  -
43f57c2443134f702f2848b37c1f4758b42f1c567bf8affdc252eaaaa2f23150  -
24ab44bfeda9c2138ff9ab17cb54f4a57af8756cb860e2c65a60b63756d757f2  -
032605123c3e6eff8a150d5811371bef2f249bca70ee439fd2ead0ad96ef3f03  -
3db1108da71a4901660b92d91c56d9646e9d8a99ec9e4bf4081daaa21b5465c6  -
b1a31693a56e81ebeca8a1db67e85ff1cff1d8df60e69d3b7a646dbcadec308e  -
8d2429f093809de1055e1c5415a7733aa768999606ccfc7592fee2544eb70532  -
61f8ed8617c109acc9ba0a3ead4c86ab8fa8cc8aef05a0adb90257a138f0e2a7  -
5d53a50abc631ba80c931d6c8cd2ad53cea5b7ec5d09935d9539c4aff9cdf47e  -
268ce2383e4622806459a24428894146f409561a8eec63ded3537240dcf9b46a  -
6bec5e44ee762a9ad921284dc25070b4052f466670caddf639125bf8f6c6adfc  -
f09ea827ad920793799572ff1c7a4d682b90c8da1ae1c351421c2b36f5d84b30  -
d117a9bd9030f0c3def344c318289d1ac9521813f7b1dd498768302c9aa07ee6  -
cc0224e1529792737ce3e983e11e2dc01975585994d6898c26963a755dac9c45  -
4f8bc02a8b701b7ba22574ad1f420899e6115b101b048f1f0c6090a1235febd8  -
75b01b407aaa88dfa59d9dc8b61e5e8581f4c23e7203588058dde69e33a36ea1  -
b92ea441db6e77658135e208ec5210d1cd5d83ea62a4963f6570e8c9976aeddd  -
cbf06a8d953ddca069559e4ff187441ce01b0728b87d46c7b2ba5e1d58dc9d75  -
a79c673097bbd64fc474ca151d7f64dfdb8be99b15de65351e738c14325c908e  -
2dbcd56d642e44adca9184e65c7274174111599c17c9b61b2da79b9aedda8526  -
002e0a9d212cbb9c4fc2050a7cc6977e27ee0456a32f9f3ef4b5d8e716733a00  -
918f485b02f2f84b30886f8b5d6ff26d8a1cd138c01cd31299d4242d138f16d8  -
8792dbd7b7312a672be153b896435b6567932502b78bc391ba3a5202f17f1c64  -
96c759afcb6030bd4fff36575c5e363a4c0a9ae13ff0d524d21b3eedf72550c6  -
99bb7cc1ffa156732a5c55427920fa3d46d3fbe6ee913dc97088316fe6c903bc  -
4894d52bd2aec861542bec55342905a57a18092b5ed59e8df26ee83c70a95b6c  -
5efcc25f8a99d61929015e6f17aec4fe144d6df73b7fec352852e1ce27a7be41  -
2a4219c56399d288a09bb1b8bf537814ff165e28a4a0dfe88f4d4b32df1fc3c3  -
cd8de19959555bb9fba64894d42a9323f692925b083d57f97a5572e43d5440f9  -
5204b1b452070fcdc4d0a08fab2a9e22131c90d06839d8419de71eb41cdf5950  -
684b96b810fbe2081e45f370a24b64d7db031c05d712bdb94769b27d0b57c9b2  -
f485e41e1ec10563fc101c2673855f302b13cc9545c6ef42f03fea892d977ca4  -
4168a80b9a89dbe4ee0e1992468c3f087d8f414469f89235aff60fa38f9180e6  -
4d67e09fff45292494910375afba070082305e99da287a312567f0262542ee9c  -
5f93f7035760ffc6018e0cf62b200e714e946cdfb286a4a80222fce391bfe8c0  -
8d24f20e312f1732cfd5f1fc33a9f163b826a6b032b92b1bd4ee9cf3b77854f7  -

Otoh

donator

Activity: 3052

Merit: 1110

Quote from: bitlotto on March 28, 2012, 10:46:30 PM

Over 122 BTC with 1 week left! Remember that you can now send any amount at once to the draw address as long as it's a multiple of 0.25. No need to keep buying single tickets.

GOOD LUCK!

As that's now implemented & to save you the hassle of returning odd < 0.25 BTC amounts to anyone who can't do maths, why not make the rules that all money sent gets put into the jackpot regardless & if anyone sends over what is divisible by 0.25 then that is treated as a tip to the jackpot, it will be less than 0.25 BTC so no big deal - maybe peeps want to send their lucky 5.55 (22 bets + 0.05 coins tip) or 7.77 BTC (31 bets + 0.02 coins tip), before it mattered (like when I was totally maths/wallet spastic or whatever Embarrassed

) but now it's a trifling amount & you shouldn't need to be working out & sending back < 0.25 coins imo

another advantage with this is that the total shown to have been sent in is always correct for = jackpot

or the extra could be tips for you or a good cause, jp would be a fraction less but negligible difference

edit: bet you get a bunch of 6.66 BTC tx with 26 bets & a generous 0.16 coins sacrificed to the tip jar Wink

Stephen Gornick

legendary

Activity: 2506

Merit: 1010

Quote from: BurtW on March 29, 2012, 10:39:38 AM

I just bought 100 tickets.

And that ticket purchase (worth 25 BTC) puts this month's BitLotto into the record book with over 600 tickets for the month (as far as the most number of tickets sold for a single monthly lotto) as well as giving this draw the record high in terms of BTCs (now over 150 BTC).

There still is one more record to break -- the highest value monthly draw, when converted to USDs. The current recordholding draw using that criteria occurred back when the exchange rate was higher.

The record draw in terms of value in USDs might be the June 1, 2011 draw when tickets were 1 BTC each. On the day of that draw that jackpot of 134.6 BTC was valued at a BTC/USD north of $8 but when that payout occurred a few days later the BTC/USD was north of $15 (yes, it was that crazy last June). For that reason, there could be the argument that the record draw was instead the July 6, 2011 draw when the jackpot of 87.86 BTC was valued at a BTC/USD of around $15, putting it just a little higher (in terms of USDs) than June's jackpot was.

Perhaps the ability to purchase multiple tickets with one payment will some day boost BitLotto's monthly jackpot above the previous "valued in USDs" record, but that probably won't occur this month.

Maybe some of those who don't win the MegaMillions jackpot (now at a record $540 million -- exceeding the previous record of $390 million which has stood since 2007) will learn of BitLotto and its blockchain-verified 99% payout and will next time give BitLotto a try instead.

BurtW

legendary

Activity: 2646

Merit: 1137

All paid signature campaigns should be banned.

Quote from: bitlotto on March 28, 2012, 10:46:30 PM

Over 122 BTC with 1 week left! Remember that you can now send any amount at once to the draw address as long as it's a multiple of 0.25. No need to keep buying single tickets.

GOOD LUCK!

I just bought 100 tickets. I would like bitlotto to please send me a file containing all 100 official hashes. Also is there a web site or script I can run that will take my initial hash as input and give me a list of all of my ticket/hashes so I can verify the values myself and compare them to the "official" entries? Adding an input box to the bitlotto web site for a hash and a number of tickets would be pretty cool.

bitlotto

hero member

Activity: 672

Merit: 500

BitLotto - best odds + best payouts + cheat-proof

Over 122 BTC with 1 week left! Remember that you can now send any amount at once to the draw address as long as it's a multiple of 0.25. No need to keep buying single tickets.

GOOD LUCK!

Topic: [BITLOTTO] Mar 1 draw over $2000 or 50BTC! Tickets now 0.1 BTC for Apr 5 - page 24. (Read 55082 times)