The instructions say to use one registered miner for each remote miner instance connected. Does this mean multithreaded miners need to be limited to 1 thread only? Will running them with multiple threads confuse the share algorithm?

I started my old pc a lot later then the fast one, but the slow one already has the full reward, so it seems a block was found in the meantime...

Found it, '32' according if it's the listed difficulty under each registered miner. So that's about 19 hours for a share using a 2,000 khash/s machine (my estimate of an average dual core laptop).

no, there's no need to limit multithread miners to 1thread,
i just tested jgarzik's miner with 2threads and it runs fine/gets me shares.

and again, i just had 2 of 3cores @ 2400khash/s each running for about 15minutes and got 2shares/found 2 winning hashes.
that's not even close to your 19hrs.

yes, that's the one i use for testing CPUs on windows.

Which version ? Did you build it yourself ?

Oh, too much traffic here 


32 is not difficulty, it means that target have 32 bits of zeros. You cannot compare this difficulty to global difficulty. 32 bits of zeros leads to ~1-2 blocks at 1000khash/s.


This is the rounding rest, reward from previous round was already sent to you. Reward for current block is calculated when block is found.


1 instance == 1 piece of software, NOT computer, NOT CPU/GPU core. Everytime you run miner software, each of them must have different credentials, otherwise your shares will not be correct.


Thanks, it is second 5970 in pool :-)


Yes, it is working. No special settings for Windows. You probably have bad URL, connection or whatewer.

It might be a good idea not to call it 'difficulty' on the webpage...

I suspect that 32 bits of zeroes = a difficulty of 1? (i.e. the original and easiest difficulty?)

hey slush,

do you feel like opening the source of your web interface ?
could give you a hand with impementing some stuff and polishing it

it's Rails isn't it ?