Topic: CGMiner --expiry --scan-time --queue (Read 3530 times)
push
I'm solo mining a fork crypto-currency with a short inter-block interval (2.5 m) with cgminer. Solo mining actually means that there's no LP (long pool). And as far as I know that also means no stratum protocol (only standard http getwork is supported). Last share I found was rejected. I suppose that happaned bacause of a lond getwork interval. I.e. my miner was working on a puzzle that had already been solved (become out of date). If getwork interval is 60 sec and a share is solved by the network in the first 5 seconds, that means my miner is wasting time another 55 seconds.
Is it possible to force more frequent getwork updates? Which cgminer parameter am I supposed to use?
I tried --expirity
I set it to 5 seconds and started mining. 10 seconds later I had a luck to find a share... BUT it has not even been sumbitted to the network It was declared as a stale. Very nice story. This is a useless parameter which might confuse people. It actually means that even if you find a share it won't be submitted if it's expired (it will be marked as a stale).
Does --scan-time do the job? Can I set it to 1-3 seconds if my wallet is running on the same computer in the server mode?
Is it possible to force more frequent getwork updates? Which cgminer parameter am I supposed to use?
I tried --expirity
I set it to 5 seconds and started mining. 10 seconds later I had a luck to find a share... BUT it has not even been sumbitted to the network It was declared as a stale. Very nice story. This is a useless parameter which might confuse people. It actually means that even if you find a share it won't be submitted if it's expired (it will be marked as a stale).Does --scan-time do the job? Can I set it to 1-3 seconds if my wallet is running on the same computer in the server mode?
Jump to: