CLOSE! You used the wrong lottery numbers. 20-24-31-33-36 Mega Ball 44 (From draw on 6th or just after 00 UTC on the 7th)
Doh! The PowerBall draw is not the same as Mega Ball draw. Wow -- shows you how much interest I have in the State-run lottery.
Oh, since the 6's make a tie, when you look at the 0's you are only using the hashes that tied with a 6.
Isn't that correct? The details from the site reads:
If multiple transaction hashes tie for how many picks match, a tie breaker is done. From the tied group, whoever has the most occurrences of the first pick in their entire hash is the winner. When using the first pick as a tie breaker it's possible for each potential winner to have the same count. If that is the case the next pick is looked at to see if a tie can be broken between those who tied with the most matching picks from the previous pick. It continues until all picks are used.
-
http://bitlotto.com/details.htmlSo in that example above [with the wrong Mega Million picks], there were multiple hashes that tied on the first pick (6), but to settle that tie, the next pick was used (0) and there were no further ties. Is that the correct methodology?
----------------------------
So, to do that winner selection over, using the correct Mega Millions lottery picks this time.
Determine the lucky block (first block after the deadline): 169953
-
https://blockexplorer.com/b/169953Hash from that block:
00000000000005300076544c21d2f352480c1efb4c1cec75125223f66a7015be
Add to that hash the Mega Millions picks:
20 24 31 33 36 Mega Ball 44
-
http://www.powerball.com/megamillions/mm_numbers.aspAppend the picks to the block hash and you get:
00000000000005300076544c21d2f352480c1efb4c1cec75125223f66a7015be202431333644
Get the sha256()
ee4cea6ea146419c874279bce52be30159b11709915d19efecd94a9a1a3f4222
-
http://www.xorbin.com/tools/sha256-hash-calculatorThe Winning Picks are the first ten from that hash:
ee4cea6ea1
Create the work file. The address for the March draw was: 1CdGqgJegokVaW5tPgC2vy3dZciggARdmh
$ GET
http://blockexplorer.com/address/1CdGqgJegokVaW5tPgC2vy3dZciggARdmh|grep "/tx/"|cut -d " " -f 3|cut -b 11-74 > workfile
(This grabs the HTML source for all the tickets for the monthly draw address, then cuts away everything but the transaction hashes.)
Remove from workfile any transaction hashes that were disqualified (e.g., entered late, amount was not large enough, etc.)
Determine the longest of the picks where there is at least one match:
$ grep e workfile|wc -l
$ grep ee workfile||wc -l
$ grep ee4 workfile|wc -l
$ grep ee4c workfile|wc -l
There were no transactoin hashes that had ee4c, so the winning pick is one of the ones with ee4.
$ grep ee4 workfile|awk 'BEGIN {FS = "e"};{print $0 " " NF-1}'|awk 'BEGIN {FS = "e"};{print $0 " " NF-1}'|awk 'BEGIN {FS = "4"};{print $0 " " NF-1}'|sort -rk2
This results in:
e1401f846cff82658f354fbed814ee414deb2fed461eed8c0e4dd3d8fa49d841 9 9 10
4e1c5454c7f13b66b39f162ec22fdd3d949d5f406e80ee4f6b07ea055906f821 6 6 6
e15ddfbf7a0ab05840f630427c1d18b6d680cfc443defd3c86ecbf87eee49a91 6 6 5
6e0c6874fc4ba9c55fbc269829e6868f058f6249a5249b8ed8ee490b8407699f 5 5 6
5677bf49d4595ca999dd2322732e64530d29b8b2eb76ef14f877520ee45f8dac 5 5 5
70141509656d93ee42651929c29fb9e65318474e02a01fc99cb6783262ffc2a3 4 4 6
f88e31a5e1f57330f384381926c5294553a31b90850925bc6ba6ff83951aee43 4 4 5
There was just one hash that had the most "e"s in it (9) -- so there were no ties.
If there had been, that tie would be broken by performing the same test for the next pick. Since in this months lotto, the second pick was the same as the first so we would still have a tie so would then move onto the next pick -- in this case, "4". If that pick too had resulted in a tie then the test would be done using next pick after that, in this case the "c", and so on until either there are no ties or until all ten picks have been used in the tests.
So at this point, the one entry becomes the winner:
e1401f846cff82658f354fbed814ee414deb2fed461eed8c0e4dd3d8fa49d841
That is the winning transaction. Looking at that transaction:
2012-03-06 07:19:02
-
http://blockexplorer.com/tx/e1401f846cff82658f354fbed814ee414deb2fed461eed8c0e4dd3d8fa49d841There is one one input to that, so that is where the jackpot will be sent:
1Nb2W2F56kuZeKAAhyEAbTomfn3RPt4t2D
This [unofficial] result jives with the unofficial result posted by bitlotto earlier.
& has loads of other potential applications where you regularly wish to repeat the same tx, either at same time, regularly, or just later 