Yep. Orphaned block.
I actually had 2 solved blocks. The other was a reject.
If i'm understanding this correctly a reject is when another person finds a block at the exact same time as you but submits it to the network first.
Also, from what I've read, rejects tend to be greater solo mining because the default setting of cgminer is only looking for new getwork every 60 seconds. So, theoretically it's possible that the current work your rig is hashing has already been done for the last 60 seconds and just doesn't know about it yet. This is not good lol.
There's also the message "no long polling available". Not sure exactly what a long poll is but it has something to do with pools and I think keeps the entire pool "current" for what work it's doing.
I believe there is a parameter available for cgminer to change the timeframe on the getwork setting. Looking into that now. However, I believe there is a better solution as per this conversation from another forum discussing this subject:
http://forum.feathercoin.com/index.php?topic=1181.0"There shouldn't be any need to change the wallet setting or to create your own pushpool. When solo-mining I recommend adding a p2pool with stratum as a backup pool. This way, your miner will be notified of any new blocks very quickly, so you won't still be mining an old block."
If someone could explain what this means exactly and how to accomplish it that would be awesome.
