Yeah, in reading over the "How the Pool Hashes Are Done" of http://bitlotto.com/pool.html I see that I am doing it all wrong.  I'll try to make a new version that does the pools correctly when I have time.

In case anyone cares, I've updated my tool to allow for multiple pool addresses:

https://github.com/baldrickv/BitLottoVerify

I've just pushed the BlockExplorer hack to github.

https://github.com/baldrickv/BitLottoVerify

The compiled jar in the download page doesn't have it, but you all can look at that terrible terrible fragile html parsing for block explorer.

https://github.com/baldrickv/BitLottoVerify/blob/master/src/BitLottoVerify.java#L79

Complete output:
http://pastebin.com/b2BaBCYE

Transactions and BTC amount match what Blockexplorer says so I am confidant the parsing was correct.

Hacked in my blockexporer code real quick:

Winner is TX 19bbd07cb4a5543dec7810a92bee57cd8204deebf517017e8a321a7fd85b6e3a (probably)


Draw address: 1Cbz6PF7ks85M4zmeWzotX12WUE14JZ29
Mixer: 00000000000003723f19329de9a63afc06abd3d9cfb1aea444cc9226ea13c611242731455238
Mixer hash: d9e3badbed16a90ab2486cad4935e82823a4ab954bac2b99fd69927592290cfa
Transactions: 412 BTC: 390.54710101 tickets: 1562

00eddc17: Transaction: 19bbd07cb4a5543dec7810a92bee57cd8204deebf517017e8a321a7fd85b6e3a multi:47 sha256(sha256(tx+47)+mixer_hash)
01028fae: Transaction: 607531218b74a7c662c6c9c9217448059f0c9183225902d440defde9ee5bac38 multi:21 sha256(sha256(tx+21)+mixer_hash)
0107634b: Transaction: 927afbfa3de03e0553941bf3764d39505701c0adf32659bb7d54099503fce5a9 multi:67 sha256(sha256(tx+67)+mixer_hash)
011453cf: Transaction: 7fd36c6986dabc5ef1f979ab2e20c82a2b9116b374b151ba063f48816c32b57f multi:61 sha256(sha256(tx+61)+mixer_hash)
014bd02c: Transaction: 607531218b74a7c662c6c9c9217448059f0c9183225902d440defde9ee5bac38 multi:41 sha256(sha256(tx+41)+mixer_hash)
015b05bc: Transaction: 19bbd07cb4a5543dec7810a92bee57cd8204deebf517017e8a321a7fd85b6e3a multi:317 sha256(sha256(tx+317)+mixer_hash)
0184d9e5: Transaction: 152ccd08c57ada125bf7206a995ec581fd0bf991d4c014e9cb5248a25f7dadd3 sha256(tx+mixer_hash)
01aad442: Transaction: 95abca2f72a9fa2a7bef2c4eb5f2bb9f83e8df9b1f746a7d50c0517ce0dc0f42 sha256(tx+mixer_hash)
0218f571: Transaction: d46427132039c870485c0fc5d50030d396b19c74ac882a21e3307878c7b87aca sha256(tx+mixer_hash)
024c9fc1: Transaction: b00ef78d11209581515515d3f098620b56da45ff138c2f370e2af31747aa1daf multi:1 sha256(sha256(tx+1)+mixer_hash)
02b4064f: Transaction: da0f318737b166fa6254f40af9878837bcc8559f9fd176e502d90d96b8de8004 multi:1 sha256(sha256(tx+1)+mixer_hash)
02ffb56b: Transaction: a851b3c176e9c349047bc814d75bddeccd76b3b71713c8dc9406f0f9f9e09aac multi:4 sha256(sha256(tx+4)+mixer_hash)
032c3fce: Transaction: 9303ef9021f054c9cbbe59eee4d9c24f3f1679d835b40872804838e5322ac4b5 sha256(tx+mixer_hash)
03719d98: Transaction: 19bbd07cb4a5543dec7810a92bee57cd8204deebf517017e8a321a7fd85b6e3a multi:162 sha256(sha256(tx+162)+mixer_hash)
0389c3b4: Transaction: 19bbd07cb4a5543dec7810a92bee57cd8204deebf517017e8a321a7fd85b6e3a multi:52 sha256(sha256(tx+52)+mixer_hash)
03aeac5f: Transaction: 19bbd07cb4a5543dec7810a92bee57cd8204deebf517017e8a321a7fd85b6e3a multi:320 sha256(sha256(tx+320)+mixer_hash)
03e3e97c: Transaction: 7af5a0bf264b925d9de6744a3775ad882a9343e78167c851254f13677b22c24b sha256(tx+mixer_hash)
03e50ca1: Transaction: 28daa59bd48af1f0a107f99f89cdb5daa0b2088c6fc50269ba10ba79b3125ed2 sha256(tx+mixer_hash)
041d2cd8: Transaction: 96a5fbe05328ee8b7329ac05092e080f049b7a5bb5692362362a2417eeb8e913 multi:3 sha256(sha256(tx+3)+mixer_hash)

Draw address: 1Cbz6PF7ks85M4zmeWzotX12WUE14JZ29
Mixer: 00000000000003723f19329de9a63afc06abd3d9cfb1aea444cc9226ea13c611242731455238
Mixer hash: d9e3badbed16a90ab2486cad4935e82823a4ab954bac2b99fd69927592290cfa

java -jar jar/BitLottoVerify.jar 1Cbz6PF7ks85M4zmeWzotX12WUE14JZ29 00000000000003723f19329de9a63afc06abd3d9cfb1aea444cc9226ea13c611 242731455238

Exception in thread "main" java.net.ConnectException: Connection refused
(Depends on blockchain.info)

Suck.

Yeah, MIT license.  I just updated it with that.

The only ways I can think of to make the output cleaner involve going to multiple lines per ticket.  I was trying to avoid that so people could grep for their transactions easily if they were so inclined.

I guess I could truncate the end hash a bit.

Yeah, that is pretty decent:
0023da9a: Transaction: 277a5da2a46b0ba9ddaa33fa374bd9acd4a0ea227badf5d3e3d14d9a05238c81 sha256(tx+mixer_hash)
00397274: Transaction: 71599cc9375aef02271486acce76dc7059af5e27919429aa3ee62c915bf613f0 multi:81 sha256(sha256(tx+81)+mixer_hash)
006fd30e: Transaction: 71599cc9375aef02271486acce76dc7059af5e27919429aa3ee62c915bf613f0 multi:74 sha256(sha256(tx+74)+mixer_hash)
0095fa50: Transaction: 0fe78f915237de55378fd59a225c1f3e1c3c40f32da770924a7bcab3b67d548a multi:2 sha256(sha256(tx+2)+mixer_hash)
00b6d9ba: Transaction: 296d34b48f099d83a500b58bc7d411c23a8fc36bc5bb64fa7a34c789b6a2565a multi:2 sha256(sha256(tx+2)+mixer_hash)
00c42aff: Transaction: c9604c6144f4c12d585891e9b507cf7781d36ae6fcf3ccf4aef198fae754ca36 sha256(tx+mixer_hash)
00cf0b5e: Transaction: a1ea664b8d1acc35adc92bb38066beeb60b18063dc04a7485cacff772d2e0779 sha256(tx+mixer_hash)

As promised, here is a program to find the winner (unless the rules have changed in the last few weeks while I haven't been paying attention):

https://github.com/baldrickv/BitLottoVerify

A compiled download is available here:

https://github.com/baldrickv/BitLottoVerify/downloads

Here is what the output looks like:

(Validating last month's drawing)
$ java -jar jar/BitLottoVerify.jar 14avxyPW5PgA68kGkDkY1mCGPP8zqkywEx 000000000000042c91c9de46f802524ab1c2296923a72b55fac2d2c6fd7f4741 113538415240

Draw address: 14avxyPW5PgA68kGkDkY1mCGPP8zqkywEx
Mixer: 000000000000042c91c9de46f802524ab1c2296923a72b55fac2d2c6fd7f4741113538415240
Mixer hash: 1e3c407515124ef4c674f1f997342cb882063f013b19b95184511ef196985b70
Transactions: 527 BTC: 288.751 tickets: 1155
Total tickets: 1155
0023da9af152f9dd17501b060df7d5dbd762ca880cb3e731e40c391af34aadf7: Transaction: 277a5da2a46b0ba9ddaa33fa374bd9acd4a0ea227badf5d3e3d14d9a05238c81 sha256(tx+mixer_hash)
00397274f95b78993d489f1ac330dcf765f532eda7f2af93860ee6c181952df3: Transaction: 71599cc9375aef02271486acce76dc7059af5e27919429aa3ee62c915bf613f0 multi:81 sha256(sha256(tx+81)+mixer_hash)
006fd30e0eb3b85e2b3d0b679665df710f4dc371c799ea0c9603905587b27c4a: Transaction: 71599cc9375aef02271486acce76dc7059af5e27919429aa3ee62c915bf613f0 multi:74 sha256(sha256(tx+74)+mixer_hash)
0095fa502da11709bf17d47b034705bd193ec68a4480efa712586167b68f2643: Transaction: 0fe78f915237de55378fd59a225c1f3e1c3c40f32da770924a7bcab3b67d548a multi:2 sha256(sha256(tx+2)+mixer_hash)
...

Just FYI, BitcoinJ 0.4 works.  It is in fact a little simpler since it doesn't generate a pool of new addresses for change addresses so your coins will be in an address you see in your wallet.

I very much doubt it.  I haven't used this particular handle much.

1DW4mtFwkLAbfc4ZBvcXypeV6NhfDryrni Is one of mine.  I had a total of 33.25 BTC in.  I don't know where the leet came from.  I guess it was a tip from someone.

My current plan is to buy two BFL Singles with the jackpot.

No problem at all.  I'll post the code at some point before then as well.

I agree, here is the top lines from my data:

http://pastebin.com/NnAd91rq

277a5da2a46b0ba9ddaa33fa374bd9acd4a0ea227badf5d3e3d14d9a05238c81

1DW4mtFwkLAbfc4ZBvcXypeV6NhfDryrni

It is currently a terrible mess and if I were to release it I'm fairly certain that would be considered a war crime.  I can clean it up and throw it in a Github project.  It isn't great because it is just downloading the list of transactions for the address from blockexplorer and parsing them poorly.

I have a program to crunch the results.

Here is what it outputs:
http://pastebin.com/Wt1wNVjd

Not the real run obviously but I'll run it and post once the real mixer string is known.

I'll work on a program for the new rules and I'll try to have it ready by drawing time.

I would like out of here.  I need to post on the Bitlotto topic, although what I have to say there has mostly already been addressed.

I've been a miner for about 6 months.  I'm developing some sites based on using BitcoinJ to automatically process some transactions.

I have a background in computer security and programming and have a rather good understanding of Bitcoin.

Never pet a burning dog.

It is complicated and likely to change.

What the Satoshi client does is pretty strange.  Other clients don't do the same thing and there is no guarantee on what miners will chose to include or nodes will rebroadcast.  This is kind of as it needs to be.  One of the attack vectors on the network is to generate too many stupid transactions that just cycle money around.  If that starts to happen people will tweak the fee structure to make that expensive or not worth it for the person doing it.  And we don't really know what those will look like until it happens.

Example, lets say everyone uses 0.0005 as a standard transaction fee.  That is enough where sending thousands of transactions is unappealing long term.  However, if bitcoins end up being 0.02 USD each then that transaction fee is so small that someone might DoS the network with transactions for fun.  So it needs to be flexible and somewhat undefined.