solo mining question

[rikii]

so while solo mining goldcoin for the fun of it. cgminer said block found accepted, my wallet, which is brand new, says transactions 1.  yet nothing shows under transactions tab, nothing listed as immature, or unconfirmed. I guess i dont get it. usually when i get an orphan it just shows as rejected in cgminer, this one said accepted and even my wallet shows "number of transactions: 1" Never encountered this and couldn't find relevant information when searching the forums.

[jonptl]

Hi, a few things we have to clarify here.

A reject is not an orphan, its just a reject. Aka a solution that doesnt solve the crypto problem for the block. Its just rejected.

An orphan is an accepted transaction, just that someone was faster than you. It will be listed as accepted in cgminer, and get a transaction as you have seen in the client but with no coins.

If you want to confirm this, go to the debug window in the clieny, type 'listtransactions' . U will see ur orphan there.

There you go!


Wouldnt mind a donation if ur happy with the ans!

[btc4ever]

So why would so many people be getting rejects when solo mining?  Based on the answer above, I conclude that the hash is being computed incorrectly by the GPU, but at least in my case I have 0 hardware errors reported by cgminer but am seeing lots of rejected.   can someone splain me please?

[btc4ever]

Okay, I found the answer on another forum.  Probably obvious to many here, but maybe it will help someone.

Usually the coin daemon does not supply LongPoll or stratum. These protocols are used to inform you when a new block is found in the network. If you are solomining you should set your scantime to something around 2-10seconds. So your miner fetches new work every 2-10seconds. Once a block is found on the network you will have a different prevhash, which causes your old getwork to be invalid.. If your miner is hashing on it for ,lets say a minute (i think this is default on cgminer), there is a chance that the network found the block a few seconds(e.g. 10) after your last getwork call. So now your hasher is hashing on an old getwork for another 50 seconds, trying to submit a block, finds out prevhash changed, and starts hashing on the new prevhash. But the block you have tried to submit, is already invalid for these 50seconds... so best way is to move to a pool or use low scantime(this does not matter on LAN usually).

I only got 1 reject, and 6500+ accepts. 
try lowering your "expiry" and "scan-time" and set queue=0

here's my settings if you want to try:

queue=0
scan-time=2
expiry=2