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.