Quote from: Just_a_miner on February 12, 2018, 05:19:08 PM

Quote from: xxmetalmartyrxx on February 12, 2018, 05:12:26 PM

Quote from: Just_a_miner on February 12, 2018, 05:07:02 PM

Quote from: xxmetalmartyrxx on February 12, 2018, 04:32:10 PM

Hey is there any way to tweak this miner for solo mining? I solo mined a bit the other day, and got a bunch of rejected blocks. On regular CCMiner, I've set the scantime=1 and timeout=1. Is there any way that can be implemented so that I'm not getting stale blocks?

I can probably add those options, but how do you actually solomine with ccminer? I've read some guide, according to it you need ccminer that supports --no-getwork and --coinbase-addr parameters, and it's not possible to add those parameters to my fork in a reasonable time.

Like it solo mines fine, just not scanning blocks in time. All I do is keep my local wallet open, and I connect to its IP and port via the batchfile. This is what my batchfile looks like
ccminer -a neoscrypt -o http://127.0.0.1:39655 -u x -p x.
You have to set the config in your wallet up, and then once its set up with the right port and IP, it's just click and go.

Ok, 1) what ccminer is this? Klaust, tpruvot? 2) What is --timeout=1 ? Network timeout? 3) Did you actually try to solo mine with my fork?

I'm using Klaust. Yeah network timeout. Not exactly sure if that helps, but I've seen on threads for solo mining feather coin, they put network timeout to 1. And yes I did try, works awesome for pool mining, but for solo mining it only got rejects Sad

100% reject rate.