Topic: This message was too old and has been purged (Read 1362 times)
Thanks!
Enough to collect the first bounty. Address please. 
I see you've already merged my changes. My address is 14cPUyRS9KqXBuRGV8Eyk4ckxD9EfPaXvo
It would seem that my submission qualifies for the second bounty because the performance of your version checked into github at the time of my submission was closer to 800000 not 4000000. I've verified this fact by testing with different compilers on different os's and on different platforms. This fact is further corroborated by statements you made here and here.
I'm going to charitably assume that the 4M number you cited earlier was from a dev version you had on your machine but had not yet pushed to github master (and therefore would not qualify as a basis for comparison per the rules of the bounty).
This message was too old and has been purged
I wrote a CPU darknxt miner about 6 months ago that is ~9 times faster than your current one.
Would committing modifications to my code so that it submits shares to your pool, www.bitprobing.com, be sufficient to collect the first two bounties?
Would committing modifications to my code so that it submits shares to your pool, www.bitprobing.com, be sufficient to collect the first two bounties?
The fifth last option you are searching for is short a hex char (7 instead of 
Should that be a trailing 0, leading 0, or did you goof in the copy/paste?
Code:
a==0xe239bdb
Should that be a trailing 0, leading 0, or did you goof in the copy/paste?
Same here - received tens of notifications on this bounty
You need wolf0 on this...I will send him a message.
I have sent him a message yesterday. Let's see how this goes 
You need wolf0 on this...I will send him a message.
This message was too old and has been purged
Jump to: