Result didn't meet full difficulty, not sending

[BruceLee]

Ok, call me paranoid but I would like to ensure that this is expected behavior.

I am mining to my local bitcoin application running with the -server flag with the phoenix miner. I have verbose on as you will see from the output;

[08/05/2011 20:47:55] Result didn't meet full difficulty, not sending
[08/05/2011 20:48:07] Result didn't meet full difficulty, not sending
[08/05/2011 20:48:08] Server gave new work; passing to WorkQueue
[291.65 Mhash/sec] [0 Accepted] [0 Rejected] [RPC]

The 'Result didn't meet full difficulty, not sending' is making me nervous as I want to ensure that everything is actually working. I don't see the accepted raising as I do when I am connected to a pool and I don't to mine locally for weeks/months, only to find out that it wasnt working.

Does anyone else see this and if so, have you won a block?

thanks in advance.

[1715603948]

1715603948

[1715603948]

1715603948

[jedi95]

Ok, call me paranoid but I would like to ensure that this is expected behavior.

I am mining to my local bitcoin application running with the -server flag with the phoenix miner. I have verbose on as you will see from the output;

[08/05/2011 20:47:55] Result didn't meet full difficulty, not sending
[08/05/2011 20:48:07] Result didn't meet full difficulty, not sending
[08/05/2011 20:48:08] Server gave new work; passing to WorkQueue
[291.65 Mhash/sec] [0 Accepted] [0 Rejected] [RPC]

The 'Result didn't meet full difficulty, not sending' is making me nervous as I want to ensure that everything is actually working. I don't see the accepted raising as I do when I am connected to a pool and I don't to mine locally for weeks/months, only to find out that it wasnt working.

Does anyone else see this and if so, have you won a block?

thanks in advance.

This is working exactly as designed. The OpenCL kernel returns results that meet a difficulty of 1. (H == 0) Since you are solo mining the only results that will be sent to the server are the ones that meet the full difficulty. (like 109K at the moment)

In your case "accepted" would mean that you found a full difficulty result and that your local bitcoin accepted it. You will see a LOT of these results not being sent before you get lucky and find a full difficulty one.

[BruceLee]

Ok, many thanks for your reply.


So in other words , when I see the 'not sending' I can think of that as hashes that didn't solve the block? When I see one that is accepted that means that I solved the block and thus will get the reward?

again, thanks for helping a newbe.

[jedi95]

Ok, many thanks for your reply.


So in other words , when I see the 'not sending' I can think of that as hashes that didn't solve the block? When I see one that is accepted that means that I solved the block and thus will get the reward?

again, thanks for helping a newbe.

You can look at all of the "not sending" results as "shares" that didn't solve the block. It's expensive performance wise to have the OpenCL kernel check full difficulty. Since the number of difficulty 1 results is relatively small (one every 10 seconds or so on a fast 5870) it's easier to just check full difficulty on the CPU.

Anytime you get an accepted it means you found the solution to a block. This doesn't guarantee that the block will be valid though, only that your bitcoin RPC server accepted it. In most cases this should mean a valid block though.

[BruceLee]

I got it. Thanks again for taking the time. A meager donation is coming your way. (don't have many yet....)